OASIS XML Localisation Interchange File Format (XLIFF) TC

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. (1)(c) Scope  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. (1)(d) Deliverables  * 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.  (1)(f) Audience 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  (1)(g) Language  The XLIFF TC operates and publishes its work products in English.  -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

Chet,
 
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)?
 
Thanks,
 
Bryan
 
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
On Behalf Of Chet Ensign
Sent: Friday, June 06, 2014 9:37 AM
To: xliff@lists.oasis-open.org
Subject: [xliff] An issue has come up in your charter clarification - please review the revised text enclosed
 


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.


 


(1)(c) Scope 


 


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.


 


(1)(d) Deliverables 


 


* 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. 


 


(1)(f) Audience


 


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 


 


(1)(g) Language 


 


The XLIFF TC operates and publishes its work products in English. 


 

--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

 


Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html  

TC Administration information and support is available at
http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:     http://linkd.in/OASISopen
Twitter:         http://twitter.com/OASISopen
Facebook:   http://facebook.com/oasis.open

Exactly my questions, I see 1 typo though,  W3C MTHML5 instead of  W3C HTML5. This seems a typo I produced when bringing the diff version up to date.. Rgds dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 1:52 AM, Schnabel, Bryan S < bryan.s.schnabel@tektronix.com > wrote: Chet,   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)?   Thanks,   Bryan   From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: Friday, June 06, 2014 9:37 AM To: xliff@lists.oasis-open.org Subject: [xliff] An issue has come up in your charter clarification - please review the revised text enclosed   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.   (1)(c) Scope    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.   (1)(d) Deliverables    * 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.    (1)(f) Audience   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    (1)(g) Language    The XLIFF TC operates and publishes its work products in English.    -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393     Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

Hi Bryan, hi David -  Yes, you will need to have the TC request another clarification Special Majority Vote and I will run that for you.  Best,  /chet   On Mon, Jun 9, 2014 at 4:56 AM, Dr. David Filip < David.Filip@ul.ie > wrote: Exactly my questions, I see 1 typo though,  W3C MTHML5 instead of  W3C HTML5. This seems a typo I produced when bringing the diff version up to date.. Rgds dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 1:52 AM, Schnabel, Bryan S < bryan.s.schnabel@tektronix.com > wrote: Chet,   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)?   Thanks,   Bryan   From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: Friday, June 06, 2014 9:37 AM To: xliff@lists.oasis-open.org Subject: [xliff] An issue has come up in your charter clarification - please review the revised text enclosed   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.   (1)(c) Scope    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.   (1)(d) Deliverables    * 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.    (1)(f) Audience   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    (1)(g) Language    The XLIFF TC operates and publishes its work products in English.    -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393     Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

I see, in that case we might have a closer look at some sections, such as audience.. I just wonder how am I supposed to maintain the red-lined version, when the regulation requires such a significant structure re-haul.. @Chet, is the red-lined version an absolute requirement of the Admin process? Thanks dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 2:26 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Bryan, hi David -  Yes, you will need to have the TC request another clarification Special Majority Vote and I will run that for you.  Best,  /chet   On Mon, Jun 9, 2014 at 4:56 AM, Dr. David Filip < David.Filip@ul.ie > wrote: Exactly my questions, I see 1 typo though,  W3C MTHML5 instead of  W3C HTML5. This seems a typo I produced when bringing the diff version up to date.. Rgds dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 1:52 AM, Schnabel, Bryan S < bryan.s.schnabel@tektronix.com > wrote: Chet,   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)?   Thanks,   Bryan   From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: Friday, June 06, 2014 9:37 AM To: xliff@lists.oasis-open.org Subject: [xliff] An issue has come up in your charter clarification - please review the revised text enclosed   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.   (1)(c) Scope    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.   (1)(d) Deliverables    * 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.    (1)(f) Audience   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    (1)(g) Language    The XLIFF TC operates and publishes its work products in English.    -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393     Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

