< Return to Calendar

* XLIFF TC Meeting (Conference Call)
Name * XLIFF TC Meeting (Conference Call)
Time Tuesday, 16 August 2016, 11:00am to 12:00pm EDT
(Tuesday, 16 August 2016, 03:00pm to 04:00pm UTC)
Description

Please get the dial in information from our private Action Item here:
https://www.oasis-open.org/apps/org/workgroup/xliff/members/action_item.php?action_item_id=3663

Minutes

I Administration (0:00 - 0:10)

  A. Roll call

dF: We have quorum on this meeting.

 

B. Approve meeting minutes, 

19 July 2016

     https://lists.oasis-open.org/archives/xliff/201607/msg00024.html 

2 August 2016

     https://lists.oasis-open.org/archives/xliff/201608/msg00047.html

dF: I propose that the TC would approve the meeting minutes for both meetings on 19th July and 2nd August, does anyone second?

Tom: I second.

 

C. Revise scheduled for XLIFF 2.1  

     https://lists.oasis-open.org/archives/xliff/201504/msg00009.html 

     https://lists.oasis-open.org/archives/xliff/201504/msg00014.html 

 

  D. ISO submission of XLIFF 2.0

     It has been confirmed that the submission has been accepted, so the process has started as expected.

     Liaison report to ISO TC 37 (Peter)

     https://lists.oasis-open.org/archives/xliff/201604/msg00013.html

dF: Pending for the french translation

 

  E. Action Item progress (as tracked in kavi AI tracker)

     https://www.oasis-open.org/apps/org/workgroup/xliff/members/action_items.php

dF: On Tom’s action item to  make sure if the schemas are in sync with the spec; We have the schema for ITSM, would be good if Soroush, Felix or Yves could review the XSD for ITSM.

Tom: I also need to update all the namespace info to use 2.1 instead of 2.0.

dF: It would apply only to ITSM and CTR, as others will stay in the 2.0 namespace.

dF: For ITS storage restriction, we have an issue as Fredrik is not responding. 

 

  F. Check prefix registration.

dF: I have taken for now the responsibility for registration of prefixes, I guess the officers can share it, no TC approval needed, an email of request would be sufficient.

 

  G. Call For Dissent: Inline Markup within Change Tracking (Phil)

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

Phil: It is very narrow improvement for our use case, which is on preventing the loss of inline markup after track changing in OCELOT. So we aimed to fix this bug, which created more questions on the scope of the CTR module. 

dF: It might be good to allow Track changes up to <unit>, to capture segmentation revision. So if the segmentation not changed, only the occurred modifications will be recorded. But, as you can not reference target (source) elements, the revision must be recorded at least from <segment> (which allows @id). Phil has provided a modified XSD, Tom, have you had a look?

Tom: Not yet. I'll have to look more closely at it. If what's in Phil's version of the XSD is complete, it's just copying to the production XSD.

dF: At least <segment> must be allowed in CTR, we could discuss allowing of <unit>.

 

  H. Call For Dissent for canCopy attribute text (Soroush)

     https://lists.oasis-open.org/archives/xliff/201608/msg00009.html 

dF: If no objections, it is approved.

     

II XLIFF 2.1 (0:10 - 0:45)

