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: 1/ Roll call
2/ Approve June 16, 2009 meeting minutes:
Accept, reject, or amend.
http://lists.oasis-open.org/archives/xliff/200906/msg00011.html
3/ Announcements/Quick-turn Issues
A. Problems with official XLIFF samples and Transitional schema
http://lists.oasis-open.org/archives/xliff/200906/msg00013.html
B. XLIFF Checker tool: Perhaps we can update the XLIFF FAQ topic on validation and mention XLIFFChecker there. The FAQ entry is:
http://www.oasis-open.org/committees/xliff/faq.php#Validation
C. 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
4/ 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}
5/ 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)
6/ "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)
7/ XLIFF 2.0
(http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking)
==========
Minutes: Present: Bryan Schnabel, Asgeir Frimannsson, Rodolfo Raya, Yves Savourel, Christian Lieske, David Filip.
Regrets: Dimitra Anastasiou
8
Yves moved to accept previous minutes. Rodolfo seconded and there were no objections.
Bryan explained the problems with the official XLIFF samples and schemas published at OASIS web site. Rodolfo described some of the details that need fixing. Corrections could be published as part of XLIFF 1.2.1. To publish XLIFF 1.2.1 we need to agree on a conformance clause to include in the specifications. Discussion will continue by email.
The possibility to mention XLIFFChecker in the FAQ was discussed. It was agreed that the text at http://www.oasis-open.org/committees/xliff/faq.php#Validation needs to be fixed, as it’s not enough to validate against the schemas. Rodolfo will send an email to the TC proposing a fix for the FAQ entry.
Call dismissed.
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members |
| Achieved quorum |
true |
| Counts toward voter eligibility |
true |
| Individual Attendance |
Members: 6 of 39 (15%)
Voting Members: 6 of 10 (60%) (used for quorum calculation)
|
| Company Attendance |
Companies: 6 of 26 (23%)
Voting Companies: 6 of 10 (60%)
|