OASIS XML Localisation Interchange File Format (XLIFF) TC

Submitter's message Added item 3/3.a Source read-only or not?

(good catch Yves)
-- Bryan Schnabel Event Title : XLIFF TC Call Date : Tuesday, 03 April 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, 20 March 2012 meeting minutes:
http://lists.oasis-open.org/archives/xliff/201203/msg00076.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. Proposed and seconded: (B25) Preserve metadata without using extensibility" (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#XLIFF2.0.2BAC8-Feature.2BAC8-PreserveXMLattributeormetadatawithoutextensibility.A.28B25.29Preservemetadatawithoutusingextensibility )
        - Extensibility sub thread (http://lists.oasis-open.org/archives/xliff/201203/msg00077.html)
        - Implementing extensions sub thread (http://lists.oasis-open.org/archives/xliff/201203/msg00078.html )

   Note: Listing items from email threads between meetings. But any feature/issue may be brought to the floor.
 
     b. Overloaded http://lists.oasis-open.org/archives/xliff/201202/msg00009.html
     c. String length constraint (should be added to wiki) http://lists.oasis-open.org/archives/xliff/201202/msg00059.html
     d. Attributes for translation candidates http://lists.oasis-open.org/archives/xliff/201202/msg00082.html
     e. Unified XML schema for XLIFF 2.0 http://lists.oasis-open.org/archives/xliff/201202/msg00099.html
     f. Generic mechanism for translation candidate elements and other annotations http://lists.oasis-open.org/archives/xliff/201203/msg00009.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. Source read-only or not? (http://lists.oasis-open.org/archives/xliff/201204/msg00004.html)
 
  4. Conformance criteria
 
4/ Sub Committee Reports
   1. Inline text (Yves)
   2. XLIFF Promotion and Liaison SC Charter (David)
      a. David formally proposes to create a formal liaison with MultilingualWeb-LT and nominate Arle Lommel to serve as the first XLIFF TC liaison on MultilingualWeb-LT (http://lists.oasis-open.org/archives/xliff/201203/msg00091.html )
      b. XLIFF support in CAT tools Survey (http://lists.oasis-open.org/archives/xliff/201204/msg00001.html)
 
5/ Current XLIFF business
Note: moved XLIFF, TM, Glossary, Segmentation and Using other standards off current business agenda (assume they are covered on wiki proposed featutres and inline text SC). If my assumption is incorrect - please let me know.

   1. Normalized the state values in wiki http://lists.oasis-open.org/archives/xliff/201203/msg00045.html
   2. Propose limiting the number of features in the wiki (Rodolfo) http://lists.oasis-open.org/archives/xliff/201203/msg00064.html
   3. Proposed OASIS XLIFF TC liaison with MultilingualWeb-LT (David) http://lists.oasis-open.org/archives/xliff/201203/msg00066.html

6/ New Business     
  Owner : Bryan Schnabel Group : OASIS XML Localisation Interchange File Format (XLIFF) TC Sharing : This event is shared with the OASIS Open (General Membership), and General Public groups. Public Event Link 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:20120403T000000Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20120403T110000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20120403T120000 SEQUENCE:2 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, 20 March 2012 meeting minutes:
http://lists.oasis-open.org/archives/xliff/201203/msg00076.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. Proposed and seconded: (B25) Preserve metadata without using extensibility" ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#XLIFF2.0.2BAC8-Feature.2BAC8-PreserveXMLattributeormetadatawithoutextensibility.A.28B25.29Preservemetadatawithoutusingextensibility )
- Extensibility sub thread ( http://lists.oasis-open.org/archives/xliff/201203/msg00077.html )
- Implementing extensions sub thread ( http://lists.oasis-open.org/archives/xliff/201203/msg00078.html )

Note: Listing items from email threads between meetings. But any feature/issue may be brought to the floor.

b. Overloaded http://lists.oasis-open.org/archives/xliff/201202/msg00009.html
c. String length constraint (should be added to wiki) http://lists.oasis-open.org/archives/xliff/201202/msg00059.html
d. Attributes for translation candidates http://lists.oasis-open.org/archives/xliff/201202/msg00082.html
e. Unified XML schema for XLIFF 2.0 http://lists.oasis-open.org/archives/xliff/201202/msg00099.html
f. Generic mechanism for translation candidate elements and other annotations http://lists.oasis-open.org/archives/xliff/201203/msg00009.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. Source read-only or not? ( http://lists.oasis-open.org/archives/xliff/201204/msg00004.html )

4. Conformance criteria

4/ Sub Committee Reports
1. Inline text (Yves)
2. XLIFF Promotion and Liaison SC Charter (David)
a. David formally proposes to create a formal liaison with MultilingualWeb-LT and nominate Arle Lommel to serve as the first XLIFF TC liaison on MultilingualWeb-LT ( http://lists.oasis-open.org/archives/xliff/201203/msg00091.html )
b. XLIFF support in CAT tools Survey ( http://lists.oasis-open.org/archives/xliff/201204/msg00001.html )

5/ Current XLIFF business
Note: moved XLIFF, TM, Glossary, Segmentation and Using other standards off current business agenda (assume they are covered on wiki proposed featutres and inline text SC). If my assumption is incorrect - please let me know.

1. Normalized the state values in wiki http://lists.oasis-open.org/archives/xliff/201203/msg00045.html
2. Propose limiting the number of features in the wiki (Rodolfo) http://lists.oasis-open.org/archives/xliff/201203/msg00064.html
3. Proposed OASIS XLIFF TC liaison with MultilingualWeb-LT (David) http://lists.oasis-open.org/archives/xliff/201203/msg00066.html

6/ New Business

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

XLIFF TC Call - April 3rd 2012 - Summary === 1/ Roll call Present: Lucia, Rodolfo, Shirley, Tom, Victor, Arle, Asanka, Bryan, DavidW, Fredrik, Helena, Ingo, Joachim, Klemens, Steven, Jung, DavidF, Christian. Regrets: Paul === 2/ Approve Tuesday, 20 March 2012 meeting minutes: http://lists.oasis-open.org/archives/xliff/201203/msg00076.html Bryan moves to approve the minutes Arle, Rodolfo second No objections. === 3/ XLIFF 2.0 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking ) Reference implementation: Rodolfo: want to pass ownership to someone else Yves: could take it DavidF: could split reference implementation and validation tool Bryan: Yves to get R30 and Rodolfo get new feature for a validation tool Christian: would need explanation of validation tool would do. Rodolfo: same as XLIFF-Checker. Christian: we may need more in term of definition (i.e. what is checked) Also what goes into schema vs tool-only Fredrik: also maybe to supply two files and validate the modifications Rodolfo, DavidF: +1 DavidF: Propose to have a formal ballot Bryan: This is different than what we did in the past. Rodolfo: sure, I will add the item in the wiki DavidF: proposed this because R30 was approved already Bryan: fine, we just need to make sure the item is clear Christian: I would also like to see a definition of "Reference Implementation" Rodolfo: yes, will add a proposed feature in the wiki. ACTIOn ITEM: Yves to take ownership of R30 (done by Rodolfo, thanks) --- 1. Features proposed and seconded between meetings via mailing list, and features mentioned c. String length constraint (should be added to wiki) http://lists.oasis-open.org/archives/xliff/201202/msg00059.html Fredrik: we need an attribute (or more) for this. Rodolfo: just characters should be fine. Fredrik: we do use plugins to test other units DavidF: this is example of a basic functionality with extended facility needed too. Propose that Fredrik define the feature in the wiki Fredrik: advance support could be supported with extensibility. But what should we have for the basic feature? Just chars? Bryan: 1.2 tend to try to provide too much, in general the smaller the picklist the better Rodolfo: yes, just char should be enough for the basic feature. DavidF: what about bytes Rodolfo, Arle: Unicode chars better Joachim: fullwidth vs normal may be different? Fredrik, Rodolfo: too much maybe. Helena: you are mixing processing and display Fredrik: for length check it may be important Helena: is it for display or for process/buffer? Steven: Simplest is to count Unicode chars (so max length for the process) Helena: what the char is (zero-width, etc.) is for the tool to decide Arle: MLW-LT is also looking at this. Interoperability would be nice. Joachim: just Unicode char count would be the easiest. Rendering length would need more (font, etc.) Fredrik: just counting code-point may not be useful Rodolfo: let's describe the feature in the wiki Arle: two use cases: UI and DB (rendering and buffer/process) Fredrik: buffer length also need encoding info Helena: trying to understand the user scenario Could use average size by char in most cases Knowing length by code point gives a starting point Joachim: agree we won't have a full solution for all cases Fredrik: not sure if I like the proposed feature That feature is in 1.2 and is used, but it's not in 2.0 It needs to be resolved in 2.0 Could drop it too Joachim: but production would need it. Bryan: a proposed feature in the wiki could be a good starting point Just need to see what use cases are possible and which one we want 2.0 to support Use of wiki: Bryan: will try to create a video to explain how to use the wiki d. Attributes for translation candidates http://lists.oasis-open.org/archives/xliff/201202/msg00082.html Helena: Yves, I want to follow up on the "translation candidate attribute" thread off line. Will do by email. --- 3. XLIFF 2.0 Technical issues ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0 ) a. Source read-only or not? ( http://lists.oasis-open.org/archives/xliff/201204/msg00004.html ) Rodolfo: seems source does not need to be read-only Bryan: some aspects may need discussion in Inline Markup SC. === 4/ Sub Committee Reports --- 1. Inline text (Yves) No meeting. Not much to report on. Will have a face-to-face meeting in Dublin on June-14/15 --- 2. XLIFF Promotion and Liaison SC Charter (David) No SC meeting today. XLIFF symposium for 15-17 Oct as pre-event of LocWorld Federated event with LocWorld, MLW-LT and ULI Call for volunteers for the review committee (to review proposal) a. David formally proposes to create a formal liaison with MultilingualWeb-LT and nominate Arle Lommel to serve as the first XLIFF TC liaison on MultilingualWeb-LT ( http://lists.oasis-open.org/archives/xliff/201203/msg00091.html On Mar-29 I move to have that vote. Joachim seconded today. Christian: proposal is to liaise with W3C WG or the MLW-LT project? DavidF: the W3C WG Christian: would imagine the W3C has rules for these liaisons DavidF: W3C is clear for this. The WG has dependency to XLIFF in charter Liaison from XLIFF TC -> WG is decided by TC. Bryan: responsibility of Arle/davidF to make sure the liaison follows rules b. XLIFF support in CAT tools Survey ( http://lists.oasis-open.org/archives/xliff/201204/msg00001.html ) Lucia started the new questionnaire We have already some answers completed Should get info from most no-show of previous round Arle: anyone interested in LOD or MLW-LT workshop (second week of June in Dublin) should contact Arle. === 5/ Current XLIFF business Note: moved XLIFF, TM, Glossary, Segmentation and Using other standards off current business agenda (assume they are covered on wiki proposed featutres and inline text SC). If my assumption is incorrect - please let me know. --- 1. Normalized the state values in wiki http://lists.oasis-open.org/archives/xliff/201203/msg00045.html Bryan: make sure to look at wiki for the changes. Should help to get final approval later on. --- 3. Proposed OASIS XLIFF TC liaison with MultilingualWeb-LT (David) http://lists.oasis-open.org/archives/xliff/201203/msg00066.html This one is done. === 6/ New Business None.