OASIS XML Localisation Interchange File Format (XLIFF) TC

Hi all, this is the v0,2 draft to kick off charter doscussion. I am not sure how the list behaves re attachments, so I copy paste into the message body as well.. XLIFF 2.0 Program Charter [Charter Draft, v0.2]   This Charter is being submitted by David Filip for discussion by the XLIFF TC [Prepared by David Filip] Preambel This Charter is not intended to amend normal OASIS TC procedures. It is intended to provide guidance and reference point for technical and organizational development of the next version of the OASIS XLIFF standard. XLIFF TC is free to use standard OASIS TC procedures such as TC ballots to amend the existing XLIFF TC procedures, amend (clarify) the existing OASIS XLIFF TC Charter or re-charter the OASIS XLIFF TC. Steering Committee and its membership The Steering Committee is formed by the currently serving Officers of the Technical Committee (including Chairs of active SCs). Current Holders of the seats as of June 7, 2011: XLIFF TC Chair €“ Bryan Schnabel €“ Individual Member XLIFF TC Secretary €“ Rodolfo Raya €“ Maxprograms Inline Markup SC Chair €“ Yves Savourel - ENLASO The executive sponsor of the XLIFF 2.0 program is the Chair of the XLIFF TC. However, all decisions taken by the Steering Committee and/or the executive sponsor must be sanctioned by a formal TC ballot (face-to-face, roll call based, or fully automated via kavi between meetings) within 2 calendar weeks to remain valid. XLIFF TC assigns at least once in a calendar year one voting member or officer of the TC to organize an International XLIFF Symposium to assess the success and usage of the current XLIFF standard, and lay plans accordingly for further development of the standard. XLIFF TC is committed to hearing the customer voice as formulated by International XLIFF Symposium attendees. The role of the XLIFF Symposium is the role of an informal industry advisory body. Executive Summary [TBD]   Definitions Core     Basic part of the specification that contains all and only substantial elements that cannot possibly be excluded without negatively affecting the standard €™s capability to allow for basic language technology related transformations. Customer             Toolmakers and End users of the standard are considered customers of the XLIFF TC. Element                 In this Charter, an XLIFF-specific expression of a XML vocabulary along with its rules, attributes, attribute values etc. An element attribute can be considered element per se for the purpose of describing the specification in this Charter. End User             There are various targeted user groups to benefit from the standard. A typical end user role is the one of a translator, project manager, reviewer etc. End users are not expected to regularly see the underlying XML of the standard, they should benefit from the interoperability achieved through implementation of the standard via various GUIs produced by Toolmakers. Meaningful functional whole               elements that are critical for performing certain types of language technology transformations, all and only such elements and their respective processing rules. Module                     a part of the specification that fulfills all of the following conditions i)                         Does not overlap with Core ii)                       Is compatible with Core iii)                     Comprises all elements and their processing rules that form a meaningful functional whole Toolmaker         A consumer of the standard who usually does not play an active role in the standard development. Unlike End Users, Toolmakers are expected to work with the XML of the standard and feedback the TC. Even though a toolmaker can play a role on the TC, his role as the standard €™s consumer is distinct. For standard OASIS terminology see e.g. http://www.oasis-open.org/policies-guidelines   Description of Business Needs the Program should address Customers €™ voice: The 1.x standard is too complex The 1.x standard has too generous extensibility The 1.x standard lacks explicit conformance criteria The overall goal is to ensure interoperability throughout Language Technology related content transformations during the whole content lifecycle. Although the XLIFF 1.x standard was intended primarily as an exchange format the industry practice shows that the defined format is also suitable for storage and legacy content leverage purposes. Product Description [Description of the desired state] The XLIFF TC commits to addressing the customer needs as under the Description of Business Needs. In particular XLIFF TC resolved via previous ballots to create a 2.0 standard that will 1)           Be modular 2)           Contain non-negotiable core 3)           Be created with conformance and processing requirements in mind Although backwards compatibility with the 1.x standards is perceived as a value per se by the XLIFF TC, backwards compatibility has lesser priority than serving the business needs stated above. XLIFF TC will prioritize the non-negotiable core and its release over long tail wish list. Immediately after releasing the core specification (maybe along with one or two important modules such as concordance memory and legacy leverage) XLIFF TC will start working on optional functional modules based on industry prioritization and available manpower. Main Success Scenario [TBD] High Level Scope and Deliverables Substantial parts of Core or Module. Smaller parts must not be released lest publishing errata to a previously published core or module. 1.           Human language specification in Docbook format, including but not limited ·                 Description of all elements ·                 Conformance criteria for every element o     Provenance of each element if needed ·                 Processing rules for each element o     Processing rules are given as admissible values on processor input and admissible values on processor output o     Conformance to processing rules must be verifiable solely via checking input and output artifacts as described above ·                 Conformance clause referring to element specific conformance criteria and processing rules 2.           XML schema (strict/transitional/skip?) conformant to the human readable specification as of 1. 3.           Reference guides for the following formats a.           DITA b.           XHTML c.             HTML 4 and 5 d.           Docx e.           ODF f.               €¦[TBD] List of high level deliverables 1.           Core specification 2.           Modules specifications €“ need to work out the schedule   Benefits Statement €“ Business Case [boiler plate guidance] The benefits should be quantified as the specification evolves, generally as early as possible, it is better to have ballpark figures which will be adjusted later on than to work with no quantifiable expectation at all. Accuracy vs. precision €“ try to be approximately accurate, do not be afraid of educated guesses within a wider interval. Precise quantified statements in early stages are almost always wrong. €œMinimax € €“ Build the business case, so that cost are estimated generously and any benefits are estimated as low as conceptually thinkable. It is the best way how to avoid unpleasant surprises during project execution and benefits realization. Benefits Realization [boiler plate guidance] How do you get from the current state to the desired one? Just high level sequence of events and coordination . It is not the benefits realization plan, this is elaborated based on this and the high and lower level plans. Scope of the Project [boiler plate guidance] Start with just all the generic types of activities to be covered. This will later on evolve into a full work breakdown structure (WBS). Project Constraints including Critical Success Factors [boiler plate guidance] Typically: Budget, Quality and Time. May include other such as feature completeness, methodology requirements etc. External and internal.. High Level Plan [boiler plate guidance] Make sure it covers the full WBS, you may base it on a subject matter relevant methodology such as waterfall, agile, RUP etc. Microsoft Project or other automated Gantt €critical path €capable tool recommended. It is much easier to update an *.mpp than say a *.xls. Benefits Realization Plan [boiler plate guidance] Results from Benefits Realization and High Level Plan. Senior Users and Key Users nominated by them must be committed to benefit realization, must take part in benefits realization planning, designing acceptance criteria etc. Project Team Currently active Voting Members €“ including Officers Last, First Company   Role Voting   Schnabel*, Bryan   Phone: 503-627-5282 bryan.s.schnabel@tektronix.com Individual Chair Yes     Raya, Mr. Rodolfo   Ramon Masini 3325/802 Montevideo, 11300 UY Phone: +598 99914993 rmraya@maxprograms.com Maxprograms Secretary Yes     Savourel, Mr. Yves   9543 W. Emerald St., Suite 105 Boise, ID 83704 US ysavourel@translate.com ENLASO Corporation Voting Member Yes     Chapman, Ms. Helena   IBM Voting Member Yes     Walters, David   waltersd@us.ibm.com IBM Voting Member Yes     Filip, Dr. David   LRC CSIS University of Limerick Limerick, Limerick 0 Ireland Phone: +353-61-202881 David.Filip@ul.ie Localisation Research Centre* Voting Member Yes     Morado Vazquez, Lucia   Phone: +353-61-202881 Lucia.Morado@ul.ie Localisation Research Centre* Voting Member Yes     Reynolds, Peter   Phone: +48 22 480 88 06 p.reynolds@maart.pl Polish Association of Translation Agencies (PSBT) Voting Member Yes     Lieske, Mr Christian   Phone: +49 (06227) 761303 christian.lieske@sap.com SAP AG* Voting Member Yes     Swift, Mr. Andrew   Phone: 44 114 2535247 aswift@sdl.com SDL International* Voting Member Yes   Active external stakeholders IN! Yamagata, LIOX LT-Web and LT-Infra   Key Users [TBD] David Filip, Ph.D. ===================== cellphone: +353-86-049-34-68 mailto: davidf@davidf.org Please use david.filip@ul.ie for LRC business www.davidf.org , http://www.linkedin.com/in/davidfatdavidf XLIFF2.0Charter_v0.2.docx

