Description: Event Description:
Standing monthly XLIFF TC Teleconference.
1. Call one of the MeetingPlace phone numbers:
From the AMER region dial: * 1-888-967-2253 * +1-650-607-2253
From the APAC region dial: * +61 2 8817 6100
From the EMEA region dial: * +44 118 924 9000
2. Enter the Meeting ID (805534) followed by the # key
3. If the organizer has not started the meeting you will be:
A. Asked to speak your name followed by the # key
B. Placed in the waiting room on music hold until the organizer starts the meeting.
If the organizer has started the meeting you will be:
A. Asked to enter the Meeting Password (030543)
B. Asked to speak your name followed by the # key
**note: If the dial-in instructions change I will try to communicate the new instructions no later than Monday, March 19
==========
Agenda: [meeting goal: quickly cover XLIFF 1.2 timeline; make good progress on sorting XLIFF 2.0 ideas into YES or NO categories]
1/ roll call
2/ Approve Previous meeting minutes
Accept, reject, or amend.
http://www.oasis-open.org/archives/xliff/200702/msg00012.html
3/ XLIFF 1.2 Specification status and timeline for approval as a standard
A. [completed] Sunday, January 21 - Public Review ended
B. [completed] Tuesday, January 23 – TC Roll call vote: Approved Request for initiation of a Committee Spec Ballot
C. [completed] Friday, February 2 – TC Ballot passed: Approve XLIFF v1.2 as a Committee Specification (http://www.oasis-open.org/apps/org/workgroup/xliff/ballot.php?id=1207)
[next steps before moving to item D.]
i. [completed] Rename, re-title, repost XLIFF 1.2 Specification and profiles to reflect the Committee Specification status (Bryan)
ii. Update whitepaper (Rodolfo will do this; Tony located the latest version here: http://www.oasis-open.org/apps/org/workgroup/xliff/document.php?document_id=3111)
iii. Update FAQ (Tony located latest version here: http://www.oasis-open.org/archives/xliff/200309/msg00011.html; last author is unknown; Doug will help author the FAQ)
iv. "Certification by at least three OASIS member organizations that they are successfully using the specification;" (http://www.oasis-open.org/committees/process.php#3.4)
The following OASIS members were identified and sent requests:
- Fredrik Corneliusson, Lionbridge
- Christian Lieske, SAP AG
- Matthew Lovatt, Oracle Corporation
- Magnus Martikainen, SDL International (Magnus confirmed that the affidavit is on its way in a couple weeks)
- Peter Reynolds, Idiom Technologies, Inc
- Reinhard Schaler, Localisation Research Centre
(thanks to each member for attempting to obtain certification!)
v. Friday, March 30 (assuming i thru iv are complete) Bryan (and Tony) submit a TC (via email) ballot for TC approval to submit the XLIFF 1.2 Committee Specification to the membership of OASIS for consideration as an OASIS Standard
[note: I pushed each of the following dates out to reflect a more realistic timeframe for completing 1 thru iv, above]
D. Wednesday, April 4 (Assuming TC approves the ballot [7 days]) Bryan (and Tony) request TC OASIS Administrator to submit the XLIFF 1.2 Committee Specification to the membership of OASIS for consideration as an OASIS Standard
E. Friday, April 13 (assuming all conditions have been met) TC OASIS Administrator submits the XLIFF 1.2 Committee Specification to the membership of OASIS for consideration as an OASIS Standard
F. Monday, April 30 OASIS members have until the middle of the month to vote (1st 14 days are reserved for OASIS members familiarizing themselves with the spec)
G. Monday, May 16 If at least 15% of OASIS voting membership has voted to approve, and no negative votes, XLIFF 1.2 becomes an OASIS Standard. What if it fails?
4/ XLIFF 2.0 - Life after approval of XLIFF 1.2
- Below we have three lists: A. things we want to do, B. things we haven't decided upon yet, and C. things we rule out for 2.0.
- Let's look at each item in B. to see if we can move it into A. or C. (or if we're not sure, leave it in B.)
- Assign a TC member to each approved 2.0 item
A. Items the TC has identified as likely next pursuits for XLIFF 2.0
i Reference implementations or toolkit(s) similar to DITA
(Rodolfo)
ii XLIFF validator tool to be included in a toolkit
(Rodolfo)
v XLIFF Round Trip tool could be modified to support:
(DITA/ITS -> XLIFF -> Translated DITA model)
(Bryan - it looks like I can change the xliffRoundTrip Tool license from GPL to
Apache {according to an inquiry I made to licensing@fsf.org, the GPL license expert debunked our
misconception that "Once something has a GPL license it is impossible to get out of it"})
B. Items the TC has not yet ruled out
iii Submitting to ISO once XLIFF becomes an OASIS standard
iv Additional Representation Guides (DITA,.NET / Win32, Docbook)
vi Subsetting / restricting XSD as proposed by Christian
vii Version control Metadata - need to track revision information
viii Ability to store Multilingual Content.
ix Create a bare-bones XLIFF core, then provide extension modules that support additional features.
x "Simplify, Extend and Clarify"
(Core XLIFF functionality would be in primary XLIFF namespace; would be very simple to implement.)
(Extensions would provide support for more complicated features like, Segmentation, Pre-Translation, Generic Inline Markup, etc.)
xi Schema Catalogues; host a namespace Catalogues
for XLIFF 3rd party custom / extension namespaces.
xii More work on inline-elements:
(Separate inline elements from other elements? Maybe as an extension? Stronger rules for when to use each inline tag?)
xiii Define a multi-lingual "Localisation Kit" format, which may include:
(XLIFF content + original source material+ all target language files+ skeleton files + reference files + some sort of manifest document describing/defining the payload.
xiv Using XLIFF as a primary content authoring container.
(Author stores contend directly to XLIFF instead of another proprietary format.)
xv Terminology Markup
(Has been suggested by Kara Warburton of IBM some time ago to support terminology markup such as translate (yes/no), subject-categorization, type, etc.)
C. Items the TC has ruled out as likely features for XLIFF 2.0
5/ Reports from liaisons involved with other standards groups:
A. W3C i18n
B. Oscar
C. Trans-WS
D. LRC
E: OASIS DITA Translation Subcommittee
6/ Any Other Business
----------------------------------------------------
==========
Minutes: 1/ roll call
There were 7 members present as record in Kavi.
Apologies: Andrzej, Matt
2/ Approve Previous meeting minutes
Accept, reject, or amend.
http://www.oasis-open.org/archives/xliff/200702/msg00012.html
Tony proposed and Doug seconded the acceptance of the minutes as a correct record. This was approved by the meeting.
3/ XLIFF 1.2 Specification status and timeline for approval as a standard
Rodolfo raised an issue with a bug in the specification.
Doug has corrected the schema and described the problem as: “The xsd:key tag requires that the identifier by defined (in this case, the ‘name’ attribute of the context-group). The xsd:unique tag is the same as xsd:key, except that the identifier may be undefined. I checked the other xsd:key elements in the schema and each of those identifiers are required and therefore xsd:key is appropriate.”
Rodolfo will update the Spec for errors and broken links. Rodolfo will change the PO profile and Java profile. Bryan and Doug will work on the HTML profile. We will also need to change the URLs for the latest version. We agreed that we would set a goal of April 1st for doing this work and testing this. Bryan and Doug agreed to do the testing for this. We will also need a document which shows the delta between this and the last review. There will then be another cycle of 14 day public review and a committee specification ballot.
A. [completed] Sunday, January 21 - Public Review ended
B. [completed] Tuesday, January 23 – TC Roll call vote: Approved Request for initiation of a Committee Spec Ballot
C. [completed] Friday, February 2 – TC Ballot passed: Approve XLIFF v1.2 as a Committee Specification (http://www.oasis-open.org/apps/org/workgroup/xliff/ballot.php?id=1207)
[next steps before moving to item D.]
i. [completed] Rename, re-title, repost XLIFF 1.2 Specification and profiles to reflect the Committee Specification status (Bryan)
ii. Update whitepaper (Rodolfo will do this; Tony located the latest version here: http://www.oasis-open.org/apps/org/workgroup/xliff/document.php?document_id=3111)
iii. Update FAQ (Tony located latest version here: http://www.oasis-open.org/archives/xliff/200309/msg00011.html; last author is unknown; Doug will help author the FAQ)
iv. "Certification by at least three OASIS member organizations that they are successfully using the specification;" (http://www.oasis-open.org/committees/process.php#3.4)
The following OASIS members were identified and sent requests:
- Fredrik Corneliusson, Lionbridge
- Christian Lieske, SAP AG
- Matthew Lovatt, Oracle Corporation
- Magnus Martikainen, SDL International (Magnus confirmed that the affidavit is on its way in a couple weeks)
- Peter Reynolds, Idiom Technologies, Inc
- Reinhard Schaler, Localisation Research Centre
(thanks to each member for attempting to obtain certification!)
v. Friday, March 30 (assuming i thru iv are complete) Bryan (and Tony) submit a TC (via email) ballot for TC approval to submit the XLIFF 1.2 Committee Specification to the membership of OASIS for consideration as an OASIS Standard
[note: I pushed each of the following dates out to reflect a more realistic timeframe for completing 1 thru iv, above]
D. Wednesday, April 4 (Assuming TC approves the ballot [7 days]) Bryan (and Tony) request TC OASIS Administrator to submit the XLIFF 1.2 Committee Specification to the membership of OASIS for consideration as an OASIS Standard
E. Friday, April 13 (assuming all conditions have been met) TC OASIS Administrator submits the XLIFF 1.2 Committee Specification to the membership of OASIS for consideration as an OASIS Standard
F. Monday, April 30 OASIS members have until the middle of the month to vote (1st 14 days are reserved for OASIS members familiarizing themselves with the spec)
G. Monday, May 16 If at least 15% of OASIS voting membership has voted to approve, and no negative votes, XLIFF 1.2 becomes an OASIS Standard. What if it fails?
4/ XLIFF 2.0 - Life after approval of XLIFF 1.2
- Below we have three lists: A. things we want to do, B. things we haven't decided upon yet, and C. things we rule out for 2.0.
- Let's look at each item in B. to see if we can move it into A. or C. (or if we're not sure, leave it in B.)
- Assign a TC member to each approved 2.0 item
A. Items the TC has identified as likely next pursuits for XLIFF 2.0
i Reference implementations or toolkit(s) similar to DITA
(Rodolfo)
ii XLIFF validator tool to be included in a toolkit
(Rodolfo)
v XLIFF Round Trip tool could be modified to support:
(DITA/ITS -> XLIFF -> Translated DITA model)
(Bryan - it looks like I can change the xliffRoundTrip Tool license from GPL to
Apache {according to an inquiry I made to licensing@fsf.org, the GPL license expert debunked our
misconception that "Once something has a GPL license it is impossible to get out of it"})
B. Items the TC has not yet ruled out
iii Submitting to ISO once XLIFF becomes an OASIS standard
We have had some contact with Gerhard Budin who chairs the ISO Language Standards committee. Rodolfo mentioned that TBX was doing this and the first step is to contact the ISO people to see if they are interested in proposing this. The specification would then have to be written in the ISO template. There would be a sub committee formed to look after XLIFF and this would be the XLIFF TC. Tony mentioned that one of the advantages would be that this would ensure that XLIFF could be used for Government contracts and may be a regulatory contract.
iv Additional Representation Guides (DITA,.NET / Win32, Docbook)
vi Subsetting / restricting XSD as proposed by Christian
vii Version control Metadata - need to track revision information
viii Ability to store Multilingual Content.
ix Create a bare-bones XLIFF core, then provide extension modules that support additional features.
x "Simplify, Extend and Clarify"
(Core XLIFF functionality would be in primary XLIFF namespace; would be very simple to implement.)
(Extensions would provide support for more complicated features like, Segmentation, Pre-Translation, Generic Inline Markup, etc.)
xi Schema Catalogues; host a namespace Catalogues
for XLIFF 3rd party custom / extension namespaces.
xii More work on inline-elements:
(Separate inline elements from other elements? Maybe as an extension? Stronger rules for when to use each inline tag?)
xiii Define a multi-lingual "Localisation Kit" format, which may include:
(XLIFF content + original source material+ all target language files+ skeleton files + reference files + some sort of manifest document describing/defining the payload.
xiv Using XLIFF as a primary content authoring container.
(Author stores contend directly to XLIFF instead of another proprietary format.)
xv Terminology Markup
(Has been suggested by Kara Warburton of IBM some time ago to support terminology markup such as translate (yes/no), subject-categorization, type, etc.)
C. Items the TC has ruled out as likely features for XLIFF 2.0
It was agreed that we should have meetings every two weeks while looking at new functionality for version 2.0. The meetings will be on the first and third Tuesday every month.
5/ Reports from liaisons involved with other standards groups:
A. W3C i18n
B. Oscar
C. Trans-WS
D. LRC
E: OASIS DITA Translation Subcommittee
6/ Any Other Business
7/ Next meeting Tuesday April 3rd at 11 AM ET/ 4 PM
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members |
| Achieved quorum |
true |
| Counts toward voter eligibility |
true |
| Individual Attendance |
Members: 9 of 37 (24%)
Voting Members: 9 of 13 (69%) (used for quorum calculation)
|
| Company Attendance |
Companies: 9 of 25 (36%)
Voting Companies: 9 of 12 (75%)
|