OASIS XML Localisation Interchange File Format (XLIFF) TC

Submitter's message Began updating the agenda, and found no updates are needed because none of us has added anything to the mailing list since our last meeting. I will use this as motivation to move my proposals forward.

Looking forward to seeing you all Tuesday! -- Bryan Schnabel Event Title : XLIFF TC Call Date : Tuesday, 03 July 2012, 11:00am - 12:00pm ET Description
Please join my meeting.

 https://www1.gotomeeting.com/join/905529225

Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

   France: +33 (0) 182 880 780

   Germany: +49 (0) 892 2061 159

   Spain: +34 911 23 0850

   Sweden: +46 (0) 852 500 612

   United Kingdom: +44 (0) 203 535 0611

   United States: +1 (773) 945-1031

 

Access Code: 905-529-225

Audio PIN: Shown after joining the meeting

Meeting ID: 905-529-225 This meeting counts towards voter eligibility. Agenda
1/ Roll call

2/ Approve Tuesday, 19 June 2012 meeting minutes:

https://lists.oasis-open.org/archives/xliff/201206/msg00041.html

3/ XLIFF 2.0 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking )

  1.     Features proposed and seconded between meetings via mailing list, and features mentioned

     a. Overloaded http://lists.oasis-open.org/archives/xliff/201202/msg00009.html ?    

     b. Attributes for translation candidates http://lists.oasis-open.org/archives/xliff/201202/msg00082.html ?    

     c. Generic mechanism for translation candidate elements and other annotations http://lists.oasis-open.org/archives/xliff/201203/msg00009.html   ?    

     d. Minor comments on the specifications http://lists.oasis-open.org/archives/xliff/201204/msg00023.html

     e. BiDi draft https://lists.oasis-open.org/archives/xliff/201206/msg00001.html

  2. XLIFF 2.0 Technical work

     a. Approved ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#ApprovedFeaturesforXLIFF2.0 )

     b. Proposed ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#Featuresunderconsideration.28notyetevaluatedbyTC.29 )

     c. Discarded ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#DiscardedProposedFeatures )

  3. XLIFF 2.0 Technical issues ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0 )

     a. translate and xml:space http://lists.oasis-open.org/archives/xliff/201204/msg00045.html ?    

     b. Question about joining/splitting segments http://lists.oasis-open.org/archives/xliff/201204/msg00051.html

      c. Uppercasing conformance keywords https://lists.oasis-open.org/archives/xliff/201206/msg00001.html

  4. Conformance criteria

4/ Sub Committee Reports

   1. Inline text (Yves)

   2. XLIFF Promotion and Liaison SC Charter (David)

5/ Current XLIFF business

   1. Announce Face to face https://lists.oasis-open.org/archives/xliff/201206/msg00010.html

   2. Donna Parrish sent an email to the comments list pointing to the presentation Christian did in Paris. https://lists.oasis-open.org/archives/xliff-comment/201206/msg00004.html

6/ New Business Owner : Bryan Schnabel Group : OASIS XML Localisation Interchange File Format (XLIFF) TC Sharing : This event is not shared to any other groups. BEGIN:VCALENDAR CALSCALE:GREGORIAN METHOD:PUBLISH VERSION:2.0 PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN X-MS-OLK-FORCEINSPECTOROPEN:TRUE BEGIN:VTIMEZONE TZID:America/New_York BEGIN:STANDARD DTSTART:20001029T020000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T060000Z TZNAME:EST TZOFFSETFROM:-0400 TZOFFSETTO:-0500 END:STANDARD BEGIN:STANDARD DTSTART:20071104T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:EST TZOFFSETFROM:-0400 TZOFFSETTO:-0500 END:STANDARD BEGIN:DAYLIGHT DTSTART:20000402T020000 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T070000Z TZNAME:EDT TZOFFSETFROM:-0500 TZOFFSETTO:-0400 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T020000 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:EDT TZOFFSETFROM:-0500 TZOFFSETTO:-0400 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT CATEGORIES:MEETING STATUS:CONFIRMED TRANSP:OPAQUE DTSTAMP:20120701T000000Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20120703T110000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20120703T120000 SEQUENCE:0 SUMMARY:XLIFF TC Call DESCRIPTION:
Please join my meeting.

