Next in thread →
Next in month →
Re: [xliff] Fwd: Proposal for XLIFF TC Charter Clarification
Thanks Helena, the idea is that it is a collection of input and output files that should cover ideally all conformance (basically MUST and MUST NOT) statements within the spec. If tools are able to produce the output files their owners can claim conformance. As I explained in Seattle, this can be addressed after the spec goes to public review. The idea is that test can be contributed by anyone (through TC members) provided that they demonstrably conform to conformance statements in the spec (TC simple majority decision). Ideally this should be ready and working before the spec becomes official OASIS standard and before it goes to ISO. The details can and should be discussed and elaborated at a later stage. For the charter clarification, we just need to answer the question whether we want to provide a transparent collection of tests or if we let people claim conformance as they see fit, as so far.. If people do NOT support having such a collection of tests they should vote NO in the upcoming ballot on the clarification that just got seconded by Bryan. Cheers dF Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 mailto: On Wed, Feb 27, 2013 at 6:28 PM, Helena S Chapman <> wrote: I have a concern about conformance test suite as well. Who will own that, define and provide the test suite? Who will perform the assessment whether a tool meets the conformance criteria? Is it for a fee or some non-profit will do this magic work for free? How can this be managed long term? Or do we let people just declare themselves as compliant and not care if it's really compliant or not? If so, what's the point of having one? From: "Schnabel, Bryan S" <> To: "Dr. David Filip" <>, "" <> Date: 02/27/2013 12:43 PM Subject: RE: [xliff] Fwd: Proposal for XLIFF TC Charter Clarification Sent by: <> Second From: [mailto:] On Behalf Of Dr. David Filip Sent: Monday, February 25, 2013 9:30 AM To: Subject: [xliff] Fwd: Proposal for XLIFF TC Charter Clarification Dear all, hereby I move to accept the attached text as the TC's charter clarification. You can also find the text copy-pasted down below along with description of some background discussion that took place in September 2012. If there is a second I'd like to ask Bryan to create a simple yes/no/abstain ballot that would ideally conclude just before our meeting next week. Regarding the reasoning around the ballot proposal, the proposed changes consist mostly in bringing the text up to date. Throughout the history of the topic, no one showed the least appetite to drive rechartering, which would be a major administrative exercise with with difficult to specify legal impact. We seem to have had consensus that the TC does not need rechartering because the major new version is in scope of the original charter with minor clarifications. Thanks for your attention dF Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 mailto: ---------- Forwarded message ---------- From: Dr. David Filip <> Date: Tue, Sep 18, 2012 at 2:32 PM Subject: Re: Proposal for XLIFF TC Charter Clarification To: Hi all, other than in the meeting there was no follow up discussion on the Charter clarification. In the new version I reformulated the statement about reference guides with may, as per Rodolfo's request in the meeting. Other issues I was not able to fix: Rodolfo was not happy with saying that a "Conformance test suit" is our deliverable (for 2.0). It seems clear that we need more than schema. @Rodolfo, all, what can we call this deliverable without trying to resolve technical details? My personal opinion is that "Conformance test suite" is neutral enough, still according to Rodolfo it has unwanted implications and "cannot work" Also did not locate garbled language and/or inconsistentncy in UK / US spellings that Fredrik mentioned.. Feel free to propose improvements. Cheers dF [charter proposal clarification text copy-pasted] OASIS XML Localisation Interchange File Format TC The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200112/msg00000.html The Charter for this TC was modified on xx September 2012; this change was announced at http://lists.oasis-open.org/archives/tc-announce/xxxxxxxxxxx.html The Charter for this TC was modified on 27 June 2006; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200607/msg00001.html The charter for this TC was modified on 5 December 2005; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200512/msg00002.html The charter for this TC was previously modified on 24 July 2002; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200207/msg00005.html The charter for this TC is as follows. Name OASIS XML Localisation Interchange File Format (XLIFF) TC 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 three 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 operates under the RF on RAND Mode of the OASIS IPR Policy, according to sections 4, 10.2.1 and 10.2.2: http://www.oasis-open.org/policies-guidelines/ipr List of Deliverables The current OASIS XLIFF standard version is XLIFF 1.2 and is located here: http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html · The Technical Committee is currently working on the version 2.0 of the standard. · The normative deliverables for the 2.0 version will be: · XLIFF 2.0 Specification (HTML and pdf) · XLIFF 2.0 Core XML schema and schemas for modules included in the specification. · Conformance test suite. 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. [end of charter proposal] Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 mailto: On Tue, Sep 4, 2012 at 2:28 PM, Dr. David Filip <> wrote: Dear all, please find attached the current version of TC Charter, the Clarification proposal and a diff of the 2. Although the diff seems large, I tried to make only minimal necessary changes. I will explain more in the call if time allows. Cheers dF The final proposed text is also pasted below: OASIS XML Localisation Interchange File Format TC The original Call For Participation for this TC may be found at http://lists.oasis-open.org/archives/tc-announce/200112/msg00000.html The Charter for this TC was modified on xx September 2012; this change was announced at http://lists.oasis-open.org/archives/tc-announce/xxxxxxxxxxx.html The Charter for this TC was modified on 27 June 2006; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200607/msg00001.html The charter for this TC was modified on 5 December 2005; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200512/msg00002.html The charter for this TC was previously modified on 24 July 2002; this change was announced at http://lists.oasis-open.org/archives/tc-announce/200207/msg00005.html The charter for this TC is as follows. Name OASIS XML Localisation Interchange File Format (XLIFF) TC 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 three 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. These non-normative reference guides will need to be redeveloped for the major 2.0 version and for currently prominent content formats and standards such as OASIS DITA and W3C MTHML5. XLIFF TC operates under the RF on RAND Mode of the OASIS IPR Policy, according to sections 4, 10.2.1 and 10.2.2: http://www.oasis-open.org/policies-guidelines/ipr List of Deliverables The current OASIS XLIFF standard version is XLIFF 1.2 and is located here: http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html · The Technical Committee is currently working on the version 2.0 of the standard. · The normative deliverables for the 2.0 version will be: · XLIFF 2.0 Specification (HTML and pdf) · XLIFF 2.0 Core XML schema and schemas for modules included in the specification. · Conformance test suite. 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. Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 cellphone: +353-86-0222-158 facsimile: +353-6120-2734 mailto:
Next in thread →
Next in month →