Description: 1/ Call one of the FreeConferenceCall phone numbers:
US: (712) 432-1600
US: (605) 772-3100
Austria: 0820 4000 1552
Belgium: 070 35 9974
France: 0826 100 256
Germany: 01805 00 76 09
Ireland: 0818 270 021
Italy: 848 390 156
Netherlands: 0870 001 920
Spain: 902 886025
Switzerland: 0848 560 179
UK: 0870 35 204 74
2/ Enter the Participant Access Code: 737043#
==========
Agenda: Agenda:
1/ Roll call
2/ Approve July 07, 2009 meeting minutes:
Accept, reject, or amend.
http://lists.oasis-open.org/archives/xliff/200907/msg00007.html
3/ Announcements/Quick-turn Issues
A. Bryan is working with the Drupal owner to update its support of XLIFF to XLIFF 2.0. Making good progress
http://lists.oasis-open.org/archives/xliff/200906/msg00009.html
B. Rodolfo will propose a fix for the FAQ text at http://www.oasis-open.org/committees/xliff/faq.php#Validation
4/ XLIFF 1.2.1 must now be moved to "front burner" now that errors have been identified in the samples
A. Good news, Schemas, Samples, and Spec are all fixed and ready to be voted on
B. We must include a conformance clause in order to bring XLIFF 1.2.1 to ballot
i. Do we create a very lax conformance clause for 1.2.1, and go back to working on 2.0? And move the work to email?
ii. Do we create a robust conformance clause in order to have a good starting point for 2.0's clause?
5/ Review Requirements for inline elements [define, understand, then vote - being mindful of Tony's suggestion of limiting the length of discussion]
(come to consensus on the requirements, then assign owners to propose wording for the spec)
(http://wiki.oasis-open.org/xliff/OneContentModel/Requirements?action=show&redirect=Requirements)
{here's my *score card*:
1.1. Definitions/Terminology
"This section is under construction. " (additional examples have been added)
3.1.1. Common representation of 'inline' markup vs 'block-level' markup
1. [Resolved]
2. [Resolved]
3. [Not Resolved]
3.1.2. Canonical Representation of native content
[Not Resolved - Christian annotated a distinction:
"Maybe, we may want to differentiate between two types of canonical representation:"
1. a semantic/abstract one
2. an encoded/concrete one]
3.1.3. Extensibility / Annotations
["Christian will modify item 3.1.3 and separate extensibility
from annotations. Action item: Christian to extend the text
to clarify the scope and meaning of the request.]
3.1.4. [Resolved] Content Manipulation
3.1.5. [Not yet addressed] XML Implementation
3.1.6. [Not yet addressed] General Scope}
6/ If something is valid XML and not disallowed explicitly by the specification, it means it is allowed?(http://lists.oasis-open.org/archives/xliff/200906/msg00008.html) (Question captured from Yves' comment on Rodolfo's XLIFF Checker Tool)
7/ "XLIFF 2.0 will be complete when _______"
There are two camps for filling in the blank
A. Set a calendar goal. All items that are complete and approved by the
TC make it into XLIFF 2.0 - All others need to wait for the "next train,"
i.e., XLIFF 2.X or XLIFF 3. Special care needs to be taken to define
doneness and ensure no dependency issues between items.
And "XLIFF 2.0 is complete on set date of *Month/Day/Year*"
- or -
B. Define a finite set of XLIFF 2.0 items. Set a cutoff date for adding items.
The list of accepted items becomes our requirements document.
And "XLIFF 2.0 is complete when items 1 through X are finished"
(some in this camp see our current set of goals, as is, as that
finite list)
i. Yves commented that XLIFF is not a software. And we should be careful with releasing versions that do not have some specific features we know will ultimately end up there. (http://lists.oasis-open.org/archives/xliff/200904/msg00018.html)
8/ XLIFF 2.0
(http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking)
==========
Minutes: Present: Doug Domeny, Yves Savourel, Bryan Schnabel, Dimitra Anastasiou, Lucia Morado Vazquez, Rodolfo Raya, David Filip, Asgeir Frimannsson, Christian Lieske, Magnus Martikainen.
Regrets: Tony Jewtushenko, Johann Roturier
Rodolfo moved to approve previous minutes, Yves seconded and none objected.
Bryan announced that he is working with Drupal developers in the implementation of XLIFF 1.2 support in Drupal.
Rodolfo will send an email with a proposal for updating the FAQ regarding validation.
Dimitra explained that she is working with a group of people interested in enhancing metadata support in XLIFF. She is interested in working with some of the features listed in the wiki for XLIFF 2.0 and perhaps proposes new ones. Discussion will continue by email.
Bryan explained that it would be important to go back to work on XLIFF 1.2.1 now that errors in the examples and Schemas have been identified.
The conformance clause to include in XLIFF 1.2.1 was discussed. Two options were presented: define conformance for XLIFF files only or conformance for XLIFF files and applications that support XLIFF. Christian requested a written draft to better evaluate the options. Rodolfo said that he would prepare an initial draft. Conversation will continue by email.
Call dismissed.
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members |
| Achieved quorum |
true |
| Counts toward voter eligibility |
true |
| Individual Attendance |
Members: 10 of 39 (25%)
Voting Members: 9 of 10 (90%) (used for quorum calculation)
|
| Company Attendance |
Companies: 9 of 26 (34%)
Voting Companies: 9 of 10 (90%)
|