Thank you for this important work David, I will try to get this on today's agenda (as soon as the note shows up in kavi). I think this informs the rest of the work we do, so we'll need to hone this to the liking of the TC as our guiding document.

Great work; thanks!

- Bryan
________________________________________
From: David Filip [davidf@davidf.org]
Sent: Tuesday, June 07, 2011 7:12 AM
To: Schnabel, Bryan S; Rodolfo Raya; xliff@lists.oasis-open.org
Cc: Lucia.Morado
Subject: Charter draft to start the discussion today

Hi all, this is the v0,2 draft to kick off charter doscussion.
I am not sure how the list behaves re attachments, so I copy paste into the message body as well..


XLIFF 2.0 Program Charter

[Charter Draft, v0.2]

This Charter is being submitted by David Filip for discussion by the XLIFF TC
[Prepared by David Filip]
Preambel
This Charter is not intended to amend normal OASIS TC procedures. It is intended to provide guidance and reference point for technical and organizational development of the next version of the OASIS XLIFF standard. XLIFF TC is free to use standard OASIS TC procedures such as TC ballots to amend the existing XLIFF TC procedures, amend (clarify) the existing OASIS XLIFF TC Charter or re-charter the OASIS XLIFF TC.
Steering Committee and its membership
The Steering Committee is formed by the currently serving Officers of the Technical Committee (including Chairs of active SCs).
Current Holders of the seats as of June 7, 2011:
XLIFF TC Chair ¨C Bryan Schnabel ¨C Individual Member
XLIFF TC Secretary ¨C Rodolfo Raya ¨C Maxprograms
Inline Markup SC Chair ¨C Yves Savourel - ENLASO
The executive sponsor of the XLIFF 2.0 program is the Chair of the XLIFF TC. However, all decisions taken by the Steering Committee and/or the executive sponsor must be sanctioned by a formal TC ballot (face-to-face, roll call based, or fully automated via kavi between meetings) within 2 calendar weeks to remain valid.
XLIFF TC assigns at least once in a calendar year one voting member or officer of the TC to organize an International XLIFF Symposium to assess the success and usage of the current XLIFF standard, and lay plans accordingly for further development of the standard. XLIFF TC is committed to hearing the customer voice as formulated by International XLIFF Symposium attendees. The role of the XLIFF Symposium is the role of an informal industry advisory body.
Executive Summary
[TBD]


