[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fwd: [xliff] Version Control Commit by David.Filip
Working Draft 026 August 2013
NoticesCopyright © OASIS Open 2013. All Rights Reserved. All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Committee Specification or OASIS Standard, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this specification by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this specification. OASIS may include such claims on its website, but disclaims any obligation to do so. OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Committee Specification or OASIS Standard, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims. The name "OASIS" is a trademark of OASIS, the owner and developer of this specification, and should be used only to refer to the organization and its official outputs. OASIS welcomes reference to, and implementation and use of, specifications, while reserving the right to enforce its marks against misleading uses. Please see http://www.oasis-open.org/policies-guidelines/trademark for above guidance. Table of Contents
Appendixes
XLIFF is the XML Localisation Interchange File Format designed by a group of software providers, localization service providers, and localization tools providers. It is intended to give any software provider a single interchange file format that can be understood by any localization provider. All text is normative unless otherwise labeled. The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are to be interpreted as described in [RFC 2119].
[BCP 47] M. Davis, Tags for Identifying Languages, http://tools.ietf.org/html/bcp47 IETF (Internet Engineering Task Force). [HTML5] W3C, HTML5. A vocabulary and associated APIs for HTML and XHTML, http://www.w3.org/TR/html5/ W3C Candidate Recommendation 17 December 2012. [NOTE-datetime] M. Wolf, C. Wicksteed, Date and Time Formats, http://www.w3.org/TR/NOTE-datetime W3C Note, 15th Setember 1997. [RFC 2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, http://www.ietf.org/rfc/rfc2119.txt IETF (Internet Engineering Task Force) RFC 2119, March 1997. [UAX #9] M. Davis, UNICODE BIDIRECTIONAL ALGORITHM, http://www.unicode.org/reports/tr9/ Unicode Bidirectional Algorithm. [UAX #15] M. Davis, K. Whistler, UNICODE NORMALIZATION FORMS, http://www.unicode.org/reports/tr15/ Unicode Normalization Forms. [Unicode] The Unicode Consortium, The Unicode Standard, http://www.unicode.org/versions/latest/ Unicode Normalization Forms. [XML] W3C, Extensible Markup Language (XML) 1.0, http://www.w3.org/TR/xml/ (Fifth Edition) W3C Recommendation 26 November 2008. [XML I18N BP] Best Practices for XML Internationalization, 13 February 2008, http://www.w3.org/TR/xml-i18n-bp/ W3C Working Group. [LDML] Unicode Locale Data Markup Language http://unicode.org/reports/tr35/ [SRX] Segmentation Rules eXchange http://www.gala-global.org/oscarStandards/srx/ XLIFF is a bilingual document format designed for containing text that needs translation, its corresponding translation and auxiliary data that makes the translation proccess possible. At creation time, an XLIFF file MAY contain only text in source language. Translations expressed in target language MAY be added at a later time. The root element of an XLIFF document is
This section contains a description of all elements used in XLIFF 2.0. Legend:
The structural elements used in XLIFF 2.0 are:
Root element for XLIFF documents. Contains:
Attributes:
Constraints
Container for localization material extracted from a single document/source. Contains:
Attributes:
Container for untranslatable material pertaining to the parent
Contains: Either
or
Attributes:
Processing Requirements
Provides a way to organize units into a structured hierarchy. Contains:
Attributes:
Extracted translatable text. Contains:
Attributes:
Minimum portion of translatable text. Contains:
Attributes:
Constraints
Part of the extracted content that is not included in a segment (and therefore not translatable). For example some tools may use
Contains:
Attributes:
Processing Requirements
Collection of comments. Contains:
Attributes:
A comment that contains information about
Contains:
Attributes:
Unit-level collection of original data for the inline codes. Contains:
Attributes:
Storage for the original data of an inline code. Contains:
Untranslatable text and Attributes:
Constraints
Portion of text to be translated. Contains:
Text and inline elements may appear in any order. Attributes:
The translation of the sibling Contains:
Text and inline elements may appear in any order. Attributes:
Constraints
The inline elements at the The elements at the Represents a Unicode character that is invalid in XML. Contains:
Parents:
Attributes:
Example: <unit id="1"> <segment> <source>Ctrl+C=<cp hex="0003"/></source> </segment> </unit> The example above shows a character U+0003 (Control C) as it must be represented in XLIFF. Represents a standalone code of the original format. Contains:
Parents:
Attributes:
Example: <unit id="1"> <segment> <source>Number of entries: <ph id="1" dataRef="d1" /> <ph id="2" dataRef="d2"/>(These entries are only the ones matching the current filter settings)</source> </segment> <originalData> <data id="d1">%d</data> <data id="d2"><br/></data> </originalData> </unit> Represents a well-formed spanning original code. Contains:
Text and inline elements may appear in any order. Parents:
Attributes:
Example: <unit id="1"> <segment><pc id="1" dataRefStart="1" dataRefEnd="2">Important</pc> text</source> </segment> <originalData> <data><B></data> <data></B></data> </originalData> </unit> Processing Requirements
Start marker of a spanning original code. Contains:
Parents:
Attributes:
Example: <unit id="1"> <segment> <source><sc id="1" type="fmt" subType="xlf:b"/>First sentence. </source> </segment> <segment> <source>Second sentence.<ec startRef="1" type="fmt" subType="xlf:b"/></source> </segment> </unit> Constraints
End marker of a spanning original code. Contains:
Parents:
Attributes:
Example: <unit id="1"> <segment> <source>Text in <sc id="1" dataRef="d1"/>bold <sc id="2" dataRef="d2"/> and<ec startRef="1" dataRef="d3"/> italics<ec startRef="2" dataRef="d4"/>.</source> </segment> <originalData> <data id="d1">\b </data> <data id="d2">\i </data> <data id="d3">\b0 </data> <data id="d4">\i0 </data> </originalData> </unit> Processing Requirements
Represents an annotation. Contains:
Text and inline elements may appear in any order. Parents:
Attributes:
See the Annotations section for more details and
examples on how to use the Start marker of an annotation. Contains:
Parents:
Attributes:
See the Annotations section for more details and
examples on how to use the This section lists all the various attributes used in XLIFF core elements. The attributes defined in XLIFF 2.0 are: Approved - Indicates whether the holding
Value description: Default value: Used in: Comment target - Indicates the element to whom the content of the note applies. Value description: Default value: undefined. Used in: Replication editing hint - Indicates whether or not the inline code can be copied. Value description: Default value: Deletion editing hint - Indicates whether or not the inline code can be deleted. Value description: Default value: Code can overlap - Indicates that the spanning code where this attribute is used may enclose partial spanning codes (i.e. a start marker without its corresponding end marker, or a end marker without its corresponding start marker). Value description: Default value: the default value for this attribute depends on the element in which it is used: Example: <unit id="1"> <segment> <source><pc id="1" dataRefStart="3" dataRefEnd="4" canOverlap="no"/>Bold, <sc id="2" dataRef="1" canOverlap="yes"/>both</pc>, italics<ec startRef="2" dataRef="2"/></source> </segment> <originalData> <data id="1">\i1 </data> <data id="2">\i0 </data> <data id="3">{\b </data> <data id="4">}</data> </originalData> </unit> Re-ordering editing hint - Indicates whether or not the inline code can be re-ordered. See Editing Hints section for more details. Value description: Default value: Category - Provides a way to categorize notes. Value description: Text. Default value: undefined Used in: Reference to base code - Holds the Value description: NMTOKEN. The Default value: undefined Used in: Example: <unit id="1"> <segment> <source>Äter <pc id="1">katter möss</pc>?</source> <target>Do <pc id="1">cats</pc> eat <pc id="2" copyOf="1">mice</pc>?</target> </segment> </unit> Indicates the directionality of a content. Value description: Default value: default values for this attribute depend on the element in which it is used:
Display text - Holds an alternative user-friendly display representation of the original data of the inline code. Value description: Text Default value: undefined Example: <unit id="1"> <segment> <source>Welcome back <ph id="1" disp="[UserName]" dataRef="d1"/>!</source> </segment> <originalData> <data id="d1">{1}</data> </originalData> </unit> NoteTo provide a plain text equivalent of the code, use the Display text - Holds an alternative user-friendly display representation of the original data of the end marker of an inline code. Value description: Text Default value: undefined Used in: Example: <unit id="1"> <segment> <source>Example of <pc id="1" dataRefStart="d1" dataRefEnd="d2" dispStart="<span>" dispEnd="</span>">formatted text</pc>.</source> </segment> <originalData> <data id="d1">\cf1\ul\b\f1\fs24 </data> <data id="d2">\cf0\ulnone\b0\f0\fs22 </data> </originalData> </unit> In the example above, the NoteTo provide a plain text equivalent of the code, use the Display text - Holds an alternative user-friendly display representation of the original data of the start marker of an inline code. Value description: Text Default value: undefined Used in: Example: <unit id="1"> <segment> <source>Example of <pc id="1" dataRefStart="d1" dataRefEnd="d2" dispStart="<span>" dispEnd="</span>">formatted text</pc>.</source> </segment> <originalData> <data id="d1">\cf1\ul\b\f1\fs24 </data> <data id="d2">\cf0\ulnone\b0\f0\fs22 </data> </originalData> </unit> In the example above, the NoteTo provide a plain text equivalent of the code, use the Equivalent text - Holds a plain text representation of the original data of the inline code that may be used when generating a plain text representation of the content. Value description: Text Default value: an empty string. Example: <unit id="1"> <segment> <source>Open <ph id="1" equiv="" dataRef="d1"/>File</source> </segment> <originalData> <data id="d1">&</data> </originalData> </unit> In this example the NoteTo provide a user-friendly representation, use the Equivalent text - Holds a plain text representation of the original data of the end marker of an inline code that may be used when generating a plain text representation of the content. Value description: Text Default value: an empty string Used in: Example: <unit id="1"> <segment> <source>The jam made of <pc id="1" dataRefStart="d1" equivStart="" dataRefEnd="d2" equivEnd="">lingonberries</pc> is quite tasty.</source> </segment> <originalData> <data id="d1"><span class="link" ></data> <data id="d2"></span></data> </originalData> </unit> NoteTo provide a user-friendly representation, use the Equivalent text - Holds a plain text representation of the original data of the start marker of an inline code that may be used when generating a plain text representation of the content. Value description: Text Default value: an empty string Used in: Example: <unit id="1"> <segment> <source>The jam made of <pc id="1" dataRefStart="d1" equivStart="" dataRefEnd="d2" equivEnd="">lingonberries</pc> is quite tasty.</source> </segment> <originalData> <data id="d1"><span class="link" ></data> <data id="d2"></span></data> </originalData> </unit> NoteTo provide a user-friendly representation, use the Hexadecimal code point - Holds the value of a Unicode code point that is invalid in XML. Value description: A canonical representation of the hexBinary XSD data type: Two hexadecimal digits to represent each octet of the Unicode code point. The allowed values are any of the values representing code points invalid in XML, between hexadecimal 0000 and 10FFFF (both included). Default value: undefined Used in: Example: <cp hex="001A"/><cp hex="0003"/> The example above shows a character U+001A and a character U+0003 as they should be represented in XLIFF. href - a pointer to the location of an external skeleton file pertaining to the
enclosing Value description: IRI. Default value: undefined Used in: Identifier - A character string used to identify an element. Value description: NMTOKEN. The scope of the values for this attribute depend on the element in which it is used
Default value: undefined Used in: Orphan code flag - Indicates if the start or end marker of a spanning
inline code is not in the same Value description: Default value: Example: <unit id="1"> <segment> <source><pc id="1">Warning: File not found.</pc></source> </segment> <mtc:matches> <mtc:match> <segment> <source><sc id="1" isolated="yes"/>Warning:</source> <target><sc id="1" isolated="yes"/>Attention :</target> </segment> </mtc:match> </match> </unit> In the example above the Resource Name - The original identifier of the resource corresponding to the extracted
Value description: text string. Default value: undefined. Original data reference - Holds the identifier of the Value description: An XSD NMTOKEN that
must be the value of the Default value: undefined. Example: <unit id="1"> <segment> <source>Error in '<ph id="1" dataRef="d1"/>'.</source> <target>Erreur dans '<ph id="1" dataRef="d1"/>'.</target> </segment> <originalData> <data id="d1">{0}</data> </originalData> </unit> The example above shows a Original data reference - Holds the identifier of the Value description: An XSD NMTOKEN that must be
the value of the Default value: undefined. Used in: Example: <unit id="1"> <segment> <source><pc id="1" dataRefStart="d1" dataRefEnd="d2">Efficiency<pc> is the operative word here.</source> <target><pc id="1" dataRefStart="d1" dataRefEnd="d2">Efficacité<pc> est le mot clé ici.</target> </segment> <originalData> <data id="d1"><EM></data> <data id="d2"></EM></data> </originalData> </unit> The example above shows two Original data reference - Holds the identifier of the Value description: An XSD NMTOKEN that must be
the value of the Default value: undefined. Used in: Example: <unit id="1"> <segment> <source><pc id="1" dataRefStart="d1" dataRefEnd="d2">Efficiency<pc> is the operative word here.</source> <target><pc id="1" dataRefStart="d1" dataRefEnd="d2">Efficacité<pc> est le mot clé ici.</target> </segment> <originalData> <data id="d1"><EM></data> <data id="d2"></EM></data> </originalData> </unit> The example above shows two Original File - A pointer to the location of the original document from which the content
of the enclosing Value description: Text. Default value: undefined Used in: Priority - Provides a way to prioritize notes. Value description: Integer 1-10. Default value: 1 Used in: NotePlease note that 1 is the highest priority that can be interpeted as an alert, e.g. an ITS Localization Note of the type alert. The best parctice is to use only one alert per an anotated element, and the full scale of 2-10 can be used for prioritizing notes of lesser importance than the alert. Reference - Holds a reference for the associated annotation. Value description: A value of the XSD type anyURI. The semantics of the value depends on the type of annotation:
Default value: undefined Example: <unit id="1"> <segment> <source>The <pc id="1">ref</pc> attribute of a term annotation holds a <mrk id="m1" type="term" ref="http://dbpedia.org/page/Uniform_Resource_Identifier">URI</mrk> pointing to more information about the given term.</source> </segment> </unit> Start marker reference - The Value description: NMTOKEN. Default value: undefined Example: <unit id="1"> <segment> <source><sc id="1"/>Bold, <sc id="2"/>both<ec startRef="1"/>, italics<ec startRef="2"/></source> </segment> </unit> Indicates the directionality of the source content. Value description: Default value: default values for this attribute depend on the element in which it is used: Source Language - The code of the language in which the text to be translated is expressed. Value description: A language code as described in [BCP 47]. Default value: undefined Used in: Sub-flows list - Holds a list of Value description: A list of NMTOKEN values
separated by spaces. Each value corresponds to the Default value: undefined Example: See the example in the Sub-Flows section. Sub-flows list - Holds a list of Value description: A list of NMTOKEN values
separated by spaces. Each value corresponds to the Default value: undefined Used in: Example: See the example in the Sub-Flows section. Sub-flows list - Holds a list of Value description: A list of NMTOKEN values
separated by spaces. Each value corresponds to the Default value: undefined Used in: Example: See the example in the Sub-Flows section. subType - Indicates the secondary level type of an inline code. Value description: The value is composed of a prefix and a sub-value separated by a
character The prefix is a string uniquely identifying a collection of values for a specific authority. The sub-value is any string value defined by an authority. The prefix
Other prefixes and sub-values may be defined by the users. Default value: Undefined subState - indicates a user-defined status for the Value description: The value is composed of a prefix and a sub-value separated by a
character The prefix is a string uniquely identifying a collection of values for a specific authority. The sub-value is any string value defined by an authority. The prefix Other prefixes and sub-values may be defined by the users. Default value: Undefined Used in: Type - indicates the state of the translation of a segment. Value description: The value must be set to one of the following values:
One can further specify the state of the translation using the Default value: Used in: Constaints
Target Language - The code of the language in which the translated text is expressed. Value description: A language code as described in [BCP 47]. Default value: undefined Used in: Translate - Indicates whether or not the source text text of a
Value description: Default value: Indicates the directionality of the target content. Value description: Default value: default values for this attribute depend on the element in which it is used: Type - Indicates the type of an element. Value description: allowed values for this attribute depend on the element in which it is used.
Value - Holds a value for the associated annotation. Value description: Text.
Default value: undefined Used in: XLIFF version - The version attribute is used to specify the format version of the XLIFF document. This corresponds to the version number of the XLIFF specification that is being adhered to. Value description: Text. Default value: 2.0 Used in: The attributes from XML namespace used in XLIFF 2.0 are xml:lang and xml:space. Language - The xml:lang attribute specifies the language variant of the text of a given element.
For example: Value description: A language code as described in [BCP 47]. Default value: undefined White spaces - The xml:space attribute specifies how white spaces (ASCII spaces, tabs and line-breaks) should be treated. Value description: Default value: CDATA sections ( Note that avoiding CDATA sections is considered a best practice from the internationalization viewpoint [XML I18N BP]. Processing Requirements
XML comments ( For example: <source>Text content <!--IMPORTANT-->that is important</source> and <source>Text content that is important</source> are identical after parsing and correspond to the same following parsed content: Text content that is important To annotate a section of the content with a comment that is
recognized and preserved by XLIFF user agents, use the Processing Requirements
XML Processing Instructions [XML](see specifically http://www.w3.org/TR/REC-xml/#sec-pi) are an XML mechanism to "allow documents to contain instructions for applications." XML Processing Instructions are allowed in XLIFF content but they are ignored in the parsed content in the same sense as XML Comments. Processing Requirements
WarningPlease note that Agents using Processing Instruction to implenmet XLIFF core or module fetaures are not compliant XLIFF Agents disregaring wheteher they are otherwise conformant. WarningAlthough this specification encourages XLIFF Agents to preserve XML Processing Instructions, it is not and cannot be, for valid processing reasons, an absolute protection and it is
for instance highly unlikely that Processing Instructions could survive an XLIFF roundtrip at the The XLIFF inline content defines how to encode the content extracted from the original source. The content includes the following types of data:
There are two elements that contain inline markup in XLIFF: In some cases, data directly associated with inline elements MAY also
be stored at the The XLIFF inline markup does not prescribe how to represent normal text, besides that it MUST be valid XML. Because the content represented in XLIFF can be extracted from anywhere, including software resources and other material that can contain control characters, XLIFF needs to be able to represent all Unicode code points [Unicode]. However, XML does not have the capability to represent all Unicode code points [Unicode], and does not provide any official mechanism to escape the forbidden code points. To remedy this, the inline markup provides the The syntax and semantic of The specification takes into account two types of codes: Any code (original or added) belongs to one of the two following categories:
Spanning codes present a set of challenges in XLIFF: First, because the code format of the original data extracted to XLIFF does not need to be XML, spanning codes can overlap. For example, in the following RTF content, the format markers are in a sequence: start bold, start italics, end bold, end italics. This does not translate into a well-formed mapping. Text in \b bold \i and\b0 italics\i0 Another challenge is the possible effect of segmentation: A spanning code can start in one segment and end in another. For example, in the following HTML content, the segmentation
splits the text independently of the codes so the starting and ending
tags of the [Sentence <B>one. ][Sentence two.][ ][Sentence</B> three.] Finally, a third potential cause of complication is that the start
or the end markers of a spanning code can become orphans if their
segment is used outside of its original For example, an entry with bold text can be broken down into two segments: Segment 1 = "<b>Warning found: " Segment 2 = "The file is read-only</b>" And later, one of the segments can be re-used outside its original
New segment = "<b>Warning found - see log</b>" Fuzzy match = "<b>Warning found: " Because of these use cases, the representation of a spanning code cannot always be mapped to a similar spanning element in XLIFF. When taking into account these issues, the possible use cases and their corresponding XLIFF representations are as follow: Table 1. Inline code use cases
A spanning code MUST be represented using a For example, the following RTF content has two spans of formatting: Text in \b bold \i and\b0 italics\i0 They can only be represented using two pairs of Text in <sc id="1">\b </sc>bold <sc id="2">\i </sc>and<ec startRef="1">\b0 </ec> italics<ec startRef="2">\i0</ec> If the spanning code is well-formed it MAY be represented using
either a single For example, the following RTF content has a single span of formatting: Text in \b bold\b0 . It can be represented using either notations: Text in <pc id="1" canOverlap="yes" dataRefStart="c1" dataRefEnd="c2">bold</pc>. Text in <sc id="1" dataRef="c1"/>bold<ec startRef="1" dataRef="c2"/>. Processing Requirements
Most of the time, inline codes correspond to an original construct in the format from which the content was extracted. This is the original data. XLIFF tries to abstract and normalize as much as possible the extracted content because this allows a better re-use of the material across projects. Some tools require access to the original data in order to create the translated document back into its original format. Others do not. In this option, the original data of the inline code is not preserved inside the XLIFF document. The tool that created the initial XLIFF document is responsible for providing a way to re-create the original format properly when merging back the content. For example, for the following HTML content: This <B>naked mole rat</B> is <B>pretty ugly</B>. one possible XLIFF representation is the following: <unit id="1"> <segment> <source>This <pc id="1">naked mole rat</pc> is <pc id="2">pretty ugly</pc>.</source> <target>Cet <pc id="1">hétérocéphale</pc> est <pc id="2">plutôt laid</pc>.</target> </segment> </unit> In this option, the original data of the inline code is stored
in a structure that resides outside the content (i.e. outside The structure is an element For example, for the following HTML content: This <B>naked mole rat</B> is <B>pretty ugly</B>. The following XLIFF representation stores the original data: <unit id="1"> <segment> <source>This <pc id="1" dataRefStart="d1" dataRefEnd="d2">naked mole rat</pc> is <pc id="2" dataRefStart="d1" dataRefEnd="d2">pretty ugly</pc>.</source> <target>Cet <pc id="1" dataRefStart="d1" dataRefEnd="d2">hétérocéphale</pc> est <pc id="2" dataRefStart="d1" dataRefEnd="d2">plutôt laid</pc>.</target> </segment> <originalData> <data id="d1"><B></data> <data id="d2"></B></data> </originalData> </unit> NoteThis mechanism allows to re-use identical original data by
pointing to the same When processing a content, there are possible cases when new inline codes need to be added. For example, in the following HTML help content, the text has the name of a button in bold: Press the <b>Emergency Stop</b> button to interrupt the count-down sequence. In the translated version, the original label needs to remain in English because the user interface, unlike the help, is not translated. However, for convenience, a translation is also provided and emphasized using another style. That new formatting needs to be added: Appuyez sur le bouton <b>Emergency Stop</b> (<i>Arrêt d'urgence</i>) pour interrompre le compte à rebours. Having to split a single formatted span of text into several separate parts during translation, can serve as another example. For instance, the following sentence in Swedish uses bold on the names of two animals: Äter <b>katter möss</b>? But the English translation separates the two names and therefore needs to duplicate the bold codes. Do <b>cats</b> eat <b>mice</b>? Processing Requirements There are several ways to add codes: One way to create a new code is to duplicate an existing one (called the base code). If the base code is associated with some original data: the new code simply use these data. For example, the translation in the following unit, the second inline code is a duplicate of the first one: <unit id="1"> <segment> <source>Äter <pc id="1" dataRefStart="d1" dataRefEnd="d2">katter möss</pc>?</source> <target>Do <pc id="1" dataRefStart="d1" dataRefEnd="d2">cats</pc> eat <pc id="2" dataRefStart="d1" dataRefEnd="d2">mice</pc>?</target> </segment> <originalData> <data id="d1"><b></data> <data id="d2"></b></data> </originalData> </unit> If the base code has no associated data, the new code MUST use
the For example, the translation in the following unit, the second inline code is a duplicate of the first one: <unit id="1"> <segment> <source>Esznek <pc id="1">a magyarok svéd húsgombócot</pc>?</source> <target>Do <pc id="1">Hungarians</pc> eat <pc id="2" copyOf="1">Swedish meatballs</pc>?</target> </segment> </unit> Another way to add a code is to create it from scratch. For example, this can happen when the translated text requires additional formating. For example, in the following unit, the UI text needs to stay in English, and is also translated into French as an hint for the reader. The French translation for the UI text is formatted in italics: <unit id="1"> <segment> <source>Press the <pc id="1" dataRefStart="d1" dataRefEnd="d2">Emergency Stop</pc> button to interrupt the count-down sequence.</source> <target>Appuyez sur le bouton <pc id="1" dataRefStart="d1" dataRefEnd="d2">Emergency Stop</pc> (<pc id="2" dataRefStart="n2" dataRefEnd="n2">Arrêt d'urgence</pc>) pour interrompre le compte à rebours.</target> </segment> <originalData> <data id="d1"><b></data> <data id="d2"></b></data> <data id="n1"><i></data> <data id="n2"></i></data> </originalData> </unit> Another way to add a code is to convert part of the extracted text into code. In some cases the inline code can be created after extraction, using part of the text content. This can be done, for instance, to get better matches from an existing TM, or better candidates from an MT system. For example, it can happen that a tool extracting a Java properties file to XLIFF is not sophisticated enough to treat HTML or XML snippets inside the extracted text as inline code: # text property for the widget 'next' nextText: Click <ui>Next</ui> Resulting XLIFF content: <unit id="1"> <segment> <source>Click <ui>Next</ui></source> </segment> </unit> But another tool, later in the process, can be used to process
the initial XLIFF document and detect additional inline codes. For
instance here the XML elements such as The original data of the new code is the part of the text content that is converted as inline code. <unit id="1"> <segment> <source>Click <pc id="1" dataRefStart="d1" dataRefEnd="d2">Next</pc></source> </segment> <originalData> <data id="d1"><ui></data> <data id="d2"></ui></data> </originalData> </unit> WarningConverting XLIFF text content into original data for inline code might need a tool-specific process as the tool which did the initial extraction could have applied some conversion to the original content to create the XLIFF content (e.g. un-escape special characters). When processing a content, there are some possible cases when existing inline codes need to be removed. For an example the translation of a sentence can result in grouping of several formatted parts into a single one. For instance, the following sentence in English uses bold on the names of two animals: Do <b>cats</b> eat <b>mice</b>? But the Swedish translation group the two names and therefore needs only a single bolded part. Äter <b>katter möss</b>? Processing Requirements
There are several ways to remove codes: One way to remove a code is to delete it from the extracted content. For example, in the following unit, the translated text does not use the italics formatting. It is removed from the target content, but the original data are preserved because they are still used in the source content. <unit id="1">
<segment>
<source>I read <pc id="1" dataRefStart="d1" dataRefEnd="d2">Little
House on the Prairie</pc> to my children.</source>
<target>子供に「大草原の小さな家」を読みました。</target>
</segment>
<originalData>
<data id="d1"><i></data>
<data id="d2"></i></data>
</originalData>
</unit> Another way to remove an inline code is to convert it into text content. This is likely to be a rare use case. It is equivalant to deleting the code, with the addition to place the original data for the given code into the content, as text. This can be done, for example, to get better matches from an existing TM, or better candidates from an MT system. For instance, the following unit has an inline code corresponding to a variable place-holder. A tool can temporarily treat this variable as text to get better matches from an existing TM. <unit id="1"> <segment> <source>Cannot find '<ph id="1" dataRef="d1"/>'.</source> </segment> <originalData> <data id="d1">%s</data> </originalData> </unit> The modified unit would end up like as shown below. Note that because the original data was not associated with other inline code it has been removed from the unit: <unit id="1"> <segment> <source>Cannot find '%s'.</source> </segment> </unit> WarningConverting the original data of an inline code into text content might need a tool-specific process as the tool which did the initial extraction could have applied some conversion to the original content. XLIFF provides some information about what editing operations are applicable to inline codes:
Note that often those properties are related and appear together. For example, the code in the first unit shown below is a variable placeholder that has to be preserved and cannot be duplicated, and when several of such variables are present, as in the second unit, they cannot be re-ordered: <unit id="1"> <segment> <source>Can't open '<ph id="1" dataRef="d1" canCopy="no" canDelete="no"/>'.</source> </segment> <originalData> <data id="d1">%s</data> </originalData> </unit> <unit id="2"> <segment> <source>Number of <ph id="1" dataRef="d1" canCopy="no" canDelete="no" canReorder="no"/>: <ph id="2" dataRef="d2" canCopy="no" canDelete="no" canReorder="no"/>.</source> </segment> <originalData> <data id="d1">%s</data> <data id="d2">%d</data> </originalData> </unit> See the Target Content Modification section for additional details on editing. Constraints
Processing Requirements
An annotation is an element that associates a section of the content with some metadata information. Annotation MAY be created by the tool that generates the initial XLIFF document, or by any other user agent later in the process. For example, after a first tool creates the document, a second tool can annotate the source content with terminological information. Annotations are represented using the Processing Requirements
There are several pre-defined types of annotation and user agents can also define custom types. This annotation is used to indicate whether a span of content is translatable or not. Usage: For example: He saw his <mrk id="m1" translate="no">doppelgänger</mrk>. NoteThe He saw his <mrk id="m1" translate="no" type="term">doppelgänger</mrk>. This annotation is used to mark up a term in the content, and possibly associate information to it. Usage: For example: <unit id="1"> <segment> <source>He is my <mrk id="m1" type="term" ref="#g1">doppelgänger</mrk>.</source> <target>Il est mon <mrk id="m1" type="term" ref="#g1">alter ego</mrk>.</target> </segment> <gls:glossary> <gls:glossentry id="g1"> <gls:term>doppelgänger</gls:term> <gls:definition source="dictionary.com">A ghostly double or counterpart of a living person.</gls:definition> </gls:glossentry> </gls:glossary> </unit> This annotation is used to associate a span of content with a comment. Usage:
For example, here with the The <mrk id="m1" type="comment" value="Possible values: Printer or Stacker"><ph id="1" dataRef="d1"/></mrk> has been enabled. And here using the <unit id="1"> <segment> <source>You use your own namespace.</source> <target>Vous pouvez utiliser votre propre <mrk id="m1" type="comment" ref="#n1">namespace</mrk>.</target> <notes> <note id="n1" appliesTo="target">Please check the translation for 'namespace'. On also can use 'espace de nom', but I think most technical manuals use the English term.</note> </notes> </segment> </unit> The A custom annotation MUST NOT provide the same functionality as a pre-defined annotation. Usage: For example: One of the earliest surviving works of literature is <mrk id="m1" type="myCorp:isbn" value="978-0-14-44919-8">The Epic of Gilgamesh</mrk>. Annotations can overlap spanning inline codes or other
annotations. They also can be split by segmentation. Because of this, a
single annotation span can be represented using a pair of For example, one can have the following content: <unit id="1"> <segment> <source>Sentence A. <mrk id="m1" type="comment" value="Comment for B and C">Sentence B. Sentence C.</mrk></source> </segment> </unit> After a user agent performs segmentation, the annotation element
<unit id="1"> <segment> <source>Sentence A. </source> </segment> <segment> <source><sm id="m1" type="comment" value="Comment for B and C"/>Sentence B. </source> </segment> <segment> <source>Sentence C.<em startRef="m1"/></source> </segment> </unit> A sub-flow is a section of text embedded inside an inline code, or inside another section of text. For example, the following HTML content includes two sub-flows: The
first one is the value of the Click to start: <img title="Start button" src="" alt="Click here to start!"/> Another example is the following DITA content where the footnote
" Palouse horses<fn>A Palouse horse is the same as an Appaloosa.</fn> have spotted coats. In XLIFF, each sub-flow is stored in its own Therefore the HTML content of the example above can be represented like below: <unit id="1"> <segment> <source>Start button</source> </segment> </unit> <unit id="2"> <segment> <source>Click here to start!</source> </segment> </unit> <unit id="3"> <segment> <source>Click to start: <ph id="1" subFlows="1 2"/></source> </segment> </unit> Processing Requirements
While white spaces can be significant or insignificant in the original format, they are always treated as significant when stored as original data in XLIFF. Processing Requirements
Text directionality in XLIFF content is defined by inheritance. Source and target content can have different directionality. The initial directionality for both the source and the target
content is defined in the The The The The Adding bidirectional information in the text content is done using the Unicode bidirectional control characters [UAX #9]. In addition, the This section defines the rules tools need to follow when working with the target content of a given segment in order to provide interoperability throughout the whole process. The extraction tool can create the initial target content as it sees fit. The merging tool is assumed to have the same level of processing and native format knowledge as the extraction tool. Providing an interoperable way to convert native documents into XLIFF with one tool and back to the native format with another tool without the same level of knowledge is outside the scope of this specification. The user agents modifying the target content of a document between the extraction and the merging tools ensure interoperability by applying specific rules. These rules are separated into two cases: When there is an existing target and when there is no existing target. When there is no existing target, the processing requirements for a given segment are the following: Processing Requirements
When working with a segment with content already in the target, user agents MUST choose one of the three behaviors described below: Processing Requirements
This specification defines two types of content equality:
A content is normalized when:
XLIFF 2.0 offers two mechanisms for storing custom data in an XLIFF document:
Both mechanisms can be used simultaneously. The following elements allow storing custom data in
Custom extensions using
The following elements accept custom attributes:
In the context of XLIFF, a segment is a content which is either a unit of extracted text, or has been created from a unit of extracted text by means of a segmentation mechanism such as sentence boundary detection. For example, a segment can be a title, the text of a menu item, a paragraph or a sentence in a paragraph. In the context of XLIFF, other types representations sometimes called "segmentation" can be represented using annotations. For example: the terms in a segment can be identified and marked up using the term annotation. XLIFF does not specify how segmentation is carried out, only how to represent its result. The Segmentation Rules eXchange standard [SRX] provides detailed information about segmenting a content. In XLIFF each segment is represented by a A Each Content parts between segments are represented with the For example: <unit id="1"> <segment> <source>First sentence.</source> <target>Première phrase.</target> </segment> <ignorable> <source> </source> </ignorable> <segment> <source>Second sentence.</source> </segment> </unit> Some applications (e.g. aligner tools) may create segmented content where the target segments are not in the same order as the source. To be able to map order differences, the For example, the following HTML documents have the same paragraph with three sentences in different order: <p lang='en'>Sentence A. Sentence B. Sentence C.</p> <p lang='fr'>Phrase B. Phrase C. Phrase A.</p> The XLIFF representation of the content, after segmentation and alignment, would be: <unit id="1"> <segment id="1"> <source>Sentence A.</source> <target order="5">Phrase A.</target> </segment> <ignorable> <source> </source> </ignorable> <segment id="2"> <source>Sentence B.</source> <target order="1">Phrase B.</target> </segment> <ignorable> <source> </source> </ignorable> <segment id="3"> <source>Sentence C.</source> <target order="3">Phrase C.</target> </segment> </unit> Segments within the same When modifying the segmentation, the user agents must make sure the integrity of the relations between segments and associated data (such as candidate translations, comments, etc.) is preserved. Processing Requirements
Appendix A XML Schemas and CatalogThe grammar of XLIFF 2.0 is defined using eight (8) XML Schemas and one (1) XML catalog. The module schemas are referenced from their respective modules.
The catalog listed below for reading convenience is accessible at http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/schemas/catalog.xml. <?xml version="1.0" encoding="UTF-8"?> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> <uri name="urn:oasis:names:tc:xliff:document:2.0" uri="xliff_core_2.0.xsd"/> <uri name="urn:oasis:names:tc:xliff:changetracking:2.0" uri="modules/change_tracking.xsd"/> <uri name="urn:oasis:names:tc:xliff:glossary:2.0" uri="modules/glossary.xsd"/> <uri name="urn:oasis:names:tc:xliff:matches:2.0" uri="modules/matches.xsd"/> <uri name="urn:oasis:names:tc:xliff:metadata:2.0" uri="modules/metadata.xsd"/> <uri name="urn:oasis:names:tc:xliff:resourcedata:2.0" uri="modules/resource_data.xsd"/> <uri name="urn:oasis:names:tc:xliff:sizerestriction:2.0" uri="modules/size_restriction.xsd"/> <uri name="urn:oasis:names:tc:xliff:validation:2.0" uri="modules/validation.xsd"/> </catalog> The schema listed below for reading convenience is accessible at http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/schemas/xliff_core_2.0.xsd. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:xlf="urn:oasis:names:tc:xliff:document:2.0" xmlns:ctr="urn:oasis:names:tc:xliff:changetracking:2.0" xmlns:fs="urn:oasis:names:tc:xliff:fs:2.0" xmlns:gls="urn:oasis:names:tc:xliff:glossary:2.0" xmlns:mtc="urn:oasis:names:tc:xliff:matches:2.0" xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0" xmlns:res="urn:oasis:names:tc:xliff:resourcedata:2.0" xmlns:slr="urn:oasis:names:tc:xliff:sizerestriction:2.0" xmlns:val="urn:oasis:names:tc:xliff:validation:2.0" targetNamespace="urn:oasis:names:tc:xliff:document:2.0"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:import namespace="urn:oasis:names:tc:xliff:changetracking:2.0" schemaLocation="modules/change_tracking.xsd"/> <xs:import namespace="urn:oasis:names:tc:xliff:glossary:2.0" schemaLocation="modules/glossary.xsd"/> <xs:import namespace="urn:oasis:names:tc:xliff:matches:2.0" schemaLocation="modules/matches.xsd"/> <xs:import namespace="urn:oasis:names:tc:xliff:metadata:2.0" schemaLocation="modules/metadata.xsd"/> <xs:import namespace="urn:oasis:names:tc:xliff:resourcedata:2.0" schemaLocation="modules/resource_data.xsd"/> <xs:import namespace="urn:oasis:names:tc:xliff:sizerestriction:2.0" schemaLocation="modules/size_restriction.xsd"/> <xs:import namespace="urn:oasis:names:tc:xliff:validation:2.0" schemaLocation="modules/validation.xsd"/> <!-- Attribute definitions --> <xs:simpleType name="yesNo"> <xs:restriction base="xs:string"> <xs:enumeration value="yes"/> <xs:enumeration value="no"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="dirValue"> <xs:restriction base="xs:string"> <xs:enumeration value="ltr"/> <xs:enumeration value="rtl"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="appliesTo"> <xs:restriction base="xs:string"> <xs:enumeration value="source"/> <xs:enumeration value="target"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="userDefinedValue"> <xs:restriction base="xs:string"> <xs:pattern value="[^\s:]+:[^\s:]+"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="attrType_type"> <xs:restriction base="xs:string"> <xs:pattern value="(fmt|quot|link|image|other)"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="typeForMrkValues"> <xs:restriction base="xs:NMTOKEN"> <xs:enumeration value="generic"/> <xs:enumeration value="comment"/> <xs:enumeration value="term"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="attrType_typeForMrk"> <xs:union memberTypes="xlf:typeForMrkValues xlf:userDefinedValue"/> </xs:simpleType> <!-- Structural elements --> <xs:element name="xliff"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="xlf:file"/> </xs:sequence> <xs:attribute name="version" fixed="2.0" use="required"/> <xs:attribute name="srcLang" use="required"/> <xs:attribute name="trgLang" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="file"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" ref="xlf:skeleton"/> <xs:element minOccurs="0" maxOccurs="1" ref="xlf:notes"/> <xs:element minOccurs="0" maxOccurs="1" ref="mda:metadata"/> <xs:element minOccurs="0" maxOccurs="unbounded" ref="res:resourceData"/> <xs:element minOccurs="0" maxOccurs="1" ref="slr:profiles"/> <xs:element minOccurs="0" maxOccurs="1" ref="slr:data"/> <xs:element minOccurs="0" maxOccurs="1" ref="validation:validation"/> <xs:choice minOccurs="1" maxOccurs="unbounded"> <xs:element ref="xlf:unit"/> <xs:element ref="xlf:group"/> </xs:choice> <xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/> </xs:sequence> <xs:attribute name="id" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="original" use="optional"/> <xs:attribute name="srcDir" use="optional" type="xlf:dirValue"/> <xs:attribute name="trgDir" use="optional" type="xlf:dirValue"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> <xs:attribute ref="slr:storageRestriction" use="optional"/> <xs:attribute ref="slr:sizeRestriction" use="optional"/> <xs:attribute ref="slr:sizeInfo" use="optional"/> <xs:attribute ref="slr:sizeInfoRef" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="skeleton"> <xs:complexType mixed="true"> <xs:sequence> <xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="group"> <xs:complexType> <xs:sequence> <xs:choice minOccurs="1" maxOccurs="unbounded"> <xs:element ref="xlf:unit"/> <xs:element ref="xlf:group"/> </xs:choice> <xs:element minOccurs="0" maxOccurs="1" ref="xlf:notes"/> <xs:element minOccurs="0" maxOccurs="1" ref="mda:metadata"/> <xs:element minOccurs="0" maxOccurs="1" ref="slr:data"/> <xs:element minOccurs="0" maxOccurs="1" ref="validation:validation"/> <xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/> </xs:sequence> <xs:attribute name="id" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="name" use="optional"/> <xs:attribute name="srcDir" use="optional" type="xlf:dirValue"/> <xs:attribute name="trgDir" use="optional" type="xlf:dirValue"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> <xs:attribute ref="slr:storageRestriction" use="optional"/> <xs:attribute ref="slr:sizeRestriction" use="optional"/> <xs:attribute ref="slr:sizeInfo" use="optional"/> <xs:attribute ref="slr:sizeInfoRef" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="unit"> <xs:complexType> <xs:sequence> <xs:choice minOccurs="1" maxOccurs="unbounded"> <xs:element ref="xlf:segment"/> <xs:element ref="xlf:ignorable"/> </xs:choice> <xs:element minOccurs="0" maxOccurs="1" ref="xlf:notes"/> <xs:element minOccurs="0" maxOccurs="1" ref="xlf:originalData"/> <xs:element minOccurs="0" maxOccurs="1" ref="mtc:matches"/> <xs:element minOccurs="0" maxOccurs="1" ref="gls:glossary"/> <xs:element minOccurs="0" maxOccurs="1" ref="mda:metadata"/> <xs:element minOccurs="0" maxOccurs="1" ref="slr:data"/> <xs:element minOccurs="0" maxOccurs="1" ref="validation:validation"/> <xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/> </xs:sequence> <xs:attribute name="id" use="required" type="xs:NMTOKEN"/> <xs:attribute name="name" use="optional" /> <xs:attribute name="translate" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="srcDir" use="optional" type="xlf:dirValue"/> <xs:attribute name="trgDir" use="optional" type="xlf:dirValue"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> <xs:attribute ref="slr:storageRestriction" use="optional"/> <xs:attribute ref="slr:sizeRestriction" use="optional"/> <xs:attribute ref="slr:sizeInfo" use="optional"/> <xs:attribute ref="slr:sizeInfoRef" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="segment"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" ref="xlf:source"/> <xs:element minOccurs="0" maxOccurs="1" ref="xlf:target"/> </xs:sequence> <xs:attribute name="id" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="translate" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="approved" type="xlf:yesNo" default="no"/> <xs:attribute name="state" use="optional" default="initial"/> <xs:attribute name="subState" use="optional"/> </xs:complexType> </xs:element> <xs:element name="ignorable"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" ref="xlf:source"/> <xs:element minOccurs="0" maxOccurs="1" ref="xlf:target"/> </xs:sequence> <xs:attribute name="id" use="optional" type="xs:NMTOKEN"/> </xs:complexType> </xs:element> <xs:element name="originalData"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="xlf:data"/> </xs:sequence> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> </xs:complexType> </xs:element> <xs:element name="data"> <xs:complexType mixed="true"> <xs:sequence> <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:cp"/> </xs:sequence> <xs:attribute name="id" use="required" type="xs:NMTOKEN"/> <xs:attribute name="dir" use="optional" type="xlf:dirValue"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> </xs:complexType> </xs:element> <xs:element name="notes"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="xlf:note"/> </xs:sequence> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> </xs:complexType> </xs:element> <xs:element name="note"> <xs:complexType mixed="true"> <xs:attribute name="id" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="appliesTo" use="optional" type="xlf:appliesTo"/> <xs:attribute name="category" use="optional"/> <xs:attribute name="priority" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> </xs:complexType> </xs:element> <xs:element name="source"> <xs:complexType mixed="true"> <xs:group ref="xlf:inline" minOccurs="0" maxOccurs="unbounded"/> <xs:attribute ref="xml:lang" use="optional"/> <xs:attribute ref="xml:space" use="optional"/> <xs:attribute name="dir" use="optional" type="xlf:dirValue"/> </xs:complexType> </xs:element> <xs:element name="target"> <xs:complexType mixed="true"> <xs:group ref="xlf:inline" minOccurs="0" maxOccurs="unbounded"/> <xs:attribute ref="xml:lang" use="optional"/> <xs:attribute ref="xml:space" use="optional"/> <xs:attribute name="dir" use="optional" type="xlf:dirValue"/> </xs:complexType> </xs:element> <!-- Inline elements --> <xs:group name="inline"> <xs:choice> <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:sc"/> <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:ec"/> <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:ph"/> <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:pc"/> <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:cp"/> <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:mrk"/> <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:sm"/> <xs:element minOccurs="0" maxOccurs="unbounded" ref="xlf:em"/> </xs:choice> </xs:group> <xs:element name="sc"> <!-- Start Code --> <xs:complexType mixed="false"> <xs:attribute name="canCopy" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="canDelete" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="canOverlap" use="optional" type="xlf:yesNo"/> <xs:attribute name="canReorder" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="copyOf" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="disp" use="optional"/> <xs:attribute name="equiv" use="optional"/> <xs:attribute name="id" use="required" type="xs:NMTOKEN"/> <xs:attribute name="isolated" use="optional" type="xlf:yesNo" default="no"/> <xs:attribute name="dataRef" use="optional"/> <xs:attribute name="subFlows" use="optional" type="xs:NMTOKENS"/> <xs:attribute name="subType" use="optional" type="xlf:userDefinedValue"/> <xs:attribute name="type" use="optional" type="xlf:attrType_type"/> <xs:attribute name="dir" use="optional" type="xlf:dirValue"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> <xs:attribute ref="slr:storageRestriction" use="optional"/> <xs:attribute ref="slr:sizeRestriction" use="optional"/> <xs:attribute ref="slr:equivStorage" use="optional"/> <xs:attribute ref="slr:sizeInfo" use="optional"/> <xs:attribute ref="slr:sizeInfoRef" use="optional"/> </xs:complexType> </xs:element> <xs:element name="ec"> <!-- End Code --> <xs:complexType mixed="false"> <xs:attribute name="canCopy" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="canDelete" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="canOverlap" use="optional" type="xlf:yesNo"/> <xs:attribute name="canReorder" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="copyOf" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="disp" use="optional"/> <xs:attribute name="equiv" use="optional"/> <xs:attribute name="id" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="isolated" use="optional" type="xlf:yesNo" default="no"/> <xs:attribute name="dataRef" use="optional"/> <xs:attribute name="startRef" use="optional"/> <xs:attribute name="subFlows" use="optional" type="xs:NMTOKENS"/> <xs:attribute name="subType" use="optional" type="xlf:userDefinedValue"/> <xs:attribute name="type" use="optional" type="xlf:attrType_type"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> <xs:attribute ref="slr:equivStorage" use="optional"/> <xs:attribute ref="slr:sizeInfo" use="optional"/> <xs:attribute ref="slr:sizeInfoRef" use="optional"/> </xs:complexType> </xs:element> <xs:element name="ph"> <!-- Placeholder --> <xs:complexType mixed="false"> <xs:attribute name="canCopy" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="canDelete" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="canReorder" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="copyOf" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="disp" use="optional"/> <xs:attribute name="equiv" use="optional"/> <xs:attribute name="id" use="required" type="xs:NMTOKEN"/> <xs:attribute name="dataRef" use="optional"/> <xs:attribute name="subFlows" use="optional" type="xs:NMTOKENS"/> <xs:attribute name="subType" use="optional" type="xlf:userDefinedValue"/> <xs:attribute name="type" use="optional" type="xlf:attrType_type"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> <xs:attribute ref="slr:equivStorage" use="optional"/> <xs:attribute ref="slr:sizeInfo" use="optional"/> <xs:attribute ref="slr:sizeInfoRef" use="optional"/> </xs:complexType> </xs:element> <xs:element name="pc"> <!-- Paired Code --> <xs:complexType mixed="true"> <xs:group ref="xlf:inline" minOccurs="0" maxOccurs="unbounded"/> <xs:attribute name="canCopy" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="canDelete" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="canOverlap" use="optional" type="xlf:yesNo"/> <xs:attribute name="canReorder" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="copyOf" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="dispEnd" use="optional"/> <xs:attribute name="dispStart" use="optional"/> <xs:attribute name="equivEnd" use="optional"/> <xs:attribute name="equivStart" use="optional"/> <xs:attribute name="id" use="required" type="xs:NMTOKEN"/> <xs:attribute name="dataRefEnd" use="optional"/> <xs:attribute name="dataRefStart" use="optional"/> <xs:attribute name="subFlowsEnd" use="optional" type="xs:NMTOKENS"/> <xs:attribute name="subFlowsStart" use="optional" type="xs:NMTOKENS"/> <xs:attribute name="subType" use="optional" type="xlf:userDefinedValue"/> <xs:attribute name="type" use="optional" type="xlf:attrType_type"/> <xs:attribute name="dir" use="optional" type="xlf:dirValue"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> <xs:attribute ref="slr:storageRestriction" use="optional"/> <xs:attribute ref="slr:sizeRestriction" use="optional"/> <xs:attribute ref="slr:equivStorage" use="optional"/> <xs:attribute ref="slr:sizeInfo" use="optional"/> <xs:attribute ref="slr:sizeInfoRef" use="optional"/> </xs:complexType> </xs:element> <xs:element name="cp"> <!-- Code Point --> <xs:complexType mixed="false"> <xs:attribute name="hex" use="required"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> </xs:complexType> </xs:element> <xs:element name="mrk"> <!-- Annotation Marker --> <xs:complexType mixed="true"> <xs:group ref="xlf:inline" minOccurs="0" maxOccurs="unbounded"/> <xs:attribute name="id" use="required" type="xs:NMTOKEN"/> <xs:attribute name="translate" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="type" use="optional" type="xlf:attrType_type"/> <xs:attribute name="ref" use="optional" type="xs:anyURI"/> <xs:attribute name="value" use="optional"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> <xs:attribute ref="slr:storageRestriction" use="optional"/> <xs:attribute ref="slr:sizeRestriction" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="sm"> <!-- Start Annotation Marker --> <xs:complexType mixed="false"> <xs:attribute name="id" use="required" type="xs:NMTOKEN"/> <xs:attribute name="translate" use="optional" type="xlf:yesNo" default="yes"/> <xs:attribute name="type" use="optional" type="xlf:attrType_type"/> <xs:attribute name="ref" use="optional" type="xs:anyURI"/> <xs:attribute name="value" use="optional"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> <xs:attribute ref="slr:storageRestriction" use="optional"/> <xs:attribute ref="slr:sizeRestriction" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="em"> <!-- End Annotation Marker --> <xs:complexType mixed="false"> <xs:attribute name="startRef" use="required"/> <xs:attribute ref="fs:fs" use="optional"/> <xs:attribute ref="fs:subFs" use="optional"/> </xs:complexType> </xs:element> </xs:schema> Appendix B Translation Candidates ModuleThe source text of a document can be pre-processed against various translation resources (TM, MT, etc.) to provide translation candidates. This module provides an XLIFF capability to store lists of possible translations along with information about the similarity of the match, the quality of the translation, its provenance, etc. The namespace for the Translation Candidates module is: The elements defined in the Translation Candidates module are:
Legend:
Collection of matches retrieved from any leveraging system (MT, TM, etc.) Contains:
A potential translation suggested for the enclosing
Contains:
Attributes:
The attributes defined in the Translation Candidates module are: Identifier - A character string used to identify a Value description: NMTOKEN. Default value: undefined The value must be unique within the Used in: Similarity - indicates the similarity level between the content of the
Value description: a decimal number between 0.0 and 100.0. Default value: undefined Used in: Match quality - indicates the quality of the Value description: a decimal number between 0.0 and 100.0. Default value: undefined Used in: NoteThis attribute can carry a human review based metrics score, a Machine Translation self-reported confidence score etc. Match suitability - indicates the general suitability and relevance of its
This attribute is intended to carry a value that can be combined from values provided in
Value description: a decimal number between 0.0 and 100.0. Default value: undefined Used in: NoteThis attribute is also useful for mapping match-quality as specified in XLIFF 1.2. Processing Requirements
Match origin - indicates the tool, system or repository that generated a Value description: Text. Default value: undefined Used in: Type - Indicates the type of a Value description: Table B.1. Standard Values
Used in: Subtype - Indicates the subtype, i.e. a secondary level type, of a Value description: The value is composed of a prefix and a sub-value separated by a character : (U+003A). The prefix is a string uniquely identifying a collection of values for a specific authority. The sub-value is any string value defined by an authority. The prefix xlf is reserved for this specification, but no sub-values are defined for it at this time. Other prefixes and sub-values may be defined by the users.
Used in: The schema listed below for reading convenience is accessible at http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/schemas/modules/matches.xsd. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:mtc="urn:oasis:names:tc:xliff:matches:2.0" xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0" xmlns:xlf="urn:oasis:names:tc:xliff:document:2.0" targetNamespace="urn:oasis:names:tc:xliff:matches:2.0"> <xs:import namespace="urn:oasis:names:tc:xliff:document:2.0" schemaLocation="../xliff_core_2.0.xsd"/> <xs:import namespace="urn:oasis:names:tc:xliff:metadata:2.0" schemaLocation="metadata.xsd"/> <xs:simpleType name="similarity"> <xs:restriction base="xs:decimal"> <xs:minInclusive value="0.0"/> <xs:maxInclusive value="100.0"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="typeValues"> <xs:restriction base="xs:string"> <xs:enumeration value="am"/> <xs:enumeration value="ebm"/> <xs:enumeration value="idm"/> <xs:enumeration value="ice"/> <xs:enumeration value="mt"/> <xs:enumeration value="tm"/> </xs:restriction> </xs:simpleType> <!-- Elements for holding translaton candidates --> <xs:element name="matches"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="mtc:match"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="match"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" ref="xlf:source"/> <xs:element minOccurs="1" maxOccurs="1" ref="xlf:target"/> <xs:element minOccurs="0" maxOccurs="1" ref="xlf:originalData"/> <xs:element minOccurs="0" maxOccurs="1" ref="mda:metadata"/> </xs:sequence> <xs:attribute name="id" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="type" use="optional" type="mtc:typeValues"/> <xs:attribute name="origin" use="optional"/> <xs:attribute name="similarity" use="optional" type="mtc:similarity"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> </xs:schema> Appendix C Glossary ModuleSimple glossaries, consisting of a list of terms with a definition or translation, can be optionally embedded in an XLIFF document using the namespace mechanism to include elements from the Glossary module. The namespace for the Glossary module is: The elements defined in the Glossary module are:
Legend:
Glossary entry. Contains:
Attributes:
Constraints
A term in the glossary, expressed in the source language of the enclosing
Contains:
Attributes:
The attribues defined in the Glossary module are: Identifier - A character string used to identify a Value description: NMTOKEN Default value: undefined Used in: Source - Indicates the source of the content for the enclosing element. Value description: Text. Default value: undefined Used in: <unit id="1"> <segment> <source>Press the <mrk id="m1" type="term" ref="#g1">TAB key</mrk>.</source> </segment> <gls:glossary> <gls:glossentry id="g1"> <gls:term source="publicTermbase">TAB key</gls:term> <gls:translation id="1" source="myTermbase">Tabstopptaste</gls:translation> <gls:translation id="2" source="myTermbase">TAB-TASTE</gls:translation> <gls:definition source="publicTermbase">A keyboard key that is traditionally used to insert tab characters into a document.</gls:definition> </gls:glossentry> </gls:glossary> </unit> The schema listed below for reading convenience is accessible at http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/schemas/modules/glossary.xsd. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:gls="urn:oasis:names:tc:xliff:glossary:2.0" targetNamespace="urn:oasis:names:tc:xliff:glossary:2.0"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <!-- Elements for holding simple glossary data --> <xs:element name="glossary"> <xs:complexType mixed="false"> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="gls:glossentry" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="glossentry"> <xs:complexType mixed="false"> <xs:sequence> <xs:element minOccurs="1" maxOccurs="1" ref="gls:term"/> <xs:element minOccurs="0" maxOccurs="1" ref="gls:translation" /> <xs:element minOccurs="0" maxOccurs="1" ref="gls:definition" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="term"> <xs:complexType mixed="true"/> </xs:element> <xs:element name="translation"> <xs:complexType mixed="true"/> </xs:element> <xs:element name="definition"> <xs:complexType mixed="true"> <xs:attribute name="source" use="required" /> </xs:complexType> </xs:element> </xs:schema> Appendix D Format Style ModuleThis is intended as a namespace mechanism to carry inside an XLIFF document information needed for generating a quick at a glance html preview of XLIFF content using a predefined set of simple html formatting elements. Format Style module consists of just two attributes: Format Style allows most structural and inline XLIFF core elements to convey basic formatting information using a predefined subset of HTML formatting elements. It primarily enables the generation of HTML pages or snippets for preview and review purposes. It MUST not be used to prescibe a roundtrip to a source document format. The Constraints Processing Requiremenets
NoteThe above constraint and validation method will make sure that the snippets are renderable by standard HTML browsres. The attributes defined in the Format Style module are:
Format style attribute, fs - allows most structural and inline XLIFF core elements to convey
basic formatting information using a predefined subset of HTML formatting elements (for example,
HTML elements names like <script> are not included). It enables the generation of HTML pages
or snippets for preview and review purposes. This attribute is not intended to facilitate round-tripping back into the original
format. If additional style information is needed, the optional Value description: Table D.1. fs attribute values
Default value: undefined. Used in:
Example:To facilitate HTML preview, fs can be applied to XLIFF like this like: <xliff> <file fs:fs="html"> <unit id="1" fs:fs="p"> <segment> <source>Mick Jones renewed his interest in the Vintage <pc id="1" fs:fs="strong">'72 Telecaster Thinline </pc> guitar. <x fs:fs="br" />He says <pc fs:fs="q">I love 'em</pc> <x fs:fs="img" fs:subFs="src,smileface.png" /></source> </segment> </unit> </file> </xliff> With an XSL stylesheet like this: <xsl:template match="*" priority="2"> <xsl:choose> <xsl:when test="@fs:fs"> <xsl:element name="{@fs:fs}"> <xsl:if test="@fs:subFs"> <xsl:variable name="att_name" select="substring-before(@fs:subFs,',')" /> <xsl:variable name="att_val" select="substring-after(@fs:subFs,',')" /> <xsl:attribute name="{$att_name}"> <xsl:value-of select="$att_val" /> </xsl:attribute> </xsl:if> <xsl:apply-templates /> </xsl:element> </xsl:when> <xsl:otherwise> <xsl:apply-templates /> </xsl:otherwise> </xsl:choose> </xsl:template> You can generate a an HTML page like this: <html> <p>Mick Jones renewed his interest in the Vintage <strong>'72 Telecaster Thinline </strong> guitar. <br/>He says <q>I love 'em</q> <img src=""/> </p> </html> Sub-format style, subFs - allows extra metadata, like URL for example, to be added in concert
with the The subFs MUST only be used to carry attribute name/value
comma-delimited pairs for attributes that are valid for the HTML element identified by the
accompanying fs. Example: Commas (,) and backslashes (\) in the value part of the pair must be escaped with a backslash. The Value description: IRI. Default value: undefined. Used in:
Appendix E Metadata ModuleThe Metadata module provides a mechanism for storing custom metadata using elements that are part of the official XLIFF specification. The namespace for the Metadata module is: The elements defined in the Metadata module are: Legend:
Container for metadata associated with the enclosing element. Example:Metadata can be used to store XML attribute names and values
for XLIFF files that do not use a skeleton. The following XML sample contains attributes on
the <document version="3" phase="draft"> <table> <row style="head"><cell>Name</cell><cell>Position</cell></row> <row><cell>Patrick K.</cell><cell>Right Wing</cell></row> <row><cell>Bryan B.</cell><cell>Left Wing</cell></row> </table> </document> To preserve these attribute for a round trip, without using a skeleton, the Metadata module may be used. <?xml version="1.0" encoding="utf-8"?> <xliff xmlns:fs="urn:oasis:names:tc:xliff:fs:2.0" xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0" version="2.0" srcLang="en"> <file> <group name="document"> <group name="table"> <group name="row"> <unit id="u1" name="cell"> <segment> <source>Name</source> </segment> </unit> <unit id="u2" name="cell"> <segment> <source>Position</source> </segment> </unit> <mda:metadata> <mda:metagroup category="row_xml_attribute"> <mda:meta type="style">head</mda:meta> </mda:metagroup> </mda:metadata> </group> <group name="row"> <unit id="u3" name="cell"> <segment> <source>Patrick K.</source> </segment> </unit> <unit id="u4" name="cell"> <segment> <source>Right Wing</source> </segment> </unit> </group> <group name="row"> <unit id="u5" name="cell"> <segment> <source>Bryan B.</source> </segment> </unit> <unit id="u6" name="cell"> <segment> <source>Left Wing</source> </segment> </unit> </group> </group> <mda:metadata> <mda:metagroup category="document_xml_attribute"> <mda:meta type="version">3</mda:meta> <mda:meta type="phase">draft</mda:meta> </mda:metagroup> </mda:metadata> </group> </file> </xliff> Contains:
Provides a way to organize metadata into a structured hierarchy. Contains:
Attributes
The attribues defined in the Metadata module are:
category - indicates a category for metadata contained in the enclosing Default value: Used in: type - indicates the type of metadata contained by the enclosing element. Default value: Used in: Indicates the element to whom the content of the matagroup applies. Value description: Default value: undefined. Used in: The schema listed below for reading convenience is accessible at http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/schemas/modules/metadata.xsd. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:mda="urn:oasis:names:tc:xliff:metadata:2.0" targetNamespace="urn:oasis:names:tc:xliff:metadata:2.0"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <!-- Elements for holding custom metadata --> <xs:element name="metadata"> <xs:complexType mixed="false"> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="mda:metagroup" /> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="metagroup"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="mda:meta" /> </xs:sequence> <xs:attribute name="category" use="optional"/> </xs:complexType> </xs:element> <xs:element name="meta"> <xs:complexType mixed="true"> <xs:attribute name="type" use="required" type="xlf:attrType_type"/> </xs:complexType> </xs:element> </xs:schema> Appendix F Resource Data ModuleThe Resource Data module provides a mechanism for referencing external resource data that MAY need to be modified or used as contextual reference during translation. The namespace for the Resource Data module is: The elements defined in the Resource Data module are: Legend:
Parent container for resource data associated with the enclosing element. Contains: At least one of the following
Specifies a reference to an associated Contains:
Attributes:
Constraints
Processing Requirements
Container for specific resource data that may need to be modified or used as contextual reference during translation. Contains: At least one of the following
Attributes:
Constraints
Processing Requirements
References the actual resource data that may need to be modified or used as contextual reference during translation. Contains: Either
or
Attributes:
The following attribute MUST be used if and only if
Processing Requirements
References the localized counterpart of the sibling Contains: Either
or
Attributes:
The following attribute MUST be used if and only if
Processing Requirements
References contextual data relating to the sibling Contains:
Attributes:
Constraints Processing Requirements
The attributes defined in the Resource Data module are: Identifier - A character string used to identify a Value description: NMTOKEN Default value: undefined Used in: Language - The xml:lang attribute specifies the language variant of the text of a given element.
For example: Value description: A language code as described in [BCP 47]. Default value: undefined Used in: MIME type, mimeType - indicates the type of a resource object. This generally corresponds to the content type of [RFC 2045], the MIME specification; e.g. mimeType="text/xml" indicates the resource data is a text file of XML format. Value description: A MIME type. An existing MIME type MUST be used from a list of standard values. Default value: undefined Used in: NoteIf you cannot use any of the standard MIME type values as specified above, a new MIME type can be registered according to [RFC 2048]. Contextual Information - Indicates whether an external resource is to be used for context only and not modified. Value description: yes or no Default value: yes Used in: Hypertext Reference, href - IRI referencing an external resource. Value description: IRI. Default value: undefined Used in: Resource Item Reference - Holds a reference to an associated Value description: An XSD NMTOKEN that must be the value of the id attribute of the Default value: undefined Used in: In this example, the <file> <res:resourceData> <res:resourceItem id="r1" mimeType="text/xml" context="no"> <res:source href="" /> <res:target href="" /> </res:resourceItem> </res:resourceData> <unit id="1" name="130;WIN_DLG_CTRL_"> <segment id="1" state="translated"> <source>Load Registry Config</source> <target>Registrierungskonfiguration laden</target> </segment> <res:resourceData> <res:resourceItemRef ref="r1" /> </res:resourceData> </unit> </file> In this example, the <file> <unit id="1"> <segment id="1" state="translated"> <source>Load Registry Config</source> <target>Registrierungskonfiguration laden</target> </segment> <res:resourceData> <res:resourceItem id="r1" context="no"> <res:source> <abc:resourceType>button</abc:resourceType> <abc:resourceHeight>40</abc:resourceHeight> <abc:resourceWidth>75</abc:resourceWidth> </res:source> <res:target> <abc:resourceType>button</abc:resourceType> <abc:resourceHeight>40</abc:resourceHeight> <abc:resourceWidth>150</abc:resourceWidth> </res:target> </res:resourceItem> </res:resourceData> </unit> </file> In this example, the <file> <res:resourceData> <res:resourceItem id="r1" mimeType="image/jpeg" context="yes"> <res:source xml:lang="en-us" href="" /> <res:target xml:lang="lb-lu" href="" /> <res:reference xml:lang="de-de" href="" /> </res:resourceItem> <res:resourceItem id="r2" mimeType="image/jpeg" context="yes"> <res:source xml:lang="en-us" href="" /> <res:target xml:lang="lb-lu" href="" /> </res:resourceItem> </res:resourceData> <unit id="1"> <segment id="1" state="translated"> <source>Remove Registry Config</source> <target>Registrierungskonfiguration entfernen</target> </segment> <res:resourceData> <res:resourceItemRef ref="r1" /> <res:resourceItemRef ref="r2" /> </res:resourceData> </unit> </file> The schema listed below for reading convenience is accessible at http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/schemas/modules/resource_data.xsd. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:res="urn:oasis:names:tc:xliff:resourceData:2.0" targetNamespace="urn:oasis:names:tc:xliff:resourceData:2.0"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:element name="res_resourceData"> <xs:complexType> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" ref="res:source"/> <xs:element minOccurs="0" maxOccurs="1" ref="res:target"/> <xs:element minOccurs="0" maxOccurs="unbounded" ref="res:reference"/> </xs:sequence> <xs:attribute name="id" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="mimeType" use="required"/> <xs:attribute name="context" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="source"> <xs:complexType mixed="false"> <xs:attribute name="href" use="required"/> <xs:attribute ref="xml:lang" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="target"> <xs:complexType mixed="false"> <xs:attribute name="href" use="required"/> <xs:attribute ref="xml:lang" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="res_reference"> <xs:complexType mixed="false"> <xs:attribute name="href" use="required"/> <xs:attribute ref="xml:lang" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> </xs:schema> Appendix G Change Tracking ModuleThe Change Tracking module is used to store revision information for XLIFF elements and attributes. The namespace for the Change Tracking module is: The elements defined in the Change Tracking module are: Legend:
Parent container for change tracking information associated with a sibling element, or a child of a sibling element, to the change track module within the scope of the enclosing element. Contains:
Container for logical groups of revisions associated with a sibling element, or a child of a sibling element, to the change track module within the scope of the enclosing element. Contains:
Attributes:
Processing Requirements
Container for specific revisions associated with a sibling element, or a child of a sibling element, to the change track module within the scope of the enclosing element. Contains:
Attributes:
Processing Requirements
Container for a specific revision associated with a sibling element, or a child of a sibling element, to the change track module within the scope of the enclosing element. Contains:
Attributes:
Processing Requirements
The attributes defined in the Change Tracking module are: appliesTo – Indicates a specific XLIFF element which is a sibling, or a child of a sibling element, to the change track module within the scope of the enclosing element. Value description: Any valid XLIFF element which is a sibling, or a child of a sibling element, to the change track module within the scope of the enclosing element. Default value: undefined Used in: author - Indicates the user or agent that created or modified the referenced element or its attributes. Value description: Text. Default value: undefined Used in: currentVersion - Holds a reference to the most current version of a revision. Value description: An XSD NMTOKEN that must be the value of the Default value: none Used in: Date and Time, datetime - Indicates the date and time the referenced element or its attributes were created or modified. Value description: Date in one of the formats defined in [NOTE-datetime]. Default value: undefined Used in: Reference - Holds a reference to a single instance of an element that has multiple instances within the enclosing element. Value description: An XSD NMTOKEN that must be the value of the Default value: undefined Used in: property – Indicates the type of revision data. Value description: The value MUST be either Default value: none Used in: version - Indicates the version of the referenced element or its attributes that were created or modified. Value description: NMTOKEN. Default value: undefined Used in: The following example shows change tracking for <unit id="1"> <segment> <source>Hello World</source> <target>Guten Tag Welt</target> </segment> <notes> <note category="instruction" id="n1">The translation should be formal</note> <note category="comment" id="n2">Please Review my translation</note> </notes> <changeTrack> <revisions appliesTo="source" currentVersion="r1"> <revision author="system" datetime="2013-07-15T10:00:00+8:00" version="r1"> <item property="content">Hello World</item>> </revision> <revision author="system" datetime="2013-06-15T10:00:00+8:00" version="r2"> <item property="content">Hello</item>> </revision> <revision author="system" datetime="2013-05-15T10:00:00+8:00" version="r3"> <item property="content">Hi</item> </revision> </revisions> <revisions appliesTo="target" currentVersion="r1"> <revision author="Frank" datetime="2013-07-17T11:00:00+8:00" version="r1"> <item property="content">Guten Tag Welt</item> </revision> <revision author="Frank" datetime="2013-06-17T11:00:00+8:00" version="r2"> <item property="content">Hallo</item> </revision> <revision author="Frank" datetime="2013-05-17T11:00:00+8:00" version="r3"> <item property="content">Grüsse</item> </revision> </revisions> <revisions appliesTo="note" nid="n1" currentVersion="r1"> <revision author="Bob" datetime="2013-07-16T10:30:00+8:00" version="r1"> <item property="content">The translation should be formal</item> <item property="category">instruction</item> </revision> <revision author="Bob" datetime="2013-05-16T10:30:00+8:00" version="r2"> <item property="content">The translation should be informal</item> <item property="category">comment</item> </revision> </revisions> <revisions appliesTo="note" nid="n2" currentVersion="r1"> <revision author="Bob" datetime="2013-07-18T10:30:00+8:00" version="r1"> <item property="content">Please Review my translation</item> </revision> </revisions> </changeTrack> </unit> The schema listed below for reading convenience is accessible at http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/schemas/modules/change_tracking.xsd. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:ctr="urn:oasis:names:tc:xliff:changeTrack:2.0" targetNamespace="urn:oasis:names:tc:xliff:changeTrack:2.0"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:element name="changeTrack"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="ctr:revisions"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="revisions"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="ctr:revision"/> </xs:sequence> <xs:attribute name="appliesTo" use="required" type="xlf:appliesTo"/> <xs:attribute name="nid" use="optional" type="xs:NMTOKEN"/> <xs:attribute name="currentVersion" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="revision"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="ctr:item"/> </xs:sequence> <xs:attribute name="author" use="optional"/> <xs:attribute name="datetime" use="optional"/> <xs:attribute name="version" fixed="2.0" use="required"/> <xs:attribute name="checksum" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="item"> <xs:complexType mixed="true"> <xs:attribute name="property" use="required"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> </xs:schema> Appendix H Size Restriction ModuleThe Size Restriction module provides a mechanism to annotate the XLIFF content with information on storage and general size restrictions. The restriction framework has support for two distinct types of restrictions; storage
size restrictions and general size restriction. The reason for this is that it is often
common to have separate restrictions between storage and display / physical
representation of data. Since it would be impossible to define all restrictions here a
concept of restriction profile is introduced. The profiles for storage size and general
size are independent. The information related to restriction profiles are stored in the
processing invariant part of the XLIFF file like the The namespace for the Size and Length restriction module is:
The elements defined in the Size and Length restriction module are: This element selects the restriction profiles to use in the document. If no storage or general profile is specified the default values (empty) of those elements will disable restriction checking in the file. Contains:
Attributes:
Processing Requirements
This element is used to hold the attributes specifying normalization form to apply to storage and size restrictions defined in the standard profiles. Contains:
Attributes:
Processing Requirements
This elements act as a container for data needed by the specified profile to check the part of the XLIFF document that is a sibling or descendant of a sibling of this element. It is not used by the default profiles. Contains:
Attributes:
Processing Requirements
The attributes defined in the Size and Length restriction module are: This attribute specifies which profile should be used to check storage size restrictions. Empty means that no restrictions should be applied. Value description: Name of restriction profile to use for storage size restrictions. Default value: empty Used in: This attribute specifies which profile should be used to check general size restrictions. Empty means that no restrictions should be applied. Value description: Name of restriction profile to use for general size restrictions. Default value: empty Used in: This attribute specifies the normalization to apply for storage size restrictions. The only normalization forms C and D as specified by the Unicode Consortium are supported, see Unicode Standard Annex #15. Value description: normalization to apply. Table H.1. Values
Default value: "none" Used in: This attribute specifies the normalization to apply for general size restrictions. The only normalization forms C and D as specified by the Unicode Consortium are supported, see Unicode Standard Annex #15. Value description: normalization to apply. Table H.2. Values
Default value: "none" Used in: This attribute is used on the Value description: Name of a restriction profile Default value: undefined Used in: This attribute specifies the storage restriction to apply to the collection descendants of the element it is defined on. Value description: Interpretation of the value is dependent on selected Default value: undefined Used in:
This attribute specifies the size restriction to apply to the collection descendants of the element it is defined on. Value description: Interpretation of the value is dependent on selected Default value: undefined Used in:
This attribute provide a means to specify how much storaqge space an inline element will use in the native format. This size contribution is then added to the size contributed by the textual parts.
This attribute is only allowed on the Value description: Interpretation of the value is dependent on selected Default value: undefined This attribute is used to associate profile specific information to inline elements so that size information can be decoupled from the native format or represented when the native data is not available in the XLIFF document.
It can be used on both inline elements and structural elements to provide information on things like GUI dialog or control sizes, expected padding or margins to consider for size, what font is used for contained text and so on.
This attribute is only allowed on the Value description: Interpretation of the value is dependent on selected
Default value: undefined Used in:
Constraints
This attribute is used to point to data that provide the same function as the Value description: a reference to data that provide the same information that could be put in a Default value: undefined Restriction: at most one of this attribute and sizeInfo can occur. Both cannot be specified at the same time. Used in:
This profile implements a simple string length restriction based on the number of
Unicode code points. It is possible to specify if normalization should be applied
using the The value of this attribute holds the ”maximum” or ”minimum and maximum” size of the string. Either size must be an integer. The maximum size can also be ’*’ to denote that there is no maximum restriction. If only a maximum is specified it is implied that the minimum is 0 (empty string). The format of the value is the optional minimum size and a coma followed by a maximum size (”[minsize,]maxsize”). The default value is ’*’ which evaluates to a string with unbounded size. These three profiles define the standard size restriction profiles for the common
Unicode character encoding schemes. It is possible to specify if normalization
should be applied using the Table H.3. Profiles
These profiles make use of the following attributes from this module: The value of this attribute holds the ”maximum” or ”minimum and maximum” size of the string. Either size must be an integer. The maximum size can also be ’*’ to denote that there is no maximum restriction. If only a maximum is specified it is implied that the minimum is 0 (empty string). The format of the value is the optional minimum size and a coma followed by a maximum size (”[minsize,]maxsize”). The default value is ’*’ which evaluates to a string with unbounded size. The value of this attribute is an integer representing how many bytes the
element it is set on should be considered to contribute to the total size. If
empty the default is 0. The The general structure of this module together with the extensibility mechanisms provided, should lend itself to most size restriction schemes. For example to represent two dimensional data a profile might adopt using a coordinate style for the values of the general restriction attributes. Like ”{x,y}” to represent width and height or ”{{x1,y1},{x2,y2}}” to represent a bounding box. It should also be possible to embed information necessary to drive a display simulator and attach that data to text to do device specific checking. Or to provide font information and to glyph based general size checking. To claim conformance to the XLIFF size and length restriction module a tool must meet the following criteria.
The schema listed below for reading convenience is accessible at http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/schemas/modules/size_restriction.xsd. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:slr="urn:oasis:names:tc:xliff:sizerestriction:2.0" targetNamespace="urn:oasis:names:tc:xliff:sizerestriction:2.0"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <!-- Attributes for size and length restriction used on core elements--> <xs:attribute name="equiv-storage" type="xs:string"/> <xs:attribute name="size-info" type="xs:string"/> <xs:attribute name="size-info-ref" type="xs:NMTOKEN"/> <xs:attribute name="size-restriction" type="xs:string"/> <xs:attribute name="storage-restriction" type="xs:string"/> <!-- Elements for size and length restriction --> <xs:element name="profiles"> <xs:complexType mixed="false"> <xs:sequence> <xs:element minOccurs="0" maxOccurs="1" ref="slr:normalization" /> <xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/> </xs:sequence> <xs:attribute name="generalProfile" use="optional"/> <xs:attribute name="storageProfile" use="optional"/> </xs:complexType> </xs:element> <xs:element name="normalization"> <xs:complexType mixed="false"> <xs:attribute name="general" use="optional"/> <xs:attribute name="storage" use="optional"/> </xs:complexType> </xs:element> <xs:element name="data"> <xs:complexType mixed="false"> <xs:sequence> <xs:any maxOccurs="unbounded" minOccurs="0" namespace="##other" processContents="skip"/> </xs:sequence> <xs:attribute name="profile" use="required"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> </xs:schema> Appendix I Validation ModuleThis module defines a specific set of validation rules that can be applied to target text both globally and locally. Further constraints can be defined that allow rules to be applied to target text based on conditions in the source text or disabled to override a global scope. The namespace for the Validation module is:
The elements defined in the Validation module are:
Parent container for a list of rules and constraints to apply to the target text of the enclosing element. Contains:
Attributes:
Processing Requirements
A specific rule and constraint to apply to the target text of the enclosing element. Contains:
Attributes:
Processing Requirements
The attributes defined in the Validation module are:
This rule attribute specifies that a string MUST be present in the target text at least once. For example, the following is valid: <unit id="1"> <segment id="1"> <source>Choose an option in the online store.</source> <target>Escolha uma opção na loja online.</target> </segment> <validation> <rule isPresent="online" /> </validation> </unit> Whereas the following is invalid: <unit id="1"> <segment id="1"> <source>Choose an option in the online store.</source> <target>Escolha uma opção na online store.</target> </segment> <validation> <rule isPresent="loja" /> </validation> </unit> Other rule attributes can be combined with
Value description: Text Default value: none Used in: This rule attribute is used with the For example, the following is valid: <unit id="1"> <segment id="1"> <source>Choose a store option in the online store.</source> <target>Escolha uma opção de loja na loja online.</target> </segment> <validation> <rule isPresent="loja" occurs="2" /> </validation> </unit> Whereas the following is invalid: <unit id="1"> <segment id="1"> <source>Choose a store option in the online store.</source> <target>Escolha uma opção de loja na online store.</target> </segment> <validation> <rule isPresent="loja" occurs="2" /> </validation> </unit> Value description: A number of 1 or greater. Default value: none Used in: This rule attribute specifies that a string MUST NOT be present in the target text. For example, the following is valid: <unit id="1"> <segment id="1"> <source>Choose an option in the online store.</source> <target>Escolha uma opção na loja online.</target> </segment> <validation> <rule isNotPresent="store" /> </validation> </unit> Whereas the following is invalid: <unit id="1"> <segment id="1"> <source>Choose an option in the online store.</source> <target>Escolha uma opção na online store.</target> </segment> <validation> <rule isNotPresent="store" /> </validation> </unit> Value description: Text. Default value: none Used in: This rule attribute specifies that a string MUST start with a specific value. For example, the following is valid: <unit id="1"> <segment id="1"> <source>*Choose an option in the online store.</source> <target>*Escolha uma opção na loja online.</target> </segment> <validation> <rule startsWith="*" /> </validation> </unit> Whereas the following is invalid: <unit id="1"> <segment id="1"> <source>*Choose an option in the online store.</source> <target>Escolha uma opção na loja online.</target> </segment> <validation> <rule startsWith="*" /> </validation> </unit> Value description: Text. Default value: none
Used in:
This rule attribute specifies that a string MUST end with a specific value. For example, the following is valid: <unit id="1"> <segment id="1"> <source>Choose an option in the online store:</source> <target>Escolha uma opção na loja online:</target> </segment> <validation> <rule endsWith=":" /> </validation> </unit> Whereas the following is invalid: <unit id="1"> <segment id="1"> <source>Choose an option in the online store:</source> <target>Escolha uma opção na online store.</target> </segment> <validation> <rule endsWith=":" /> </validation> </unit> Value description: Text Default value: none Used in: When this rule attribute is used with another rule attribute and is set to When For example, the following are valid: <unit id="1"> <segment id="1"> <source>Choose an option in the online store:</source> <target>Escolha uma opção na loja online:</target> </segment> <validation> <rule endsWith=":" existsInSource="yes" /> </validation> </unit> <unit id="1"> <segment id="1"> <source>Choose an option in the online store.</source> <target>Escolha uma opção na loja online:</target> </segment> <validation> <rule endsWith=":" existsInSource="no" /> </validation> </unit> Whereas the following is invalid: <unit id="1"> <segment id="1"> <source>Choose an option in the online store.</source> <target>Escolha uma opção na loja online:</target> </segment> <validation> <rule endsWith=":" existsInSource="yes" /> </validation> </unit> Value description: yes or no Default value: no Used in: This rule attribute determines whether a rule MUST or MUST NOT be applied within the
scope of its enclosing element. For example, a rule defined at the This attribute is provided to allow for overriding execution of rules set at higher levels,
see In the following example, the isNotPresent rule is applied in its entirety to the first unit, but not to the second. <file> <validation> <rule isPresent="store" /> </validation> <unit id="1"> <segment id="1"> <source>Choose an option in the online store:</source> <target>Escolha uma opção na loja online:</target> </segment> </unit> <unit id="2"> <segment id="1"> <source>Choose an option in the application store:</source> <target>Escolha uma opção na application store:</target> </segment> <validation> <rule isPresent="store" disabled="yes" /> </validation> </unit> <file> Value description: yes or no Default value: no Used in: This rule attribute specifies the normalization type to apply when validating a rule. Only the normalization forms C and D as specified by the Unicode Consortium are supported, see Unicode Standard Annex #15. Value description: The allowed values are are listed in the table below along with their corresponding types of normalization to be applied. Table I.1. Values
Default value: nfc Used in: The schema listed below for reading convenience is accessible at http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/schemas/modules/validation.xsd. <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" xmlns:val="urn:oasis:names:tc:xliff:validation:2.0" targetNamespace="urn:oasis:names:tc:xliff:validation:2.0"> <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="http://www.w3.org/2001/xml.xsd"/> <xs:element name="validation"> <xs:complexType> <xs:sequence> <xs:element minOccurs="1" maxOccurs="unbounded" ref="val:rule"/> </xs:sequence> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> <xs:element name="rule"> <xs:complexType mixed="false"> <xs:attribute name="startsWith" use="optional"/> <xs:attribute name="endsWith" use="optional"/> <xs:attribute name="occurrences" use="optional"/> <xs:attribute name="mustLoc" use="optional"/> <xs:attribute name="noLoc" use="optional"/> <xs:attribute name="disabled" use="optional"/> <xs:attribute name="existsInSource" use="optional"/> <xs:attribute name="normalization" use="optional"/> <xs:anyAttribute namespace="##any" processContents="skip"/> </xs:complexType> </xs:element> </xs:schema> Appendix J Specification Change Tracking (Non-Normative)This is to facilitate human tracking of changes in the specification made since the first Public Review publication on 16th April 2013. This section tracks changes made to this specification compared to the Committee Specification Drat 01 / Public Review Draft 01 http://docs.oasis-open.org/xliff/xliff-core/v2.0/csprd01/xliff-core-v2.0-csprd01.html. The initial Public Review took place from 29th April 2013 until 29th May 2013.
Appendix K Acknowledgements (Non-Normative)The following individuals have participated in the creation of this specification and are gratefully acknowledged:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]