OASIS XML Localisation Interchange File Format (XLIFF) TC

Reminder to our European members that our meeting is still on US Eastern time (now). Kavi did not change, as your continent did last week.

Thanks,

Bryan

________________________________________
From: bryan.s.schnabel@tektronix.com [bryan.s.schnabel@tektronix.com]
Sent: Sunday, October 31, 2010 6:59 PM
To: xliff@lists.oasis-open.org
Subject: [xliff] Groups - XLIFF TC Telelconference added

XLIFF TC Telelconference has been added by Bryan Schnabel*

Date:  Tuesday, 02 November 2010
Time:  11:00am - 12:00pm ET

Event 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
(meeting setup Courtesy of Yves)

Agenda:
1/ Roll call

2/ Approve Tuesday, 19 October 2010 meeting minutes:
   Accept, reject, or amend.
(http://lists.oasis-open.org/archives/xliff/201010/msg00009.html)

3/ Current XLIFF business
  1. Expression if gratitude to Doug for his many contributions, and best wishes on his future activities
  2. Dee Schur announced the OASIS OAXAL Webinar, 16, November
     (http://lists.oasis-open.org/archives/xliff/201010/msg00020.html)
  3. David proposes a ballot on *conformance criteria and processing requirements in xliff 2.0*
     (http://lists.oasis-open.org/archives/xliff/201010/msg00002.html).
    a. This is the wording as David indicated in the 19 October meeting
----- ballot wording:
TC sets as the following methodological principles for XLIFF 2.0 re conformance and processing:
 1. Each element and data type must be accompanied by clearly specified conformance criteria
 2. Conformance criteria must be binary, i.e. satisfied or failed, no shades of grey or levels of support.
 3. Conformance criteria must include well-formedness and processing requirements
 4. Processing requirements must be defined in terms of well-formedness and specific allowed values of elements and data types before and after processing.
-----
    b. Christian initiated the "Input to discussion on Conformance"
       (http://lists.oasis-open.org/archives/xliff/201010/msg00013.html)

  4. Move our spec into Docbook (http://lists.oasis-open.org/archives/xliff/201007/msg00009.html)
    a. Filter current spec into Docbook (Bryan)
    b. Rodolfo to add Docbook spec to OASIS
  5. ISO/OASIS XLIFF - XLIFF as an ISO standard (Peter) (http://lists.oasis-open.org/archives/xliff/201008/msg00029.html)
  6. RDF + XLIFF (Dimitra)
  7. Christian's usage scenarios for having a MIME-type for XLIFF (http://lists.oasis-open.org/archives/xliff/201010/msg00004.html)

4/ XLIFF Inline text SC report (LISA/OSCAR proposal to re-establish a partnership
   in developing common text markup)
  1. Yves' SC report

5/ XLIFF Symposium Debrief: "Voice of our customer"
   Christian began the Consolidated takeaways wiki page (http://wiki.oasis-open.org/xliff/Consolidated%20Takesaways%20from%20First%20XLIFF%20Symposium)
   Christian's slides: http://www.oasis-open.org/apps/org/workgroup/xliff/download.php/39848/2010-10-08_1st%20XLIFF%20Symposium%20-%20XLIFF%20TC%20Summary-draft.pdf
   The "Voice of the Customer": Place for all attendee to comments here: (http://wiki.oasis-open.org/xliff/Consolidated%20Takesaways%20from%20First%20XLIFF%20Symposium )


6/ Conformance (Here are the OASIS Guidelines: http://docs.oasis-open.org/templates/TCHandbook/ConformanceGuidelines.html)
  (See also 3.3)
  1. Rodolfo started a thread on his first draft (http://lists.oasis-open.org/archives/xliff/201006/msg00001.html)
  2. Yves started a thread on Conformance/compliance (http://lists.oasis-open.org/archives/xliff/201006/msg00002.html)

7/ Charter
  The current charter is here: (http://www.oasis-open.org/committees/xliff/charter.php)

8/ XLIFF 2.0
  1. Simplified XLIFF element tree (http://lists.oasis-open.org/archives/xliff/201008/msg00012.html)
     and Christian's idea of Domains (http://lists.oasis-open.org/archives/xliff/201009/msg00004.html)
  (we now have 4 approved new features and 11 proposed features to be evaluated)
  2. Asgeir started a thread on multiple File elements (http://lists.oasis-open.org/archives/xliff/201006/msg00012.html)
     - discuss this here, or move it to the Feature Tracking page?
  3. Review items from XLIFF 2.0 Dashboard (http://wiki.oasis-open.org/xliff/XLIFF2.0)
    (move any items to Feature Tacking Section?)
  4. Review items approved in section 1 (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking)
  5. Begin work evaluating proposed features

9/ 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)

10/ New Business

Minutes:


View event details:
http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=28715

PLEASE NOTE:  If the above link does not work for you, your email
application may be breaking the link into two pieces.  You may be able to
copy and paste the entire link address into the address field of your web
browser.

XLIFF TC Teleconference - Summary
Date:  Tuesday, 02 November 2010
Time:  11:00am - 12:00pm ET

=== 1/ Roll call

Presents: Arle, Bryan, Asgeir, Yves, Rodolfo, Christian, Andrew, David, Lucia
Regrets: Dimitra
Absents: Peter


=== 2/ Approve Tuesday, 19 October 2010 meeting minutes:
(http://lists.oasis-open.org/archives/xliff/201010/msg00009.html)

Bryan moves to accept the minutes
Rodolfo seconds
No dissent

Rodolfo: modify the charter requires a ballot and we can't keep modifying it.



=== 3.1. Expression if gratitude to Doug for his many contributions, and best wishes on his future activities

Note for member count: Doug has left his company, so not a voting member now.
Bryan: TC is very grateful for Doug's contribution
Did a lot of work (transitional/strict, representation guide, etc.)



=== 3.2. Dee Schur announced the OASIS OAXAL Webinar, 16, November
(http://lists.oasis-open.org/archives/xliff/201010/msg00020.html)

XLIFF figures prominently in OAXAL.



=== 3.3. David proposes a ballot on *conformance criteria and processing requirements in xliff 2.0*
(http://lists.oasis-open.org/archives/xliff/201010/msg00002.html).
a. This is the wording as David indicated in the 19 October meeting
----- ballot wording:
TC sets as the following methodological principles for XLIFF 2.0 re conformance and processing:
1. Each element and data type must be accompanied by clearly specified conformance criteria
2. Conformance criteria must be binary, i.e. satisfied or failed, no shades of grey or levels of support.
3. Conformance criteria must include well-formedness and processing requirements
4. Processing requirements must be defined in terms of well-formedness and specific allowed values of elements and data types before and after processing.
----- 
b. Christian initiated the "Input to discussion on Conformance" 
(http://lists.oasis-open.org/archives/xliff/201010/msg00013.html)


Rodolfo: info for conformance for each element and attribute, so most of this is fine.
But can't define processing requirements for conformance
Conformance of document, not conformance of application.

Arle: Example file v.s. browser. 
Rodolfo: MSIE and FF for example, different rendering with same valid HTML

Bryan: example with ITS?
Yves: ITS is a processing standard, so maybe a bit different.

R: DITA is another example: same file, different outputs.
We can set processing expectations for attributes, etc. but we cannot have this as a conformance.

Arle: difference between file conformance and semantics
Bryan: For example removing group cannot be conformance then?
Rodolfo: it's important but it cannot be validated
Another example: modifying the source with