![](/uploads/1/2/6/9/126931901/573212900.jpg)
Subscribe to Download! It's your choice - buy your WordPress plugins at full price from their authors and benefit from technical support, or join GPLVaults today and enjoy full access to over 1400 premium WordPress plugins and themes at a fraction of the cost, without technical support.
Status:This document was last revised or approved by the membership of OASIS on the above date. Thelevel of approval is also listed above.
Check the “Latest version” location noted above for possible later revisions of this document.Technical Committee members should send comments on thisspecification to the Technical Committee's email list. Others shouldsend comments to the Technical Committee by using the 'button on the Technical Committee's web page at.For information on whether any patents have been disclosed thatmay be essential to implementing this specification, and any offers ofpatent licensing terms, please refer to the Intellectual Property Rightssection of the Technical Committee web page.
![Xliff Xliff](/uploads/1/2/6/9/126931901/858053229.jpg)
NoticesCopyright © OASIS Open 2014. All Rights Reserved.All capitalized terms in the following text have the meaningsassigned to them in the OASIS Intellectual Property Rights Policy (the'OASIS IPR Policy'). The full may be found at the OASISwebsite.This document and translations of it may be copied and furnishedto others, and derivative works that comment on or otherwise explain itor assist in its implementation may be prepared, copied, published, anddistributed, in whole or in part, without restriction of any kind,provided that the above copyright notice and this section are includedon all such copies and derivative works.
1 IntroductionXLIFF is the XML Localisation Interchange File Format designed by agroup of multilingual content publishers, software providers, localization service providers,localization tools providers and researchers. It is intended to give any multilingual contentowner a single interchange file format that can be understood by any localization provider,using any conformant localization tool. While the primary focus is on being a losslessinterchange format, usage of XLIFF as a processing format is neither encouraged nordiscouraged or prohibited.All text is normative unless otherwise labeled. The following common methods are used forlabeling portions of this specification as informative and hence non-normative:Appendices and sections marked as '(Informative)' or 'Non-Normative' intitle,Notes (sections with the 'Note' title),Warnings (sections with the 'Warning' title),Examples (mainly example code listings but also any inline examples or illustrativeexemplary lists in otherwise normative text),Schema and other artifacts listings (the corresponding artifacts are normative, nottheir listings). NoteExtractor knowledge of the native format is not assumed while Enriching. XLIFF CoreThe core of XLIFF 2.0 consists of the minimum set of XMLelements and attributes required to (a) prepare a document thatcontains text extracted from one or more files for localization,(b) allow it to be completed with the translation of theextracted text, and (c) allow the generation of Translatedversions of the original document.The XML namespace that corresponds to the core subset of XLIFF 2.0 is'urn:oasis:names:tc:xliff:document:2.0'. XLIFF-defined (elements and attributes)The following is the list of allowed schema URN prefixes for XLIFF-defined elements and attributes: urn:oasis:names:tc:xliff:However, the following namespaces are NOT consideredXLIFF-defined for the purposes of the XLIFF 2.0specification: urn:oasis:names:tc:xliff:document:1.0urn:oasis:names:tc:xliff:document:1.1urn:oasis:names:tc:xliff:document:1.2Elements and attributes from other namespaces are not XLIFF-defined.
XLIFF DocumentAny XML document that declares the namespace'urn:oasis:names:tc:xliff:document:2.0' as its main namespace, hasas the root element and complies with the XMLSchemas and the declared Constraints that are part of this specification. XLIFF ModuleA module is an OPTIONAL set of XML elements and attributesthat stores information about a process applied to an XLIFFDocument and the data incorporated into the document as resultof that process.Each official module defined for XLIFF 2.0 has its grammardefined in an independent XML Schema with a separatenamespace. Document Conformance.XLIFF is an XML vocabulary, therefore conformant XLIFF DocumentsMUST be well formed and valid documents.Conformant XLIFF Documents MUST be valid instances of the officialthat is part of this XLIFF specification.As not all aspects of the XLIFF specification can be expressed in terms of XML Schemas,conformant XLIFF DocumentsMUST also comply with all relevant elements andattributes definitions, normative usage descriptions, and Constraintsspecified in this specification document.XLIFF Documents MAY contain custom extensions, as defined in thesection. Application Conformance.XLIFF WritersMUST create conformant XLIFFDocuments to be considered XLIFF compliant.Agents processing conformant XLIFF Documents thatcontain custom extensions are not REQUIRED to understand and processnon-XLIFF elements or attributes.
Constraints.The prefix of a module or an extension MUST be an NMTOKEN longer than 1character and MUST be defined in the module or extensionspecification.The prefix of a module or an extension MUST be registered with theXLIFF TC.A given module or extension namespace URI MUST be associated with a single prefix.A prefix MAY be associated with more than one namespace URI (to allowfor example different versions of a given module or extension to use the sameprefix).See also the (which applies for modules as well).
![](/uploads/1/2/6/9/126931901/573212900.jpg)