Committee Specification Draft 01
04 February 2014
- Specification URIs
- This version:
- http://docs.oasis-open.org/xliff/xliff-media/v2.0/csd01/xliff-media-v2.0-csd01.html
(Authoritative)
http://docs.oasis-open.org/xliff/xliff-media/v2.0/csd01/xliff-media-v2.0-csd01.pdf
http://docs.oasis-open.org/xliff/xliff-media/v2.0/csd01/xliff-media-v2.0-csd01.xml
- Previous version:
- N/A
- Technical Committee:
- OASIS XML Localisation Interchange File Format (XLIFF) TC
- Chair:
- Bryan Schnabel (bryan.s.schnabel@tektronix.com), Individual
- Editors:
- David Filip (davidf@ul.ie), Localisation Research Centre
Yves Savourel (ysavourel@enlaso.com), ENLASO Corporation
- Related Work:
This specification is related to:
XLIFF Version 2.0. Edited by Tom Comerford, David Filip, Rodolfo M. Raya, and Yves Savourel. Latest version: http://docs.oasis-open.org/xliff/xliff-core/v2.0/xliff-core-v2.0.html.
- Status:
This document was last revised or approved by the OASIS XML Localisation Interchange File Format (XLIFF) TC on the above date. The level 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 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 https://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 (https://www.oasis-open.org/committees/xliff/ipr.php).
- Citation format:
When referencing this specification the following citation format should be used:
[XLIFF-media-v2.0]
Media Type Registration Template for XLIFF Version 2.0. Edited by David Filip and Yves Savourel. 04 February 2014. OASIS Committee Specification Draft 01. http://docs.oasis-open.org/xliff/xliff-media/v2.0/csd01/xliff-media-v2.0-csd01.html. The latest version: http://docs.oasis-open.org/xliff/xliff-media/v2.0/xliff-media-v2.0.html.
Notices
Copyright © OASIS Open 2014. 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 https://www.oasis-open.org/policies-guidelines/trademark for above guidance.
Table of Contents
Type name: application
Subtype name: xliff+xml
Required parameters: N/A
Optional parameters: N/A
Encoding considerations:
Same as encoding considerations of application/xml as specified in RFC 3023
Security considerations:
All of the security considerations described in RFC 3023
Interoperability considerations:
Same as interoperability considerations described in RFC 3023
Also, interoperability requirements are specified throughout the specification and summarized in its Conformance section.
Published specification:
XLIFF Version 2.0 (CSD03) http://docs.oasis-open.org/xliff/xliff-core/v2.0/cos01/xliff-core-v2.0-cos01.html
Applications that use this media type:
XLIFF conformant applications, according to the Conformance Section of the specification
Fragment identifier considerations:
Generic XML processors won't be able to resolve XLIFF fragment identifiers, as the fragment identification syntax is specific for XLIFF and has been defined in its Fragment Identification section as of csd03/csprd03 of Version 2.0.
Intended usage: COMMON
Restrictions on usage: N/A
Author:
OASIS XML Localisation Interchange File Format (XLIFF) TC Editors: Tom Comerford,
<tom@supratext.com>; David Filip,<David.Filip@ul.ie>; Yves Savourel,<ysavourel@enlaso.com>Change controller:
OASIS XML Localisation Interchange File Format (XLIFF) TC https://www.oasis-open.org/committees/xliff/
Bryan Schnabel,
<bryan.s.schnabel@tektronix.com>, ChairTom Comerford,
<tom@supratext.com>, SecretaryDavid Filip,
<David.Filip@ul.ie>, SecretaryProvisional registration? (standards tree only): YES
Additional information:
Deprecated alias names for this type: N/A
Magic number(s): N/A
File extension(s): xlf
Macintosh file type code(s): "TEXT"
Person & email address to contact for further information:
OASIS Technical Committee administration
<tc-admin@oasis-open.org>