Definitions
Core Basic part of the specification that contains all and only substantial elements that cannot possibly be excluded without negatively affecting the standard¡¯s capability to allow for basic language technology related transformations.
Customer Toolmakers and End users of the standard are considered customers of the XLIFF TC.
Element In this Charter, an XLIFF-specific expression of a XML vocabulary along with its rules, attributes, attribute values etc. An element attribute can be considered element per se for the purpose of describing the specification in this Charter.
End User There are various targeted user groups to benefit from the standard. A typical end user role is the one of a translator, project manager, reviewer etc. End users are not expected to regularly see the underlying XML of the standard, they should benefit from the interoperability achieved through implementation of the standard via various GUIs produced by Toolmakers.
Meaningful functional whole elements that are critical for performing certain types of language technology transformations, all and only such elements and their respective processing rules.
Module a part of the specification that fulfills all of the following conditions

i) Does not overlap with Core

ii) Is compatible with Core

iii) Comprises all elements and their processing rules that form a meaningful functional whole
Toolmaker A consumer of the standard who usually does not play an active role in the standard development. Unlike End Users, Toolmakers are expected to work with the XML of the standard and feedback the TC. Even though a toolmaker can play a role on the TC, his role as the standard¡¯s consumer is distinct.
For standard OASIS terminology see e.g. http://www.oasis-open.org/policies-guidelines


