Description: 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 (805534) - Note: this is the new password
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/200705/msg00011.html
3/ XLIFF 1.2 Passed as Committee Specification (a yes vote came in from every voting member)
A. Because of the calendar, and the desire to pass the spec in time to not have to comply with a new requirement for certification, the spec included a known typo:
"Extensible Markup Language (XML) 1.0 Second Edition. W3C (World Wide Web Consortium), 29 Sep 2006"
(There was never a Second Edition with a date of 29 Sep 2006)
"Extensible Markup Language (XML) 1.0. W3C (World Wide Web Consortium)"
B. According to our TC Administrator, we can fix the typo, and have her initiate a new ballot to pass the corrected version as a Committee specification (no public review required, don't need to change our certification method to comply with the new requirements)
4/ Two comments came in from Asgeir Frimannsson
"XLIFF 1.2 seg-source extension point"
http://www.oasis-open.org/archives/xliff/200705/msg00014.html
"XLIFF 1.2 phase-name attribute inconsistency"
http://www.oasis-open.org/archives/xliff/200705/msg00015.html
5/ Next steps
A. May 22, Roll Call Vote: Approve Request for initiation of a Committee Spec Ballot (passed)
B. May 31, TC Ballot: Approval XLIFF v1.2 as a Committee Specification (passed)
[next steps before moving to item C.]
i. Rename, re-title, repost XLIFF 1.2 Specification and profiles to reflect the Committee Specification status (Rodolfo)
ii. Update whitepaper (Bryan will begin this; Rodolfo and Tony will contribute - Tony located the latest version here: http://www.oasis-open.org/apps/org/workgroup/xliff/document.php?document_id=3111)
iii. Update FAQ (Doug, Christian, Rodolfo's work is here: http://wiki.oasis-open.org/xliff/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 available as soon as we need it)
- Peter Reynolds, Idiom Technologies, Inc
- Reinhard Schaler, Localisation Research Centre
(thanks to each member for attempting to obtain certification!)
## Tony said that LISA is also a qualified organization and that we could ask Michael or Arle
## Rodolfo said he can get a certification form Arle or Michael (Rodolfo is a member of the OSCAR Steering Committee)
v. [Date TBD] (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
C. [Date TBD] 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
D. [Date TBD] (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
E. [Date TBD] OASIS members have until the middle of the month to vote (1st 14 days are reserved for OASIS members familiarizing themselves with the spec)
F. [Date TBD] If at least 15% of OASIS voting membership has voted to approve, and no negative votes, XLIFF
1.2 becomes an OASIS Standard.
6/ 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"})
- Feature updates:
- - Update to XLIFF 1.2
- - Add option to produce minimalist or maximalist XLIFF round trip
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.)
xvi [added April 15] Propose we create a requirements document for XLIFF 2.0 along the lines of the requirements document the W3C's XSLT committee
drafted for their XSLT 2.0 requirements: http://www.w3.org/TR/xslt20req
C. Items the TC has ruled out as likely features for XLIFF 2.0
7/ Reports from liaisons involved with other standards groups:
A. W3C i18n
B. Oscar
C. Trans-WS
D. LRC
E: OASIS DITA Translation Subcommittee
8/ Any Other Business
==========
Minutes: 1. roll call
Doug Tony Milan Bryan Rodolfo Christian
2. Tony moves to approve minutes. Doug seconds. None opposes.
3. Discussion about the typo found in XML reference in the specification. Two options were given: correct the typo now and initiate the procedure for obtaining OASIS specification status or leave the type to be corrected at a later time. A vote for correcting the typo was conducted:
- Tony yes
- Milan yes
- Rodolfo yes
- Bryan yes
- Christian yes
- Doug yes
Rodolfo has to fix the typo and send new files to Bryan.
Asgeir comment regarding was discussed. Vote is to agree that the comment refers to a non-substantial change to the specification and the incorrect link should be removed.
- Tony yes
- Milan yes
- Rodolfo yes
- Bryan yes
- Christian yes
- Doug yes
Comment about description of "phase-name" attribute in element is not relevant. It is not necessary to change the specs now. Description of the element can be enhanced later.
It is not necessary to wait until next vote passes to request the affidavits. Bryan will check with Mary the best way to collect them.
We are optimistically recruiting new members. Tony discussed with Mateo Pedersoli regarding potential contributors.
The creation of a subcommittee for XLIFF adoption was suggested.
There will be a meeting on June 19 and then eventually we will go back to one meeting per month.
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members |
| Achieved quorum |
true |
| Counts toward voter eligibility |
true |
| Individual Attendance |
Members: 6 of 38 (15%)
Voting Members: 6 of 11 (54%) (used for quorum calculation)
|
| Company Attendance |
Companies: 6 of 25 (24%)
Voting Companies: 6 of 11 (54%)
|