Description: To access the meeting go to:
https://www1.gotomeeting.com/join/277182288
- You can use your microphone and speakers (VoIP)
- Or, call in using your telephone:
Dial: 1-630-869-1010
Access Code: 277-182-288
Meeting ID: 277-182-288
(thanks to Yves for providing this)
==========
Agenda: 1/ Roll call
2/ Approve Tuesday, 16 March 2010 meeting minutes:
Accept, reject, or amend.
http://lists.oasis-open.org/archives/xliff/201003/msg00016.html
3/ Updates on the 1st International XLIFF Symposium
4/ XLIFF Inline text SC report (LISA/OSCAR proposal to re-establish a partnership
in developing common text markup)
1. Bryan and Yves requested OASIS Administrator, Mary to set up the SC
2. Yves' SC report (this is a placeholder for the regular report to the TC)
5/ XLIFF 1.2 Errata Status Update
1. Rodolfo's report
2. Steps are listed in wiki (http://wiki.oasis-open.org/xliff/)
3. OASIS provided an SVN repository
6/ Rodolfo raises questions regarding
1. "Translatable stuff in XLIFF 1.2"(http://lists.oasis-open.org/archives/xliff/201002/msg00012.html)
2. segmentation (http://lists.oasis-open.org/archives/xliff/201002/msg00029.html)
(note: this thread had many facets. The url above is the latest entry,
and also contains references to all the other email)
3. problems with seg-source (http://lists.oasis-open.org/archives/xliff/201002/msg00028.html)
7/ XLIFF 2.0
1. Finish our work regarding text elements in XLIFF 2.0
(http://wiki.oasis-open.org/xliff/OneContentModel/Requirements?action=show&redirect=Requirements).
1.1 Scope section:
1.1.1 Finish items (3.1.2, 3.1.5, 3.1.6)
1.1.2 Bryan will assign action based on each documented resolution
(for example: 3.1.3, (1) Rodolfo adds a note to section 2.5 explaining that extension points are intended
for providing support for internal tool processing, not for solving XLIFF deficiencies.)
1.2 Requirements section:
1.2.1 Validate that each of these are requirements
1.2.2 Identify any missing requirements
1.2.3 Create code examples to show resolution for each requirement
1.2.4 Turn the examples into words for the specification
1.2.5 Turn the examples into code for the schemas
(now for our "where do we go from here moment")
2. Decide how to go forward with remaining (non-text) parts of XLIFF 2.0
2.1 Revisit Feature Tracking (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking)
2.2 Revisit XLIFF 2.0 Dashboard (http://wiki.oasis-open.org/xliff/XLIFF2.0)
3. Write a new Conformance Clause
4. Update the charter
8/ "XLIFF 2.0 will be complete when _______"
There are two camps for filling in the blank
1. 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 -
2. 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)
9/ New Business
==========
Minutes:
==========
Attendance:
| Meeting Statistics |
| Quorum rule |
51% of voting members |
| Achieved quorum |
true |
| Counts toward voter eligibility |
true |
| Individual Attendance |
Members: 9 of 41 (21%)
Voting Members: 9 of 10 (90%) (used for quorum calculation)
|
| Company Attendance |
Companies: 8 of 26 (30%)
Voting Companies: 8 of 9 (88%)
|