Description of Business Needs the Program should address
Customers¡¯ voice:
The 1.x standard is too complex
The 1.x standard has too generous extensibility
The 1.x standard lacks explicit conformance criteria
The overall goal is to ensure interoperability throughout Language Technology related content transformations during the whole content lifecycle.
Although the XLIFF 1.x standard was intended primarily as an exchange format the industry practice shows that the defined format is also suitable for storage and legacy content leverage purposes.
Product Description [Description of the desired state]
The XLIFF TC commits to addressing the customer needs as under the Description of Business Needs. In particular XLIFF TC resolved via previous ballots to create a 2.0 standard that will

1) Be modular

2) Contain non-negotiable core

3) Be created with conformance and processing requirements in mind
Although backwards compatibility with the 1.x standards is perceived as a value per se by the XLIFF TC, backwards compatibility has lesser priority than serving the business needs stated above.
XLIFF TC will prioritize the non-negotiable core and its release over long tail wish list.
Immediately after releasing the core specification (maybe along with one or two important modules such as concordance memory and legacy leverage) XLIFF TC will start working on optional functional modules based on industry prioritization and available manpower.
Main Success Scenario
[TBD]
High Level Scope and Deliverables
Substantial parts of Core or Module.
Smaller parts must not be released lest publishing errata to a previously published core or module.

1. Human language specification in Docbook format, including but not limited

¡¤ Description of all elements

¡¤ Conformance criteria for every element

o Provenance of each element if needed

¡¤ Processing rules for each element

o Processing rules are given as admissible values on processor input and admissible values on processor output

o Conformance to processing rules must be verifiable solely via checking input and output artifacts as described above

¡¤ Conformance clause referring to element specific conformance criteria and processing rules

2. XML schema (strict/transitional/skip?) conformant to the human readable specification as of 1.

3. Reference guides for the following formats

a. DITA

b. XHTML

c. HTML 4 and 5

d. Docx

e. ODF

f. ¡­[TBD]

List of high level deliverables

1. Core specification

2. Modules specifications ¨C need to work out the schedule


Benefits Statement ¨C Business Case
[boiler plate guidance]
The benefits should be quantified as the specification evolves, generally as early as possible, it is better to have ballpark figures which will be adjusted later on than to work with no quantifiable expectation at all.
Accuracy vs. precision ¨C try to be approximately accurate, do not be afraid of educated guesses within a wider interval. Precise quantified statements in early stages are almost always wrong.
¡°Minimax¡± ¨C Build the business case, so that cost are estimated generously and any benefits are estimated as low as conceptually thinkable. It is the best way how to avoid unpleasant surprises during project execution and benefits realization.
Benefits Realization
[boiler plate guidance]
How do you get from the current state to the desired one? Just high level sequence of events and coordination . It is not the benefits realization plan, this is elaborated based on this and the high and lower level plans.
Scope of the Project
[boiler plate guidance]
Start with just all the generic types of activities to be covered. This will later on evolve into a full work breakdown structure (WBS).
Project Constraints including Critical Success Factors
[boiler plate guidance]
Typically: Budget, Quality and Time. May include other such as feature completeness, methodology requirements etc.
External and internal..
High Level Plan
[boiler plate guidance]
Make sure it covers the full WBS, you may base it on a subject matter relevant methodology such as waterfall, agile, RUP etc.
Microsoft Project or other automated Gantt©critical path©capable tool recommended. It is much easier to update an *.mpp than say a *.xls.
Benefits Realization Plan
[boiler plate guidance]
Results from Benefits Realization and High Level Plan. Senior Users and Key Users nominated by them must be committed to benefit realization, must take part in benefits realization planning, designing acceptance criteria etc.
Project Team
Currently active Voting Members ¨C including Officers
Last, First< http://www.oasis-open.org/apps/org/workgroup/xliff/members/roster.php?sort_field=p.plname&sort_type=ASC >