* indicates new topic, not yet discussed 

  A. CanReorder Validation error (Ryan)

     https://lists.oasis-open.org/archives/xliff/201509/msg00031.html 

  B. XLIFF and ITS mapping-ID value (Soroush)

     https://lists.oasis-open.org/archives/xliff/201512/msg00034.html 

  C. Issue with validating extensions (David)

     https://lists.oasis-open.org/archives/xliff/201603/msg00019.html 

     --> new AI for people to register extensions.

     --> issue report to Okapi-XLIFF (https://bitbucket.org/okapiframework/xliff-toolkit/issues/9)

  D. * XLIFF 2.1 - ITS support; editing calls (Felix)

     https://lists.oasis-open.org/archives/xliff/201604/msg00014.html 

  E. itsm namespace in extension registration (Yves)

     https://lists.oasis-open.org/archives/xliff/201604/msg00023.html 

  F. Proposal on how to move forward with ITS 2.0 support in XLIFF 2.1 (Felix)

     https://lists.oasis-open.org/archives/xliff/201605/msg00002.html 

  G. * Changes for the registration of value prefixes (Yves)

     https://lists.oasis-open.org/archives/xliff/201605/msg00005.html 

  H. * Implementation of XLIFF 2.1 - ITS module (Felix)

     https://lists.oasis-open.org/archives/xliff/201608/msg00037.html 

Felix: I rather discuss this issue on the email to draw everyone’s attention, especially Yve’s. 

 

  I. * preparing csd01/csprd01 - Question where to allow ITSM elements and attributes 

     https://lists.oasis-open.org/archives/xliff/201608/msg00008.html 

III Sub Committee Report (0:45 - 0:55)

IV  Current and New Business (0:55 -0:00)

dF: We will have a short FEISGILTT event within the LocWorld conference in Montreal, please send your proposals if planning to by the end of August. 

dF: The meeting is now adjourned. 



Agenda

I Administration (0:00 - 0:10)
  A. Roll call
  B. Approve meeting minutes, 2 August 2016
     https://lists.oasis-open.org/archives/xliff/201608/msg00047.html
  C. Revise scheduled for XLIFF 2.1  
     https://lists.oasis-open.org/archives/xliff/201504/msg00009.html
     https://lists.oasis-open.org/archives/xliff/201504/msg00014.html
  D. ISO submission of XLIFF 2.0
     It has been confirmed that the submission has been accepted, so the process has started as expected.
     Liaison report to ISO TC 37 (Peter)
     https://lists.oasis-open.org/archives/xliff/201604/msg00013.html
  E. Action Item progress (as tracked in kavi AI tracker)
     https://www.oasis-open.org/apps/org/workgroup/xliff/members/action_items.php
  F. Check prefix registration.
  G. Call For Dissent: Inline Markup within Change Tracking (Phil)
     https://lists.oasis-open.org/archives/xliff/201608/msg00041.html
  H. Call For Dissent for canCopy attribute text (Soroush)
     https://lists.oasis-open.org/archives/xliff/201608/msg00009.html

     
II XLIFF 2.1 (0:10 - 0:45)
* indicates new topic, not yet discussed
  A. CanReorder Validation error (Ryan)
     https://lists.oasis-open.org/archives/xliff/201509/msg00031.html
  B. XLIFF and ITS mapping-ID value (Soroush)
     https://lists.oasis-open.org/archives/xliff/201512/msg00034.html
  
  C. Issue with validating extensions (David)
     https://lists.oasis-open.org/archives/xliff/201603/msg00019.html
     --> new AI for people to register extensions.
     --> issue report to Okapi-XLIFF (https://bitbucket.org/okapiframework/xliff-toolkit/issues/9)
  D. * XLIFF 2.1 - ITS support; editing calls (Felix)
     https://lists.oasis-open.org/archives/xliff/201604/msg00014.html
  E. itsm namespace in extension registration (Yves)
     https://lists.oasis-open.org/archives/xliff/201604/msg00023.html
 
  F. Proposal on how to move forward with ITS 2.0 support in XLIFF 2.1 (Felix)
     https://lists.oasis-open.org/archives/xliff/201605/msg00002.html
     
  G. * Changes for the registration of value prefixes (Yves)
     https://lists.oasis-open.org/archives/xliff/201605/msg00005.html

  H. * Implementation of XLIFF 2.1 - ITS module (Felix)
     https://lists.oasis-open.org/archives/xliff/201608/msg00037.html

  I. * preparing csd01/csprd01 - Question where to allow ITSM elements and attributes 
     https://lists.oasis-open.org/archives/xliff/201608/msg00008.html

III Sub Committee Report (0:45 - 0:55)
IV  Current and New Business (0:55 -



Submitter Bryan Schnabel
GroupOASIS XML Localisation Interchange File Format (XLIFF) TC
Access This event is visible to OASIS XML Localisation Interchange File Format (XLIFF) TC and shared with
  • OASIS Open (General Membership)
  • General Public