Next Steps to Approve XLIFF 1.2 As OASIS Specification

Next steps

A. July 16, Roll Call Vote: Approve Request for initiation of a Committee Spec Ballot (passed)

B. July 23, TC Ballot: Approval XLIFF v1.2 as a Committee Specification (passed)

C. November 26, Mary updates the covers or the representation guides (sadly, in Rodolfo's job change, we need to take Mary up on her offer: "Rodolfo can say he’d like me to do it – not that I’m volunteering, but if he doesn’t have the time I’m happy to try to assist."). Names should be:

D. November 26, Mary finishes updates

E. Decmber 3, Mary has the representaion guids uploaded to ({FILENAME})

F.December 4, Mary sets up a Special Majority ballots; she needs go-ahead from TC Chair (7-day ballot) (passed)

G. December 15 (no later than), Mary initiates OASIS ballot (the required submission date for a January ballot).

H. January 15, OASIS members have until the middle of the month to vote (1st 14 days are reserved for OASIS members familiarizing themselves with the spec)

G. February 1, If at least 15% of OASIS voting membership has voted to approve, and no negative votes, XLIFF

H. 1.2 becomes an OASIS Standard.


I think we are just about ready to submit XLIFF 1.2 to the Membership of OASIS for consideration as an OASIS standard (in compliance with

Here's what we have:

(a) Committee Specifications and appropriate supplemental documentation

Note from Rodolfo: The representation guides are not in the server at the right places. Zipped versions are

Note from Rodolfo: The representation guides that we have still say "Public Review Draft 02" because we don't have a better name for approved related documents yet.

Note from Bryan: I did not include our FAQ, Whitepaper, or articles. I think we can use these as leverage to help persuade members to vote, down the line, but I do not consider them part of the core.

(b) Editable version of all files that are a part of the specification

(c) Certification of XML validity (schemas, and samples)

(d) A clear English-language summary of the specification

The XLIFF 1.2 Specification defines the XML Localization Interchange File Format (XLIFF). The purpose of this vocabulary is to store localizable data and carry it from one step of the localization process to the other, while allowing interoperability between tools.

The specification is tool-neutral, supports the entire localization process, and supports common software, document data formats, and mark-up languages. The specification provides 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.

(e) Statement of the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations

(f) Statements of Use

(g) Public Review announcements and dates

(h) An account of and results of the voting to approve the specification as a Committee Specification

(i) An account of or pointer to votes and comments received in any earlier

(j) A pointer to the publicly visible comments archive

(k) A pointer to any minority reports delivered by one or more Members


RemainingApprovalSteps (last edited 2009-08-12 18:07:05 by localhost)