XMLMap on Computing (2/4) - exploring XML
XMLMap on Computing
Active Digital Profile
The ADPr is a structured framework (a vocabulary and schema) for describing the structure and content of eProvisioning information in an XML Document. Then ,the information can be used by any application that makes use of XML, to provision resources or services.
eProvisioning refers to automating the process of systematically providing resources and services, according to business requirements. For example, when a new person joins an organization, this means automating the process of collecting, allocating, and configuring all of the resources this person will need before he or she begins to work. This process can include assigning an extension on a PBX, creating accounts for email and other applications the person will need, procuring and configuring a computer or cell phone based on the job profile, and even ordering business cards.
eProvisioning also supports the allocation and confiscation of resources as people are reassigned or their relationship to the business changes. This allows eProvisioning to be used with partners, contractors, supply chain vendors, customers and other parties that are not part of a company per se but that still need access to company resources for the term of the relationship.
Service Provisioning Markup Language
Service Provisioning Markup Language (SPML) is an XML-based framework specification for exchanging user, resource, and service provisioning information. The SPML specification is being developed with consideration of the following provisioning-related specifications: Active Digital Profile (ADPr), eXtensible Resource Provisioning Management (XRPM), and Information Technology Markup Language (ITML).
XML support for UTF-8 and UTF-16 character sets make it a compelling technology to use for internationalization and text translation.
TMXTMX stands for Translation Memory eXchange. It is a vendor-neutral, open standard for storing and exchanging translation memories created by Computer Aided Translation (CAT) and localization tools. The purpose of TMX is to allow easier exchange of translation memory data between tools and/or translation vendors with little or no loss of critical data during the process.
TMX is the result of an initiative undertaken by the OSCAR (Open Standards for Container/Content Allowing Re-use) committee, a LISA Special Interest Group. Founded in 1990 as a non-profit association, LISA is the premier organization for the GILT (Globalization, Internationalization, Localization, and Translation) business communities. Over 200 leading IT manufacturers and solutions providers, along with industry professionals and an increasing number of vertical market corporations with an international business focus, have helped establish LISA best practice guidelines and language-technology standards for enterprise globalization.
TMX is defined in two parts:
- A specification of the format of the container (the higher-level elements that provide information about the file as a whole and about entries). In TMX, an entry consisting of aligned segments of text in two or more languages is called a Translation Unit (the <tu> element).
- A specification of a low-level meta-markup format for the content of a segment of translation-memory text. In TMX, an individual segment of translation-memory text in a particular language is denoted by a <seg> element.
TMX offers two levels of implementation:
- Level (Plain Text Only) - Support for the container only. The data inside each <seg> element is plain text, without Content Markup. This level is enough when the data does not have inline codes, such as software messages. It is not sufficient for documentation-type formats.
- Level (Content Markup) - Support for both container and content. The application uses the TMX Content Markup, to allow any other tools supporting also TMX Level 2 to recreate the translated version of an original document by using only the TMX document. This level does not take in account segmentation difference.
XLIFF is the XML Localization Interchange File Format designed by a group of software providers, localization service providers, and localisation tools providers. It is intended to give any software provider a single interchange file format that can be understood by any localization provider. It is loosely based on the OpenTag version 1.2 specification and borrows from the TMX 1.2 specification. However, it is different enough from either one to be its own format.
On to devices and databases...
Produced by Michael Claßen
Created: Apr 28, 2003
Revised: Apr 28, 2003