The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200112/msg00000.html
The Charter for this TC was modified on xx September 2012; this change was announced at http://lists.oasis-open.org/archives/tc-announce/xxxxxxxxxxx.html
The Charter for this TC was modified on 27 June 2006; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200607/msg00001.html
The charter for this TC was modified on 5 December 2005; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200512/msg00002.html
The charter for this TC was previously modified on 24 July 2002; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200207/msg00005.html
The charter for this TC is as follows.
OASIS XML Localisation Interchange File Format (XLIFF) TC
Statement of Purpose
The purpose of the OASIS XLIFF TC is to define, through extensible XML vocabularies, and promote the adoption of, a specification for the interchange of localisable software and document based objects and related metadata. To date, the committee has published three specifications - XLIFF 1.0, XLIFF 1.1, and XLIFF 1.2 - that define how to mark up and capture localisable data that will interoperate with different processes or phases without loss of information. Currently the TC works on XLIFF 2.0 specification, i.e. the major new version. The specifications are tool-neutral, support the entire localization process, and support common software and document data formats and mark-up languages. The specifications provide an extensibility mechanism to allow the development of tools compatible with an implementer's data formats and workflow requirements. The extensibility mechanism provides controlled inclusion of information not defined in the specification.
XLIFF defines a standard but extensible vocabulary that captures relevant metadata for any point in the lifecycle which can be exchanged between a variety of commercial and open-source tools. The XLIFF standard has been successfully fulfilling its purpose set by previous versions of this charter. However, the standard has to move forward as the industry moves forward. Therefore the XLIFF TC remains committed to producing major and minor new versions and maintaining them as per developing industry needs.
The first phase, completed 31 October 2003, created a 1.1 version committee specification that concentrated on software UI resource file localisable data requirements. The next phase consisted of promoting the adoption of XLIFF throughout the industry through additional collateral and specifications, continuing to advance the committee specification towards an official OASIS standard, and revising the XLIFF spec to 1.2 version to support document based content segmentation and alignment requirements. To encourage adoption of XLIFF, the TC had defined and published implementation guides for some of the most commonly used resource formats. The TC may redevelop non-normative reference guides for the major 2.0 version and for currently prominent content formats and standards, such as OASIS DITA and W3C MTHML5.
XLIFF TC operates under the RF on RAND Mode of the OASIS IPR Policy, according to sections 4, 10.2.1 and 10.2.2: http://www.oasis-open.org/policies-guidelines/ipr
List of Deliverables
The current OASIS XLIFF standard version is XLIFF 1.2 and is located here: http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html
· The Technical Committee is currently working on the version 2.0 of the standard.
· The normative deliverables for the 2.0 version will be:
· XLIFF 2.0 Specification (HTML and pdf)
· XLIFF 2.0 Core XML schema and schemas for modules included in the specification.
· Conformance test suite.
XLIFF TC plans to continuously work on minor versions numbered 2.x, eventually 2.x.y. Minor versions numbered 2.x will be produced by adding modules. Minor versions numbered 2.x.y will be produced by correcting minor issues.
Should significant changes to the core be required as result of industry developments, creation of a new major version will be triggered.