Requirements and Goals for XLIFF 2.0
24 October 2007
Latest Approved Version:
OASIS XML Localisation Interchange File Format (XLIFF) TC
Bryan Schnabel < email@example.com>
Tony Jewtushenko <firstname.lastname@example.org>
Rodolfo M. Raya <email@example.com>
Bryan S. Schnabel <firstname.lastname@example.org>
This document describes the requirements for the XLIFF 2.0 specification.
This document is an early draft. It has not been submitted at any level for fromal approval.
Technical Committee members should send comments on this specification to the Technical Committee's email list. Others should send comments to the Technical Committee by using the "Send A Comment" button on the Technical Committee' s web page at www.oasis-open.org/committees/xliff
For information on whether any patents have been disclosed that may be essential to implementing this specification, and any offers of patent licensing terms, please refer to the Intellectual Property Rights section of the Technical Committee web page ( http://www.oasis-open.org/committees/xliff/ipr.php).
The non-normative errata page for this document does not exist www.oasis-open.org/committees/xliff/documents/xliff-core-1.2-errata.htm
Copyright © OASIS® 1993 - 2007. 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 names "OASIS" and "XLIFF" are trademarks 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/who/trademark.php for above guidance.
Table of Contents
2. Must Have Requirements
3. Should Have Requirments
4. Nice to Have Requirements and Goals
A. XLIFF Technical Committee (Non-Normative)
This document is a record of the Requirements and Goals for XLIFF 2.0.
A list of goals was evaluated by the XLIFF TC, and categorized into one of three ratings:
There were a number of items discarded from consideration. They are not listed in this document, but are recored in TC meeting minutes.
Each of these are rated as Must have - Has to be part of the next release.
Each of these are rated as Should have - Will probably be part of the next release.
Each of these are rated as Nice to have - Good ideas that we want to record but are not required to be in the next release (could be goals we accomplish, but do not tie to the approval of XLIFF 2.0).
The XLIFF Technical Committee at OASIS is composed of the following members:
CSS Specifications. W3C (World Wide Web Consortium).
IANA Names for Character Sets. IANA (Internet Assigned Numbers Authority), Aug 2001
Codes for the Representation of Names of Languages. ISO (International Standards Organization), Nov 2001.
Codes for the representation of names of countries and their subdivisions. ISO (International Organization for Standardization), Jun 2000.
Representation of dates and times. ISO (International Organization for Standardization), Dec 2000.
Multipurpose Internet Mail Extensions. IETF (Internet Engineering Task Force), Jun 1992.
RFC 4646 Tags for the Identification of Languages. IETF (Internet Engineering Task Force), Sep 2006.
Extensible Markup Language (XML) 1.0. W3C (World Wide Web Consortium).
Namespaces in XML. W3C (World Wide Web Consortium), August 16, 2006.
International Organization for Standardization Web site.
Localisation Industry Standards Association Web site.
Organization for the Advancement of Structured Information Standards Web site.
OpenTag Format Specifications. ILE (International Language Engineering), Nov 1998.
Translation Memory eXchange (TMX). LISA (Localisation Industry Standards association).
Segmentation Rules eXchange (SRX). LISA (Localisation Industry Standards association).
Unicode Consortium Web site.
World Wide Web Consortium Web site.