No, the red-lined version is not a requirement. In most cases, I'll use or create a red-line for the ballot and generally send it with the announcement as well so that people can quickly see the changes the TC made.  In this case, I would just use a before and after version and explain what actions were taken.  Though I think if you did do a red-line, it would show extensive edits to the statement of purpose, some changes to the deliverables and then the introduction of the new sections. I'll try doing it with Word and see what it looks like.  /chet  On Mon, Jun 9, 2014 at 11:01 AM, Dr. David Filip < David.Filip@ul.ie > wrote: I see, in that case we might have a closer look at some sections, such as audience.. I just wonder how am I supposed to maintain the red-lined version, when the regulation requires such a significant structure re-haul.. @Chet, is the red-lined version an absolute requirement of the Admin process? Thanks dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 2:26 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Bryan, hi David -  Yes, you will need to have the TC request another clarification Special Majority Vote and I will run that for you.  Best,  /chet   On Mon, Jun 9, 2014 at 4:56 AM, Dr. David Filip < David.Filip@ul.ie > wrote: Exactly my questions, I see 1 typo though,  W3C MTHML5 instead of  W3C HTML5. This seems a typo I produced when bringing the diff version up to date.. Rgds dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 1:52 AM, Schnabel, Bryan S < bryan.s.schnabel@tektronix.com > wrote: Chet,   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)?   Thanks,   Bryan   From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: Friday, June 06, 2014 9:37 AM To: xliff@lists.oasis-open.org Subject: [xliff] An issue has come up in your charter clarification - please review the revised text enclosed   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.   (1)(c) Scope    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.   (1)(d) Deliverables    * 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.    (1)(f) Audience   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    (1)(g) Language    The XLIFF TC operates and publishes its work products in English.    -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393     Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

Thanks, Chet, this helps I tried this with word before but the program did not seem intelligent enough, it showed everything as edits. Whole paragraph deletions and whole paragraph insertions. Maybe I did something wrong but I will rather provide before and after with explanation that the structural change is required because of changed admin process.. Thanks 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 4:09 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: No, the red-lined version is not a requirement. In most cases, I'll use or create a red-line for the ballot and generally send it with the announcement as well so that people can quickly see the changes the TC made.  In this case, I would just use a before and after version and explain what actions were taken.  Though I think if you did do a red-line, it would show extensive edits to the statement of purpose, some changes to the deliverables and then the introduction of the new sections. I'll try doing it with Word and see what it looks like.  /chet  On Mon, Jun 9, 2014 at 11:01 AM, Dr. David Filip < David.Filip@ul.ie > wrote: I see, in that case we might have a closer look at some sections, such as audience.. I just wonder how am I supposed to maintain the red-lined version, when the regulation requires such a significant structure re-haul.. @Chet, is the red-lined version an absolute requirement of the Admin process? Thanks dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 2:26 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Bryan, hi David -  Yes, you will need to have the TC request another clarification Special Majority Vote and I will run that for you.  Best,  /chet   On Mon, Jun 9, 2014 at 4:56 AM, Dr. David Filip < David.Filip@ul.ie > wrote: Exactly my questions, I see 1 typo though,  W3C MTHML5 instead of  W3C HTML5. This seems a typo I produced when bringing the diff version up to date.. Rgds dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 1:52 AM, Schnabel, Bryan S < bryan.s.schnabel@tektronix.com > wrote: Chet,   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)?   Thanks,   Bryan   From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: Friday, June 06, 2014 9:37 AM To: xliff@lists.oasis-open.org Subject: [xliff] An issue has come up in your charter clarification - please review the revised text enclosed   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.   (1)(c) Scope    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.   (1)(d) Deliverables    * 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.    (1)(f) Audience   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    (1)(g) Language    The XLIFF TC operates and publishes its work products in English.    -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393     Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

Yes, in this case I think that will be cleaner and easier. /chet On Mon, Jun 9, 2014 at 12:08 PM, Dr. David Filip < David.Filip@ul.ie > wrote: Thanks, Chet, this helps I tried this with word before but the program did not seem intelligent enough, it showed everything as edits. Whole paragraph deletions and whole paragraph insertions. Maybe I did something wrong but I will rather provide before and after with explanation that the structural change is required because of changed admin process.. Thanks 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 4:09 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: No, the red-lined version is not a requirement. In most cases, I'll use or create a red-line for the ballot and generally send it with the announcement as well so that people can quickly see the changes the TC made.  In this case, I would just use a before and after version and explain what actions were taken.  Though I think if you did do a red-line, it would show extensive edits to the statement of purpose, some changes to the deliverables and then the introduction of the new sections. I'll try doing it with Word and see what it looks like.  /chet  On Mon, Jun 9, 2014 at 11:01 AM, Dr. David Filip < David.Filip@ul.ie > wrote: I see, in that case we might have a closer look at some sections, such as audience.. I just wonder how am I supposed to maintain the red-lined version, when the regulation requires such a significant structure re-haul.. @Chet, is the red-lined version an absolute requirement of the Admin process? Thanks dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 2:26 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Bryan, hi David -  Yes, you will need to have the TC request another clarification Special Majority Vote and I will run that for you.  Best,  /chet   On Mon, Jun 9, 2014 at 4:56 AM, Dr. David Filip < David.Filip@ul.ie > wrote: Exactly my questions, I see 1 typo though,  W3C MTHML5 instead of  W3C HTML5. This seems a typo I produced when bringing the diff version up to date.. Rgds dF 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Mon, Jun 9, 2014 at 1:52 AM, Schnabel, Bryan S < bryan.s.schnabel@tektronix.com > wrote: Chet,   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)?   Thanks,   Bryan   From: xliff@lists.oasis-open.org [mailto: xliff@lists.oasis-open.org ] On Behalf Of Chet Ensign Sent: Friday, June 06, 2014 9:37 AM To: xliff@lists.oasis-open.org Subject: [xliff] An issue has come up in your charter clarification - please review the revised text enclosed   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.   (1)(c) Scope    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.   (1)(d) Deliverables    * 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.    (1)(f) Audience   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    (1)(g) Language    The XLIFF TC operates and publishes its work products in English.    -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393     Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393  Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

