[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xliff] An issue has come up in your charter clarification - please review the revised text enclosed
I see nothing objectionable with your proposed fix.
But I just want to be clear on what you are asking us to do.
Are there next steps you’re expecting from us, or do you want us to “speak now or forever hold our peace”?
Or are you saying we need to vote on this at our next meeting (which will be 17 June)?
From: firstname.lastname@example.org [mailto:email@example.com]
On Behalf Of Chet Ensign
Members of the XLIFF TC,
In preparing to load the clarified charter language passed by the recent Special Majority Vote, I realized that the TC’s charter is not in alignment with the current requirements of the OASIS TC Process. (See section 2.2 TC Formation at https://www.oasis-open.org/policies-guidelines/tc-process#formation.)
Clarifying the charter gives us the opportunity to address this and fix it. It is particularly important that we bring the TC into alignment because the scope section governs the work of the TC.
Below, I have taken the existing language from the XLIFF charter and moved it into the normative sections of the charter required by the OASIS TC Process. I made no changes to the text itself. Therefore, this can still be treated as a clarification.
Please have a look at this and let me know if you want to discuss it further. If you want to edit/revise, feel free to do so. As long as your changes do not expand the scope of the TC’s work, it still falls under the heading of clarification.
Section 1: Charter
(1)(a) TC Name
OASIS XML Localisation Interchange File Format (XLIFF) TC
(1)(b) Statement of Purpose
The purpose of the OASIS XLIFF TC is to define, through extensible XML vocabularies, and promote the adoption of, a specification for the interchange of localisable software and document based objects and related metadata. To date, the committee has published two specifications - XLIFF 1.0, XLIFF 1.1, and XLIFF 1.2 - that define how to mark up and capture localisable data that will interoperate with different processes or phases without loss of information.
Currently the TC works on XLIFF 2.0 specification, i.e. the major new version. The specifications are tool-neutral, support the entire localization process, and support common software and document data formats and mark-up languages. The specifications provide 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.
XLIFF defines a standard but extensible vocabulary that captures relevant metadata for any point in the lifecycle which can be exchanged between a variety of commercial and open-source tools. The XLIFF standard has been successfully fulfilling its purpose set by previous versions of this charter. However, the standard has to move forward as the industry moves forward. Therefore the XLIFF TC remains committed to producing major and minor new versions and maintaining them as per developing industry needs.
The first phase, completed 31 October 2003, created a 1.1 version committee specification that concentrated on software UI resource file localisable data requirements. The next phase consisted of promoting the adoption of XLIFF throughout the industry through additional collateral and specifications, continuing to advance the committee specification towards an official OASIS standard, and revising the XLIFF spec to 1.2 version to support document based content segmentation and alignment requirements. To encourage adoption of XLIFF, the TC had defined and published implementation guides for some of the most commonly used resource formats. The TC may redevelop non-normative reference guides for the major 2.0 version and for currently prominent content formats and standards such as OASIS DITA and W3C MTHML5.
XLIFF TC plans to continuously work on minor versions numbered 2.x, eventually 2.x.y. Minor versions numbered 2.x will be produced by adding modules. Minor versions numbered 2.x.y will be produced by correcting minor issues.
Should significant changes to the core be required as result of industry developments, creation of a new major version will be triggered.
* XLIFF 2.0 Specification (HTML and pdf)
* XLIFF 2.0 Core XML schema and schemas for modules included in the specification.
* Conformance test suite.
* Minor versions numbered 2.x
(1)(e) IPR Mode
The XLIFF TC operates under the RF on RAND Mode per the OASIS IPR Policy, sections 4, 10.2.1 and 10.2.2.
The audience for the work of the XLIFF TC includes:
- Software providers for enterprise localization tools and processes
- Technical communicators employing enterprise localization tools and processes
The XLIFF TC operates and publishes its work products in English.
Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html