https://www1.gotomeeting.com/join/905529225

Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

France: +33 (0) 182 880 780

Germany: +49 (0) 892 2061 159

Spain: +34 911 23 0850

Sweden: +46 (0) 852 500 612

United Kingdom: +44 (0) 203 535 0611

United States: +1 (773) 945-1031



Access Code: 905-529-225

Audio PIN: Shown after joining the meeting

Meeting ID: 905-529-225

Agenda:
1/ Roll call

2/ Approve Tuesday, 19 June 2012 meeting minutes:

https://lists.oasis-open.org/archives/xliff/201206/msg00041.html

3/ XLIFF 2.0 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking )

1. Features proposed and seconded between meetings via mailing list, and features mentioned

a. Overloaded http://lists.oasis-open.org/archives/xliff/201202/msg00009.html&#8232 ;

b. Attributes for translation candidates http://lists.oasis-open.org/archives/xliff/201202/msg00082.html&#8232 ;

c. Generic mechanism for translation candidate elements and other annotations http://lists.oasis-open.org/archives/xliff/201203/msg00009.html 


d. Minor comments on the specifications http://lists.oasis-open.org/archives/xliff/201204/msg00023.html

e. BiDi draft https://lists.oasis-open.org/archives/xliff/201206/msg00001.html

2. XLIFF 2.0 Technical work

a. Approved ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#ApprovedFeaturesforXLIFF2.0 )

b. Proposed ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#Featuresunderconsideration.28notyeteval )

c. Discarded ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#DiscardedProposedFeatures )

3. XLIFF 2.0 Technical issues ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0 )

a. translate and xml:space http://lists.oasis-open.org/archives/xliff/201204/msg00045.html&#8232 ;

b. Question about joining/splitting segments http://lists.oasis-open.org/archives/xliff/201204/msg00051.html

c. Uppercasing conformance keywords https://lists.oasis-open.org/archives/xliff/201206/msg00001.html

4. Conformance criteria

4/ Sub Committee Reports

1. Inline text (Yves)

2. XLIFF Promotion and Liaison SC Charter (David)

5/ Current XLIFF business

1. Announce Face to face https://lists.oasis-open.org/archives/xliff/201206/msg00010.html

2. Donna Parrish sent an email to the comments list pointing to the presentation Christian did in Paris. https://lists.oasis-open.org/archives/xliff-comment/201206/msg00004.html

6/ New Business
Group: OASIS XML Localisation Interchange File Format (XLIFF) TC
Creator: Bryan Schnabel URL: https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=33262 UID: https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=33262 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT00H15M00S END:VALARM END:VEVENT END:VCALENDAR