Hi all, another important point on our today's agenda is finalizing our charter clarification. We have materially approved the clarification twice by now, but the loading of the clarification failed as our structure does not conform to structural requirements (required normative sections) that have evolved since this TC had last clarified its Charter, Again we discussed this with Chet and a clear set of action is ahead of us. This is the Charter clarification text that we approved on May 20. http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/XLIFF2.0Charter/XLIFF%20TC%20Charter_Clarification.docx?op=dl&rev=0&isdir=0 Below, you can see how Chet distributed the text into section that are now required by the OASIS policy. I submitted Chet's proposal to SVN here: http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/XLIFF2.0Charter/XLIFF%20TC%20Charter%20Clarification_Restructured_AdminProposal.docx?op=dl&rev=0&isdir=0 Finally, this is how I propose to change the version proposed by Chet and request a special majority vote for it. http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/XLIFF2.0Charter/XLIFF%20TC%20Charter%20Clarification_Restructured_ToBeAproved.docx?op=dl&rev=0&isdir=0 We should have a brief discussion in the TC today and hopefully request the new Special Majority vote for the above linked version 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Fri, Jun 6, 2014 at 5:36 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: 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. (1)(c) Scope  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. (1)(d) Deliverables  * 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.  (1)(f) Audience 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  (1)(g) Language  The XLIFF TC operates and publishes its work products in English.  -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open

All, this is the motion language for the clarification special majority vote: I move to approve the TC Officers requesting that TC Administration hold a Special Majority Ballot to approve the charter clarification contained here:  http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/XLIFF2.0Charter/XLIFF%20TC%20Charter%20Clarification_Restructured_ToBeAproved.docx?op=dl&rev=0&isdir=0 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Tue, Jul 1, 2014 at 3:20 PM, Dr. David Filip < David.Filip@ul.ie > wrote: Hi all, another important point on our today's agenda is finalizing our charter clarification. We have materially approved the clarification twice by now, but the loading of the clarification failed as our structure does not conform to structural requirements (required normative sections) that have evolved since this TC had last clarified its Charter, Again we discussed this with Chet and a clear set of action is ahead of us. This is the Charter clarification text that we approved on May 20. http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/XLIFF2.0Charter/XLIFF%20TC%20Charter_Clarification.docx?op=dl&rev=0&isdir=0 Below, you can see how Chet distributed the text into section that are now required by the OASIS policy. I submitted Chet's proposal to SVN here: http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/XLIFF2.0Charter/XLIFF%20TC%20Charter%20Clarification_Restructured_AdminProposal.docx?op=dl&rev=0&isdir=0 Finally, this is how I propose to change the version proposed by Chet and request a special majority vote for it. http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/XLIFF2.0Charter/XLIFF%20TC%20Charter%20Clarification_Restructured_ToBeAproved.docx?op=dl&rev=0&isdir=0 We should have a brief discussion in the TC today and hopefully request the new Special Majority vote for the above linked version 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 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Fri, Jun 6, 2014 at 5:36 PM, Chet Ensign < chet.ensign@oasis-open.org > wrote: 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. (1)(c) Scope  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. (1)(d) Deliverables  * 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.  (1)(f) Audience 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  (1)(g) Language  The XLIFF TC operates and publishes its work products in English.  -- /chet  ---------------- Chet Ensign Director of Standards Development and TC Administration  OASIS: Advancing open standards for the information society http://www.oasis-open.org Primary: +1 973-996-2298 Mobile: +1 201-341-1393   Check your work using the Support Request Submission Checklist at  http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html   TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin Follow OASIS on: LinkedIn:     http://linkd.in/OASISopen Twitter:         http://twitter.com/OASISopen Facebook:   http://facebook.com/oasis.open