Great job TC! Great job David! Now we go on to the business of XLIFF Next.
From: email@example.com [mailto:firstname.lastname@example.org]
On Behalf Of Chet Ensign
Sent: Wednesday, February 14, 2018 6:59 AM
Cc: Paul Knight <email@example.com>
Subject: [xliff] Fwd: [voting] Groups - Ballot closed: "Call for consent of XLIFF V2.1 COS02 as an OASIS Standard"
Members of the XLIFF TC,
As you can see below, the call for consent has closed and XLIFF v2.1 is now an OASIS Standard. Congratulations!
Again, congratulations and let us know if you have any questions.
---------- Forwarded message ----------
Date: Tue, Feb 13, 2018 at 7:02 PM
Subject: [voting] Groups - Ballot closed: "Call for consent of XLIFF V2.1 COS02 as an OASIS Standard"
"Call for consent of XLIFF V2.1 COS02 as an OASIS Standard" has closed.
Call for consent of XLIFF V2.1 COS02 as an OASIS Standard
XLIFF Version 2.1 has been presented to the membership by the OASIS XML Localisation Interchange File Format (XLIFF) TC  as a Candidate OASIS Standard. Do you consent or object to its approval as a
19 of 263 eligible companies cast their vote before the deadline. - Consent received 19 Votes - Object received 0 Votes The ballot received 1 comment.
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  as a Candidate OASIS Standard. Do you consent or object to its approval as an OASIS Standard."
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 .
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 . To register an objection, you
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 . 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.
The prose specification document and related files are available here:
XLIFF Version 2.1
Candidate OASIS Standard 02
24 January 2018
Declarative validation artifacts:
Please contact OASIS TC Administration at
firstname.lastname@example.org with any questions you may have about this ballot.
--- Additional information ---
 OASIS XML Localisation Interchange File Format (XLIFF) TC
 Statements of Use
Felix Sasaki, Individual:
Soroush Saadatafar, Individual:
SDL Trados Studio:
Group: OASIS organizational voting
Date Opened: Wednesday, 31 January 2018 @ 12:00 am UTC
Date Closed: Tuesday, 13 February 2018 @ 11:59 pm UTC
03171: Call for consent of XLIFF V2.1 COS02 as an OASIS Standard (183K)
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer
to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.