Company < http://www.oasis-open.org/apps/org/workgroup/xliff/members/roster.php?sort_type=DESC >

Role< http://www.oasis-open.org/apps/org/workgroup/xliff/members/roster.php?sort_field=r.name&sort_type=ASC >

Voting< http://www.oasis-open.org/apps/org/workgroup/xliff/members/roster.php?sort_field=wgv.level&sort_type=ASC >

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=20 > Schnabel*, Bryan< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=27410 >
Phone: 503-627-5282
bryan.s.schnabel@tektronix.com< bryan.s.schnabel@tektronix.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=bryan.s.schnabel@tektronix.com >

Individual

Chair

Yes

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=10473 > Raya, Mr. Rodolfo< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=36797 >
Ramon Masini 3325/802
Montevideo, 11300
UY
Phone: +598 99914993
rmraya@maxprograms.com< rmraya@maxprograms.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=rmraya@maxprograms.com >

Maxprograms

Secretary

Yes

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=11473 > Savourel, Mr. Yves< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=40889 >
9543 W. Emerald St., Suite 105
Boise, ID 83704
US
ysavourel@translate.com< ysavourel@translate.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=ysavourel@translate.com >

ENLASO Corporation

Voting Member

Yes

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=13249 > Chapman, Ms. Helena< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=48204 >

IBM< http://www.ibm.com/ >

Voting Member

Yes

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=4609 > Walters, David< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=48205 >
waltersd@us.ibm.com< waltersd@us.ibm.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=waltersd@us.ibm.com >

IBM< http://www.ibm.com/ >

Voting Member

Yes

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=13162 > Filip, Dr. David< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=47831 >
LRC CSIS University of Limerick
Limerick, Limerick 0
Ireland
Phone: +353-61-202881
David.Filip@ul.ie< David.Filip@ul.ie">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=David.Filip@ul.ie >

Localisation Research Centre*< http://www.localisation.ie/ >

Voting Member

Yes

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=5942 > Morado Vazquez, Lucia< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=41362 >
Phone: +353-61-202881
Lucia.Morado@ul.ie< Lucia.Morado@ul.ie">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=Lucia.Morado@ul.ie >

Localisation Research Centre*< http://www.localisation.ie/ >

Voting Member

Yes

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=10602 > Reynolds, Peter< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=47231 >
Phone: +48 22 480 88 06
p.reynolds@maart.pl< p.reynolds@maart.pl">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=p.reynolds@maart.pl >

Polish Association of Translation Agencies (PSBT)< http://www.psbt.org.pl/ >

Voting Member

Yes

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=426 > Lieske, Mr Christian< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=6097 >
Phone: +49 (06227) 761303
christian.lieske@sap.com< christian.lieske@sap.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=christian.lieske@sap.com >

SAP AG*< http://www.sap.com/ >

Voting Member

Yes

< http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=12485 > Swift, Mr. Andrew< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=45293 >
Phone: 44 114 2535247
aswift@sdl.com< aswift@sdl.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=aswift@sdl.com >

SDL International*< http://www.sdl.com/ >

Voting Member

Yes

Active external stakeholders
IN!
Yamagata, LIOX
LT-Web and LT-Infra

Key Users
[TBD]


David Filip, Ph.D.
=====================
cellphone: +353-86-049-34-68
mailto:davidf@davidf.org < mailto:davidf@davidf.org >
Please use david.filip@ul.ie< mailto:david.filip@ul.ie > for LRC business
www.davidf.org< http://www.davidf.org >, http://www.linkedin.com/in/davidfatdavidf