Summary of XLIFF TC Call - July 3 2012 === 1/ Roll call Present: Yves, Bryan, Asanka, DavidW, Klemens, Helena, Jungwoo, Fredrik, Rodolfo, Victor, Tom, Peter, Ingo, DavidF, Joachim, Christian, Michael, Uwe, === 2/ Approve Tuesday, 19 June 2012 meeting minutes: https://lists.oasis-open.org/archives/xliff/201206/msg00041.html Bryan moves to approve the minutes. Tom seconds No objections === 3/ XLIFF 2.0 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking ) Rodolfo: need a list of element for extensibility Yves: will take this as an action item. Fredrik: will move the bidi item to feature list. Bryan: what type of validation for extensions. Rodolfo: strict would be better but can't do this. Lax means if the schema is there you validate Skip means no validation Possible issue with lax too. Need PE for extension (ns and meta) Yves will come up with an initial list too. DavidF: different levels of options. Modules not option if supported. Maybe skip when not supported, lax otherwise. Rodolfo: skip/lax is in schema can't be changed on usage. Fredrik: PE also need to be define when you change the document (discard, etc.) Rodolfo: metadata ready as a module Need to define what we want to do. Could be safely ignorable Bryan: for metadata not the same since part of 'our' namespace Rodolfo: extension should be ignorable Removing is something different. Bryan: agree Yves: +1 Rodolfo: maintaining/updating is something also different (maybe should not be required) DavidF: only if supported. Should not use ext in a way it's mandatory for your round trip. e.g. Apps should not rely on presence of ext for merging back Helena: what is private use of extensions? DavidF: by definition Helena: so it's not private use (different from public). DavidF: module would be 'public' user-ns would be 'private' Bryan: ignore but don't delete may be safer way to go. Worry about case like its:translate DavidF: but we can't use that since we have own translate Fredrik: need very clear rule in place where we modify structure (like on segment. E.g. what to do with the extension). Rodolfo: using attributes in inline element is also an extension Klemens: What about creating a Central repository for Extension Where Tools can Register their Extensions? Rodolfo: we have schemes in wiki, but no documentation Fredrik, DavidF: can't mandate using all extensions DavidF: extension can move to a module stage at some point. Fredrik: allowing removal lower the interest of the extension. e.g. attribute in <xliff> could be preserved by all. Rules may need to be defined per location. Rules must be not link to the functionality of the extension Christian: I would suggest that we craft a clause for "extensions" that is similar for example to http://www.w3.org/TR/REC-xml/#sec-white-space Rodolfo: +1 Bryan: a lot of work will be needed on this. Rodolfo: about Processing Expectations. Should we not allow translate property to be changed? Fredrik: +1 But we need a 'lock' feature too At unit and inline level. DavidF: think the process should decide if translate flag can be changed or not, not the spec. Klemens +1 Fredrik: some cases are dangerous. E.g. when it *cannot* be translated (and merged back translated). DavidF: changing translate at local level should be allowed Joachim: any real case for translate=no to yes? DavidF: open issue, for example segmentation change. So translate flag may be wrong. Should be decided at process time Fredrik: then going to yes should mean that that translation may not be merged. Christian: not sure if we started to defined PE in a structure fashion. Rodolfo: no one volunteered. Fredrik: did this for editing target in inline content. We should do this for all different areas that are stable. Rodolfo: did add some PE as I was writing it. But we need feedback. DavidF: agree with Fredrik. Feature owner sould draft that. We also need PR processing requirements So they can be used in conformance statement. Rodolfo: like MUST and SHOULD DavidF: yes we can use them, but PE is not normative PR are normative New soon member: Michael Ow (IBM) Also: Klemens officially in TC now. === 4/ Sub Committee Reports --- 1. Inline text (Yves) Fredrik did gave a summary of the F2F meeting last time. Out next call is next week. Currently Yves is working on editing the spec to reflect the changes/fixes generated during the face-to-face. We are reaching the end. Hope to have something quite stable by the end of summer. --- 2. XLIFF Promotion and Liaison SC Charter (David) - Sent an email to TC to promote 3rd symposium http://localizationworld.com/lwseattle2012/feisgiltt/ http://www.localizationworld.com/lwseattle2012/feisgiltt/xliffcall.html http://linkd.in/L4t8vj try to engage with bloggers End of July is deadline for call. So far: Interesting proposal from Microsoft. Christian: we had summary for the 1st symposium. Did it happened for 2nd? DavidF: no But we could summarize it before. Christian: we should demonstrate we act on the community input. Peter Reynolds (to All - Entire Audience): David, Kevin Lossner is visiting me next week and I will get him to blog about it. Is there a tweet hash tag Lets discuss Christian's at the sub committee We also need better attendance at this event The XLIFF TC was not as well represented as it could have been at the last one --- 5/ Current XLIFF business 1. Announce Face to face https://lists.oasis-open.org/archives/xliff/201206/msg00010.html Bryan: face-to-face TC meeting in Seattle. 2. Donna Parrish sent an email to the comments list pointing to the presentation Christian did in Paris. https://lists.oasis-open.org/archives/xliff-comment/201206/msg00004.html === 6/ New Business Fredrik: group for 2.0? Yves: +1 Rodolfo: There is a proposal. -done