OASIS Open

XLIFF Version 2.1 has been presented to the membership by the OASIS XML Localisation Interchange File Format (XLIFF) TC [1] as a Candidate OASIS Standard. Do you consent or object to its approval as a

XLIFF is the XML Localization Interchange File Format. It has been designed by a group of multilingual content publishers, software providers, localization service providers, localization tools providers and researchers. It is intended to give any multilingual content owner 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 lossless interchange format, usage of XLIFF as a processing format is neither encouraged nor discouraged or prohibited.

The TC received 5 Statements of Use from ENLASO Corporation, Felix Sasaki, Soroush Saadatafar, SDL Trados Studio, and Umbraco [2].

This is a call to the Organizational Members of OASIS to consent or object to this approval. You are welcome to register your consent explicitly on the ballot; however your consent is assumed unless you register an objection [3]. To register an objection, you must:

1. Indicate your objection on this ballot, and

2. Provide a reason for your objection and/or a proposed remedy to the TC.

You may provide the reason in the comment box or by email to the Technical Committee on its comment mailing list or, if you are a member of the TC, to the TC's mailing list [3]. If you provide your reason by email, please indicate in the subject line that this is in regard to the Call for Consent. Note that failing to provide a reason and/or remedy may result in an objection being deemed invalid.

URIs:

The prose specification document and related files are available here:

XLIFF Version 2.1
Candidate OASIS Standard 02
24 January 2018

http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos02/xliff-core-v2.1-cos02.html (Authoritative)
http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos02/xliff-core-v2.1-cos02.pdf
http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos02/xliff-core-v2.1-cos02.xml
Declarative validation artifacts: http://docs.oasis-open.org/xliff/xliff-core/v2.1/cos02/schemas/

Please contact OASIS TC Administration at tc-admin@lists.oasis-open.org with any questions you may have about this ballot.

--- Additional information ---

[1] OASIS XML Localisation Interchange File Format (XLIFF) TC
https://www.oasis-open.org/committees/xliff/

[2] Statements of Use
ENLASO Corporation: https://lists.oasis-open.org/archives/xliff/201709/msg00006.html

Felix Sasaki, Individual: https://lists.oasis-open.org/archives/xliff/201709/msg00007.html

Soroush Saadatafar, Individual: https://lists.oasis-open.org/archives/xliff-comment/201710/msg00005.html

SDL Trados Studio: https://lists.oasis-open.org/archives/xliff-comment/201710/msg00004.html

Umbraco: https://lists.oasis-open.org/archives/xliff-comment/201710/msg00003.html

[3] https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26#OScallForConsent

Amendment Posted on Tuesday, 6 February 2018:
My thanks to CIS for catching the truncated question. It should read:

"XLIFF Version 2.1 has been presented to the membership by the OASIS XML Localisation Interchange File Format (XLIFF) TC [1] as a Candidate OASIS Standard. Do you consent or object to its approval as an OASIS Standard."