XLIFF TC Teleconference

When:  Feb 20, 2007 from 11:00 to 12:00 (ET)
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 ----------------------------------------------------

==========
Agenda: ---------------------------------------------------- 1/ roll call 2/ Approve Previous meeting minutes Accept, reject, or amend. http://www.oasis-open.org/archives/xliff/200701/msg00005.html 3/ Celebrity OASIS Guest, Carol Geyer: XML.org community site for XLIFF. A. From last month's notes "Magnus suggested that it would be a good idea to have people taking responsibility for some of these. We would like to use a WIKI to work on this." B. Refer to Carol's suggestion, posted here: http://www.oasis-open.org/archives/xliff/200702/msg00001.html . 4/ 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. Rename, re-title, repost XLIFF 1.2 Specification and profiles to reflect the Committee Specification status (Rodolfo) 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. Wednesday, March 14 (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, March 21 (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. Thursday, April 1 (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. Thursday, April 15 OASIS members have until the end of the month to vote (1st 14 days are reserved for OASIS members familiarizing themselves with the spec) G. Monday, May 2 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? 5/ 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 6/ Reports from liaisons involved with other standards groups: A. W3C i18n B. Oscar C. Trans-WS D. LRC E: OASIS DITA Translation Subcommittee 7/ Any Other Business ----------------------------------------------------

==========
Minutes: 1/ roll call There were 10 members present as recorded in KAVI New member Micah Bly attended. There may have been an issue with people gaining access to the call as there were problems connecting to the conference call. Bryan will check with Tony whether there are issues with having 2/ Approve Previous meeting minutes Accept, reject, or amend. http://www.oasis-open.org/archives/xliff/200701/msg00005.html Rodolfo proposed to accept last months meeting as a correct record and Bryan seconded this. We agreed this a correct record. 3/ Celebrity OASIS Guest, Carol Geyer: XML.org community site for XLIFF. A. From last month's notes "Magnus suggested that it would be a good idea to have people taking responsibility for some of these. We would like to use a WIKI to work on this." B. Refer to Carol's suggestion, posted here: http://www.oasis-open.org/archives/xliff/200702/msg00001.html . Carol Greyer talked about how they are changing the xml.org web site. They have launched the DITA pages a year ago. Drupel is the technology for managing the content.http://www.drupel.org/ They would like a XLIFF/ Localisation community pages. There are three main sections. These are: • Knowledge base: Material put up by the TC. Specs FAQs etc. This can only be submitted by the TC. • Information submitted by ‘public’ – companies can put up press releases, can contribute about what they are doing. This can be submitted by anyone but can not be edited. • WIKI pages – where people can collaborate – WIKI page on best practises/ deployment. People can submit and the submissions can be edited by others, All pages are viewable by all. Registration is needed to post press releases, blogs etc. TC members are editors. Only these can create pages for the knowledge base. Carol also mentioned that there were advantages for using this as opposed to the existing xml.org Localisation area where you have to go through the OASIS web master to make changes. Lionbridge currently own XLIFF.ORG and XLIFF.COM and this could be transferred to OASIS so that it points to the new site. We had a short discussion on the use of WIKI and it was suggested that it would be good to have WIKI both internally for developing XLIFF and externally for promoting XLIFF. We had a roll call vote to initiate the XLIFF.XML.ORG web site. This was agreed by 8 votes with no abstentions or negative votes. 4/ XLIFF 1.2 Specification status and timeline for approval as a standard Bryan outlined where we were with the XLIFF 1.2 specification. 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. Rename, re-title, repost XLIFF 1.2 Specification and profiles to reflect the Committee Specification status (Rodolfo) 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) Rodolfo will check whether he can do this and liaise with Bryan. 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) The author of the FAQ was Yves Saveroul who is no longer part of the committee but Bryan has agreed to work with Doug on this. 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!) Peter mentioned that Idiom were checking that their technology was compatible with 1.2. Fredrik mentioned that he was checking this at Lionbridge. Christian asked whether he could comment on this as an individual. Bryan will liaise with him over this. v. Wednesday, March 14 (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, March 21 (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. Thursday, April 1 (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. Thursday, April 15 OASIS members have until the end of the month to vote (1st 14 days are reserved for OASIS members familiarizing themselves with the spec) G. Monday, May 2 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? 5/ Next meeting March 20th 11.00 AM ET

==========
Attendance:
Meeting Statistics
Quorum rule 51% of voting members
Achieved quorum true
Counts toward voter eligibility true
Individual Attendance Members: 10 of 37 (27%)
Voting Members: 10 of 13 (76%) (used for quorum calculation)
Company Attendance Companies: 10 of 25 (40%)
Voting Companies: 10 of 12 (83%)