Bryan, I see from the minutes there are some lingering issues about ETSI and what it does/doesn't mean for XLIFF and OASIS. Could I request a few minutes in the meeting to address this matter? -Arle On Jun 7, 2011, at 10:18 , Schnabel, Bryan S wrote: > Thank you for this important work David, I will try to get this on today's agenda (as soon as the note shows up in kavi). I think this informs the rest of the work we do, so we'll need to hone this to the liking of the TC as our guiding document. > > Great work; thanks! > > - Bryan > ________________________________________ > From: David Filip [davidf@davidf.org] > Sent: Tuesday, June 07, 2011 7:12 AM > To: Schnabel, Bryan S; Rodolfo Raya; xliff@lists.oasis-open.org > Cc: Lucia.Morado > Subject: Charter draft to start the discussion today > > Hi all, this is the v0,2 draft to kick off charter doscussion. > I am not sure how the list behaves re attachments, so I copy paste into the message body as well.. > > > XLIFF 2.0 Program Charter > > [Charter Draft, v0.2] > > This Charter is being submitted by David Filip for discussion by the XLIFF TC > [Prepared by David Filip] > Preambel > This Charter is not intended to amend normal OASIS TC procedures. It is intended to provide guidance and reference point for technical and organizational development of the next version of the OASIS XLIFF standard. XLIFF TC is free to use standard OASIS TC procedures such as TC ballots to amend the existing XLIFF TC procedures, amend (clarify) the existing OASIS XLIFF TC Charter or re-charter the OASIS XLIFF TC. > Steering Committee and its membership > The Steering Committee is formed by the currently serving Officers of the Technical Committee (including Chairs of active SCs). > Current Holders of the seats as of June 7, 2011: > XLIFF TC Chair ¨C Bryan Schnabel ¨C Individual Member > XLIFF TC Secretary ¨C Rodolfo Raya ¨C Maxprograms > Inline Markup SC Chair ¨C Yves Savourel - ENLASO > The executive sponsor of the XLIFF 2.0 program is the Chair of the XLIFF TC. However, all decisions taken by the Steering Committee and/or the executive sponsor must be sanctioned by a formal TC ballot (face-to-face, roll call based, or fully automated via kavi between meetings) within 2 calendar weeks to remain valid. > XLIFF TC assigns at least once in a calendar year one voting member or officer of the TC to organize an International XLIFF Symposium to assess the success and usage of the current XLIFF standard, and lay plans accordingly for further development of the standard. XLIFF TC is committed to hearing the customer voice as formulated by International XLIFF Symposium attendees. The role of the XLIFF Symposium is the role of an informal industry advisory body. > Executive Summary > [TBD] > > > Definitions > Core Basic part of the specification that contains all and only substantial elements that cannot possibly be excluded without negatively affecting the standard¡¯s capability to allow for basic language technology related transformations. > Customer Toolmakers and End users of the standard are considered customers of the XLIFF TC. > Element In this Charter, an XLIFF-specific expression of a XML vocabulary along with its rules, attributes, attribute values etc. An element attribute can be considered element per se for the purpose of describing the specification in this Charter. > End User There are various targeted user groups to benefit from the standard. A typical end user role is the one of a translator, project manager, reviewer etc. End users are not expected to regularly see the underlying XML of the standard, they should benefit from the interoperability achieved through implementation of the standard via various GUIs produced by Toolmakers. > Meaningful functional whole elements that are critical for performing certain types of language technology transformations, all and only such elements and their respective processing rules. > Module a part of the specification that fulfills all of the following conditions > > i) Does not overlap with Core > > ii) Is compatible with Core > > iii) Comprises all elements and their processing rules that form a meaningful functional whole > Toolmaker A consumer of the standard who usually does not play an active role in the standard development. Unlike End Users, Toolmakers are expected to work with the XML of the standard and feedback the TC. Even though a toolmaker can play a role on the TC, his role as the standard¡¯s consumer is distinct. > For standard OASIS terminology see e.g. http://www.oasis-open.org/policies-guidelines > > > Description of Business Needs the Program should address > Customers¡¯ voice: > The 1.x standard is too complex > The 1.x standard has too generous extensibility > The 1.x standard lacks explicit conformance criteria > The overall goal is to ensure interoperability throughout Language Technology related content transformations during the whole content lifecycle. > Although the XLIFF 1.x standard was intended primarily as an exchange format the industry practice shows that the defined format is also suitable for storage and legacy content leverage purposes. > Product Description [Description of the desired state] > The XLIFF TC commits to addressing the customer needs as under the Description of Business Needs. In particular XLIFF TC resolved via previous ballots to create a 2.0 standard that will > > 1) Be modular > > 2) Contain non-negotiable core > > 3) Be created with conformance and processing requirements in mind > Although backwards compatibility with the 1.x standards is perceived as a value per se by the XLIFF TC, backwards compatibility has lesser priority than serving the business needs stated above. > XLIFF TC will prioritize the non-negotiable core and its release over long tail wish list. > Immediately after releasing the core specification (maybe along with one or two important modules such as concordance memory and legacy leverage) XLIFF TC will start working on optional functional modules based on industry prioritization and available manpower. > Main Success Scenario > [TBD] > High Level Scope and Deliverables > Substantial parts of Core or Module. > Smaller parts must not be released lest publishing errata to a previously published core or module. > > 1. Human language specification in Docbook format, including but not limited > > ¡¤ Description of all elements > > ¡¤ Conformance criteria for every element > > o Provenance of each element if needed > > ¡¤ Processing rules for each element > > o Processing rules are given as admissible values on processor input and admissible values on processor output > > o Conformance to processing rules must be verifiable solely via checking input and output artifacts as described above > > ¡¤ Conformance clause referring to element specific conformance criteria and processing rules > > 2. XML schema (strict/transitional/skip?) conformant to the human readable specification as of 1. > > 3. Reference guides for the following formats > > a. DITA > > b. XHTML > > c. HTML 4 and 5 > > d. Docx > > e. ODF > > f. ¡­[TBD] > > List of high level deliverables > > 1. Core specification > > 2. Modules specifications ¨C need to work out the schedule > > > Benefits Statement ¨C Business Case > [boiler plate guidance] > The benefits should be quantified as the specification evolves, generally as early as possible, it is better to have ballpark figures which will be adjusted later on than to work with no quantifiable expectation at all. > Accuracy vs. precision ¨C try to be approximately accurate, do not be afraid of educated guesses within a wider interval. Precise quantified statements in early stages are almost always wrong. > ¡°Minimax¡± ¨C Build the business case, so that cost are estimated generously and any benefits are estimated as low as conceptually thinkable. It is the best way how to avoid unpleasant surprises during project execution and benefits realization. > Benefits Realization > [boiler plate guidance] > How do you get from the current state to the desired one? Just high level sequence of events and coordination . It is not the benefits realization plan, this is elaborated based on this and the high and lower level plans. > Scope of the Project > [boiler plate guidance] > Start with just all the generic types of activities to be covered. This will later on evolve into a full work breakdown structure (WBS). > Project Constraints including Critical Success Factors > [boiler plate guidance] > Typically: Budget, Quality and Time. May include other such as feature completeness, methodology requirements etc. > External and internal.. > High Level Plan > [boiler plate guidance] > Make sure it covers the full WBS, you may base it on a subject matter relevant methodology such as waterfall, agile, RUP etc. > Microsoft Project or other automated Gantt©critical path©capable tool recommended. It is much easier to update an *.mpp than say a *.xls. > Benefits Realization Plan > [boiler plate guidance] > Results from Benefits Realization and High Level Plan. Senior Users and Key Users nominated by them must be committed to benefit realization, must take part in benefits realization planning, designing acceptance criteria etc. > Project Team > Currently active Voting Members ¨C including Officers > Last, First< http://www.oasis-open.org/apps/org/workgroup/xliff/members/roster.php?sort_field=p.plname&sort_type=ASC > > > Company < http://www.oasis-open.org/apps/org/workgroup/xliff/members/roster.php?sort_type=DESC > > > Role< http://www.oasis-open.org/apps/org/workgroup/xliff/members/roster.php?sort_field=r.name&sort_type=ASC > > > Voting< http://www.oasis-open.org/apps/org/workgroup/xliff/members/roster.php?sort_field=wgv.level&sort_type=ASC > > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=20 > Schnabel*, Bryan< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=27410 > > Phone: 503-627-5282 > bryan.s.schnabel@tektronix.com< bryan.s.schnabel@tektronix.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=bryan.s.schnabel@tektronix.com > > > Individual > > Chair > > Yes > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=10473 > Raya, Mr. Rodolfo< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=36797 > > Ramon Masini 3325/802 > Montevideo, 11300 > UY > Phone: +598 99914993 > rmraya@maxprograms.com< rmraya@maxprograms.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=rmraya@maxprograms.com > > > Maxprograms > > Secretary > > Yes > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=11473 > Savourel, Mr. Yves< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=40889 > > 9543 W. Emerald St., Suite 105 > Boise, ID 83704 > US > ysavourel@translate.com< ysavourel@translate.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=ysavourel@translate.com > > > ENLASO Corporation > > Voting Member > > Yes > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=13249 > Chapman, Ms. Helena< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=48204 > > > IBM< http://www.ibm.com/ > > > Voting Member > > Yes > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=4609 > Walters, David< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=48205 > > waltersd@us.ibm.com< waltersd@us.ibm.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=waltersd@us.ibm.com > > > IBM< http://www.ibm.com/ > > > Voting Member > > Yes > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=13162 > Filip, Dr. David< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=47831 > > LRC CSIS University of Limerick > Limerick, Limerick 0 > Ireland > Phone: +353-61-202881 > David.Filip@ul.ie< David.Filip@ul.ie">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=David.Filip@ul.ie > > > Localisation Research Centre*< http://www.localisation.ie/ > > > Voting Member > > Yes > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=5942 > Morado Vazquez, Lucia< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=41362 > > Phone: +353-61-202881 > Lucia.Morado@ul.ie< Lucia.Morado@ul.ie">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=Lucia.Morado@ul.ie > > > Localisation Research Centre*< http://www.localisation.ie/ > > > Voting Member > > Yes > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=10602 > Reynolds, Peter< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=47231 > > Phone: +48 22 480 88 06 > p.reynolds@maart.pl< p.reynolds@maart.pl">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=p.reynolds@maart.pl > > > Polish Association of Translation Agencies (PSBT)< http://www.psbt.org.pl/ > > > Voting Member > > Yes > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=426 > Lieske, Mr Christian< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=6097 > > Phone: +49 (06227) 761303 > christian.lieske@sap.com< christian.lieske@sap.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=christian.lieske@sap.com > > > SAP AG*< http://www.sap.com/ > > > Voting Member > > Yes > > < http://www.oasis-open.org/apps/org/workgroup/xliff/mail_to_person.php?recipient_id=12485 > Swift, Mr. Andrew< http://www.oasis-open.org/apps/org/workgroup/xliff/members/wg_person.php?workgroup_person_id=45293 > > Phone: 44 114 2535247 > aswift@sdl.com< aswift@sdl.com">https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=aswift@sdl.com > > > SDL International*< http://www.sdl.com/ > > > Voting Member > > Yes > > Active external stakeholders > IN! > Yamagata, LIOX > LT-Web and LT-Infra > > Key Users > [TBD] > > > David Filip, Ph.D. > ===================== > cellphone: +353-86-049-34-68 > mailto:davidf@davidf.org < mailto:davidf@davidf.org > > Please use david.filip@ul.ie< mailto:david.filip@ul.ie > for LRC business > www.davidf.org< http://www.davidf.org >, http://www.linkedin.com/in/davidfatdavidf >