OASIS XML Localisation Interchange File Format (XLIFF) TC

  • 1.  Groups - Event "XLIFF TC Call" modified

    Posted 11-01-2011 14:27
      |   view attached
    Submitter's message Added David's proposal for 3.2 -- Bryan Schnabel Event Title : XLIFF TC Call Date : Tuesday, 01 November 2011, 11:00am - 12:00pm ET Description 1.  Please join my meeting.
    https://www1.gotomeeting.com/join/905529225
    2.  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, 04 October 2011 meeting minutes:
        http://lists.oasis-open.org/archives/xliff/201110/msg00009.html

    3/ Sub Committee Reports
     1.  Inline text (Yves)
     2. XLIFF Promotion and Liaison SC Charter (David)
    - Vote on David's proposal for features for 2.0 (http://lists.oasis-open.org/archives/xliff/201111/msg00002.html)
     
    4/ XLIFF 2.0 (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking)
        Note: perhaps we need to add permanent tracking ids to titles, and not need to worry about preserving numbering scheme?

      1.  XLIFF 2.0 Technical work
          a. Code and content comparison (good discussion at 18Oct2011, non-binding meeting - tracked in Inline SC)
          b. Representing starting/ending/stand-alone parts (good discussion at 18Oct2011, non-binding meeting - tracked in Inline SC)
          c. Segmentation feature (good discussion at 18Oct2011, non-binding meeting - tracked wiki)

      2.  XLIFF 2.0 Technical issues
          a. Added this category to FeatureTracking wiki page (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking)
             - Does this work?

      3.  Conformance criteria (good discussion at 18Oct2011, non-binding meeting)

    5/ Current XLIFF business
      Note: Moved some items to P & L SC; some remaining things need TC approval to move
     
      1. XLIFF and TM, Glossary, Segmentation Rules (Christian)
         Note: shall we move this to Technical Issues for XLIFF 2.0 wiki page (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0)?
           (http://lists.oasis-open.org/archives/xliff/201105/msg00043.html)
           - - Need a full discussion on this topic (Peter)
              (http://lists.oasis-open.org/archives/xliff/201105/msg00047.html)
      2. Gathering common extension points from
          existing XLIFF Tools as a guide for 2.0 features (Bryan, Thomas)
          Note: Bryan will propose moving this to P & L SC
          (http://lists.oasis-open.org/archives/xliff/201101/msg00007.html)
         - Lucia has taken over Micah's matrix
         - David F is investigating funding for XLIFF tools page
      3. Using other standards vs. adding XLIFF modules (Arle, David W., Yves, Helena, . . .)
          Note: shall we move this to Technical Issues for XLIFF 2.0 wiki page (http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0)?
          (http://lists.oasis-open.org/archives/xliff/201107/msg00023.html)
         (http://lists.oasis-open.org/archives/xliff/201108/msg00001.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:20111101T000000Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20111101T110000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20111101T120000 SEQUENCE:2 SUMMARY:XLIFF TC Call DESCRIPTION:1. Please join my meeting.
    https://www1.gotomeeting.com/join/905529225
    2 . 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, 04 October 2011 meeting minutes:
    http://lists.oasis-open.org/archives/xliff/201110/msg00009.html

    3/ Sub Committee Reports
    1. Inline text (Yves)
    2. XLIFF Promotion and Liaison SC Charter (David)
    - Vote on David's proposal for features for 2.0 ( http://lists.oasis-open.org/archives/xliff/201111/msg00002.html )

    4/ XLIFF 2.0 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking )
    Note: perhaps we need to add permanent tracking ids to titles, and not need to worry about preserving numbering scheme?

    1. XLIFF 2.0 Technical work
    a. Code and content comparison (good discussion at 18Oct2011, non-binding meeting - tracked in Inline SC)
    b. Representing starting/ending/stand-alone parts (good discussion at 18Oct2011, non-binding meeting - tracked in Inline SC)
    c. Segmentation feature (good discussion at 18Oct2011, non-binding meeting - tracked wiki)

    2. XLIFF 2.0 Technical issues
    a. Added this category to FeatureTracking wiki page ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking )
    - Does this work?

    3. Conformance criteria (good discussion at 18Oct2011, non-binding meeting)

    5/ Current XLIFF business
    Note: Moved some items to P & L SC; some remaining things need TC approval to move

    1. XLIFF and TM, Glossary, Segmentation Rules (Christian)
    Note: shall we move this to Technical Issues for XLIFF 2.0 wiki page ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0 )?
    ( http://lists.oasis-open.org/archives/xliff/201105/msg00043.html )
    - - Need a full discussion on this topic (Peter)
    ( http://lists.oasis-open.org/archives/xliff/201105/msg00047.html )
    2. Gathering common extension points from
    existing XLIFF Tools as a guide for 2.0 features (Bryan, Thomas)
    Note: Bryan will propose moving this to P & L SC
    ( http://lists.oasis-open.org/archives/xliff/201101/msg00007.html )
    - Lucia has taken over Micah's matrix
    - David F is investigating funding for XLIFF tools page
    3. Using other standards vs. adding XLIFF modules (Arle, David W., Yves, Helena, . . .)
    Note: shall we move this to Technical Issues for XLIFF 2.0 wiki page ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0 )?
    ( http://lists.oasis-open.org/archives/xliff/201107/msg00023.html )
    ( http://lists.oasis-open.org/archives/xliff/201108/msg00001.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=31884 UID: http://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=31884 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT00H15M00S END:VALARM END:VEVENT END:VCALENDAR

    Attachment(s)

    ics
    ical_31884.ics   4 KB 1 version


  • 2.  XLIFF TC Teleconference - Nov-1-2011 - Summary

    Posted 11-01-2011 16:14
    XLIFF TC Teleconference - Nov-1-2011 - Summary === 1/ Roll call Present: Arle, Shirley, Yves, Helena, Fredrik, Tom, Bryan, Steven, David-W, David-F, Rodolfo, Lucía, Regrets: Christian === 2/ Approve Tuesday, 04 October 2011 meeting minutes: http://lists.oasis-open.org/archives/xliff/201110/msg00009.html Bryan moves to approve. Tom, Rodolfo second. No objections. === 3/ Sub Committee Reports --- 1. Inline text (Yves) Worked on annotations/metadata. Summary: http://lists.oasis-open.org/archives/xliff-inline/201110/msg00013.html Rodolfo: DocBook template available on SVN And modules will be available soon. Yves: nice, big step forward to get the draft started Bryan: need to make sure DocBook are correctly validated before committing to SVN. Any recommendation welcome. Rodolfo: DocBook to HTML and PDF available. Fredrik: had good result with http://dblatex.sourceforge.net/ Rodolfo: note the style-sheets (we're not using the default) Fredrik: will try things out. --- 2. XLIFF Promotion and Liaison SC Charter (David) - Vote on David's proposal for features for 2.0 ( http://lists.oasis-open.org/archives/xliff/201111/msg00002.html ) David-F: Lucía is close to releasing the questions of state-of-the-art tools. Also, may need to answer this blog: http://www.translationtribulations.com/2011/10/notes-from-xliff-symposium-in-warsaw.html Bryan: I will do my part no later than end of week. - ballot about the process for approving features. Several steps: 1) choose between A: no restrictions, B: only owner can suggest reconsideration Then if B is selected: B1: need absolute majority B2: 3 month limit B3: no special conditions If no majority, then run-off between the two top selected options Then Yes/No vote for the whole procedure See David-F email for details ( http://lists.oasis-open.org/archives/xliff/201111/msg00002.html ) Ballot: A or B Option A passes. Ballot: Yes or No for the whole feature approval procedure. Yes passes. Rodolfo: Voted no because of "Owners must demonstrate to the TC not only the technical appropriateness of the feature but also explain what resources and timeframe is needed for elaboration and if those resources are available.": need to define those things (appropriateness, etc.) Bryan: example of reasons why a feature fail: lack of resource to define it. Rodolfo: don't think it'll be easy to do. But ok to move on. === 4/ XLIFF 2.0 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking ) Bryan: perhaps we need to add permanent tracking ids to titles, and not need to worry about preserving numbering scheme? Fixed IDs could be more helpful. Maybe we can appoint this task to wiki gardener (Bryan)? Fredrik: valid concern if it's auto-numbered. --- 1. XLIFF 2.0 Technical work a. Code and content comparison (good discussion at 18Oct2011, non-binding meeting - tracked in Inline SC) b. Representing starting/ending/stand-alone parts (good discussion at 18Oct2011, non-binding meeting - tracked in Inline SC) c. Segmentation feature (good discussion at 18Oct2011, non-binding meeting - tracked wiki) Bryan: about http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0 Should they be there? David-F: those are "procedural issues" Ok with our procedure because the procedure talks only about "features" Bryan: what is item goes to 2 to 4? David-F: fine, those were "mislabeled" except if someone disagrees. Bryan: owner can move item from 2 to 4. --- 2. XLIFF 2.0 Technical issues a. Added this category to FeatureTracking wiki page ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking ) - Does this work? Discussion on moving "Segmentation" to section 1 of feature. Yves: moving to #1 doesn't mean the description is final General agreement on that David-F: should we decide if it's core or not? Yves/Rodolfo: seem its' core because the elements are the containers David-W: segmentation not necessarily core: it's done afterward. Ballot to move Segmentation to #1 (not deciding if core or not) Passes. Action item: Yves to move item in the wiki === 5/ Current XLIFF business No time to discuss most of those items. but they are active item for current business === 6/ New Business None. -meeting adjourned


  • 3.  RE: [xliff] XLIFF TC Teleconference - Nov-1-2011 - Summary

    Posted 11-01-2011 16:36
    Hi, I looked at and tested the style-sheets. The style-sheets will not work with DbLaTex so that option is out. On the other hand the style-sheets to generate XML-FO seem to generate very clean FO XML that work well with Apache FOP. So using just XSLT + Apache FOP generated a PDF that looks very much like the pre-rendered PDF in SVN. Regards, Fredrik Estreen
    Original Message


  • 4.  Re: [xliff] XLIFF TC Teleconference - Nov-1-2011 - Summary

    Posted 11-01-2011 17:40
    Hi Yves, I posted the resulting procedure wording in the Chat window, but you probably missed it. I thought that it would be good to have the final wording as part of the minutes, maybe as an appendix. Thanks dF Here it is anyway: [start of procedure as  approved by TC on Nov 1, 2011] Feature approval  procedure Features not listed here: http://wiki.oasis-open.org/ xliff /XLIFF2.0/FeatureTracking will not be considered at all for inclusion in any  XLIFF  2.x spec. The feature tracking wiki comprises three sections. 1. Approved, 2. Under Consideration, 3. Discarded. Section 2. Features under consideration is the default section: http://wiki.oasis-open.org/ xliff /XLIFF2.0/FeatureTracking#Featuresunderconsideration.28notyetevaluatedbyTC.29 Any TC member can record a feature in Section 2., preferably following an e-mail or meeting discussion. Features can be moved into section 1. or 3. only following a formal TC  ballot . Features can be proposed for  ballot  in a regular TC meeting by the listed Owner (Champion) or the TC Chair. Owners must demonstrate to the TC not only the technical appropriateness of the feature but also explain what resources and timeframe is needed for elaboration and if those resources are available. TC Chair can suggest moving a feature from Section 1. to section 2. Or even 3. if it does not show reasonable progress close to  XLIFF  2.x spec release deadline. Any TC member can suggest reconsideration of an item in section 3, and no additional conditions apply.   Approval of core features Only features in the Section 1. Approved Features can be proposed for  XLIFF  2.x Core. This is recorded as “Core/Module: [Not determined/Core/Module]” Otherwise the  procedure  is the same as feature approval. A feature moving away from Section 1. gets its core status set to “Module” “Not determined” is being used as initial value only, all subsequent changes are between “Core” and “Module” only. [end of procedure] Dr. David Filip ======================= LRC CNGL LT-Web CSIS University of Limerick, Ireland telephone: +353-6120-2781 mobile:  +353-86-049-34-68 facsimile: +353-6120-2734 mailto: david.filip@ul.ie On Tue, Nov 1, 2011 at 16:11, Yves Savourel < ysavourel@enlaso.com > wrote: XLIFF TC Teleconference - Nov-1-2011 - Summary === 1/ Roll call Present: Arle, Shirley, Yves, Helena, Fredrik, Tom, Bryan, Steven, David-W, David-F, Rodolfo, Lucía, Regrets: Christian === 2/ Approve Tuesday, 04 October 2011 meeting minutes: http://lists.oasis-open.org/archives/xliff/201110/msg00009.html Bryan moves to approve. Tom, Rodolfo second. No objections. === 3/ Sub Committee Reports --- 1.  Inline text (Yves) Worked on annotations/metadata. Summary: http://lists.oasis-open.org/archives/xliff-inline/201110/msg00013.html Rodolfo: DocBook template available on SVN And modules will be available soon. Yves: nice, big step forward to get the draft started Bryan: need to make sure DocBook are correctly validated before committing to SVN. Any recommendation welcome. Rodolfo: DocBook to HTML and PDF available. Fredrik: had good result with http://dblatex.sourceforge.net/ Rodolfo: note the style-sheets (we're not using the default) Fredrik: will try things out. --- 2. XLIFF Promotion and Liaison SC Charter (David) - Vote on David's proposal for features for 2.0 ( http://lists.oasis-open.org/archives/xliff/201111/msg00002.html ) David-F: Lucía is close to releasing the questions of state-of-the-art tools. Also, may need to answer this blog: http://www.translationtribulations.com/2011/10/notes-from-xliff-symposium-in-warsaw.html Bryan: I will do my part no later than end of week. - ballot about the process for approving features. Several steps: 1) choose between A: no restrictions, B: only owner can suggest reconsideration Then if B is selected: B1: need absolute majority B2: 3 month limit B3: no special conditions If no majority, then run-off between the two top selected options Then Yes/No vote for the whole procedure See David-F email for details ( http://lists.oasis-open.org/archives/xliff/201111/msg00002.html ) Ballot: A or B Option A passes. Ballot: Yes or No for the whole feature approval procedure. Yes passes. Rodolfo: Voted no because of "Owners must demonstrate to the TC not only the technical appropriateness of the feature but also explain what resources and timeframe is needed for elaboration and if those resources are available.": need to define those things (appropriateness, etc.) Bryan: example of reasons why a feature fail: lack of resource to define it. Rodolfo: don't think it'll be easy to do. But ok to move on. === 4/ XLIFF 2.0 ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking ) Bryan: perhaps we need to add permanent tracking ids to titles, and not need to worry about preserving numbering scheme? Fixed IDs could be more helpful. Maybe we can appoint this task to wiki gardener (Bryan)? Fredrik: valid concern if it's auto-numbered. --- 1.  XLIFF 2.0 Technical work a. Code and content comparison (good discussion at 18Oct2011, non-binding meeting - tracked in Inline SC) b. Representing starting/ending/stand-alone parts (good discussion at 18Oct2011, non-binding meeting - tracked in Inline SC) c. Segmentation feature (good discussion at 18Oct2011, non-binding meeting - tracked wiki) Bryan: about http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking#TechnicalIssuesforXLIFF2.0 Should they be there? David-F: those are "procedural issues" Ok with our procedure because the procedure talks only about "features" Bryan: what is item goes to 2 to 4? David-F: fine, those were "mislabeled" except if someone disagrees. Bryan: owner can move item from 2 to 4. --- 2.  XLIFF 2.0 Technical issues a. Added this category to FeatureTracking wiki page ( http://wiki.oasis-open.org/xliff/XLIFF2.0/FeatureTracking ) - Does this work? Discussion on moving "Segmentation" to section 1 of feature. Yves: moving to #1 doesn't mean the description is final General agreement on that David-F: should we decide if it's core or not? Yves/Rodolfo: seem its' core because the elements are the containers David-W: segmentation not necessarily core: it's done afterward. Ballot to move Segmentation to #1 (not deciding if core or not) Passes. Action item: Yves to move item in the wiki === 5/ Current XLIFF business No time to discuss most of those items. but they are active item for current business === 6/ New Business None. -meeting adjourned --------------------------------------------------------------------- To unsubscribe, e-mail: xliff-unsubscribe@lists.oasis-open.org For additional commands, e-mail: xliff-help@lists.oasis-open.org


Related Content