XLIFF TC Call

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

I Administration (0:00 - 0:10)
  A. Roll call
       
  B. Approve meeting minutes, 1 November 2016
     https://lists.oasis-open.org/archives/xliff/201611/msg00016.html

----------------------------------------------------------------------
Review Public Review comments in JIRA

https://issues.oasis-open.org/browse/XLIFF/

Public Review ends 25 November
----------------------------------------------------------------------

  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
     Pending French translation.
     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.
     ITS ID prefix registry (Yves)
     https://lists.oasis-open.org/archives/xliff/201609/msg00010.html
  G. Call For Dissent: Inline Markup within Change Tracking (Phil)
     https://lists.oasis-open.org/archives/xliff/201608/msg00041.html
  - latest https://lists.oasis-open.org/archives/xliff/201608/msg00056.html     
  H. Call For Dissent for canCopy attribute text (Soroush)
     https://lists.oasis-open.org/archives/xliff/201608/msg00009.html
     Approved.
  I. Comments on XLIFF 2.1 Draft (Yves)
     https://lists.oasis-open.org/archives/xliff/201608/msg00067.html
     XLF draft feedback
     https://lists.oasis-open.org/archives/xliff/201609/msg00008.html
  J. Call for papers for the Montreal Symposium
     https://lists.oasis-open.org/archives/xliff/201608/msg00069.html
  K. * Generating HTML/PDF for each edit (Yves)
     https://lists.oasis-open.org/archives/xliff/201609/msg00044.html
     
II XLIFF 2.1 (0:10 - 0:45)

Latest printout

https://www.oasis-open.org/apps/org/workgroup/xliff/email/archives/201609/msg00019.html

* 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 will issue a new email.
  I. * preparing csd01/csprd01 - Question where to allow ITSM elements and attributes
     https://lists.oasis-open.org/archives/xliff/201608/msg00008.html
  J. * Change Tracking 2.1 (Yves)
     https://lists.oasis-open.org/archives/xliff/201609/msg00027.html
  K. * ITS rules file (Felix)
     https://lists.oasis-open.org/archives/xliff/201609/msg00029.html
  L * Localization Note vs   (Yves)
    https://lists.oasis-open.org/archives/xliff/201609/msg00045.html
    
III Sub Committee Report (0:45 - 0:55)

IV  Current and New Business (0:55 -

Summary of the XLIFF TC Call Nov-15-2016
========================================

- Present: David, Bryan, Yves, Soroush, Tom, Lucia
- Regrets: Phil, (Felix probably in Dublin too)


  B. Approve meeting minutes, 1 November 2016
     https://lists.oasis-open.org/archives/xliff/201611/msg00016.html

BS: move to accept those as the minutes for last call
YS: second
No dissent.

BS: One of the XLF2.1 issues difficult to resolve is #9 (ITS vs ITSM namespace)
BS has issue with audio.


--- Issue #9: https://issues.oasis-open.org/browse/XLIFF-9

YS: it seems that if we don't use ITS namespace we can't have them as ITS data categories
.. We can't access them with ITS processors

DF: there are other obstacles with ITS processors, like sm/em too.

YS: I think sm is pretty much the only obstacle if you have ITS pointers

DF: Felix mentioned the fact we could use the ITS schemas
.. for example docbook 5.1, not sure about DITA
SS: That is correct (DocBook+ITS)
DF: so if we can change the catalog and point to our schema
.. then we could do the ITS validation

TC: I'm not aware of any different schema for ITS in DITA

DF: we should confirm with Felix
.. We should move to something else.


DF: Issue 8 is depending on issue 9.

SS: DocBook doesn't use the ITS native namespace.
DF: also for data categories without pointers?
SS: Not sure, will have to check


--- Issue-4: CTR: https://issues.oasis-open.org/browse/XLIFF-4

DF:

we could track all changes on the unitItem (in case sm/em would need orphaned), and changes captured by a unitItem, should probably not be tracked separately and only unit attributes would be allowed to have separate items not attributes inside unit to avoid conflicts..Will try and do the tracking PRs so that the ctr autocomplete is not needed... maybe we can have content and some other coordinated attributes
.. Will work on a possible solution: change data model in prose and xsd as well as PRs.
.. and Soroush will update the Schematron


--- Issue-5: https://issues.oasis-open.org/browse/XLIFF-5

Depending on #9 too.

DF: we should be able to change the list of what is making up the XLIFF-defined elements/attributes
YS: It seems that would be a core change: some core PR depend on the definition of what is a XLIFF-defined construct
.. so if we change that definition, we change the core, no?
DF: I think we should be able to change the definitions, it's not part of the core.


--- Issue-10: https://issues.oasis-open.org/browse/XLIFF-10

Good catch.
Error in the Schematron it seems.
Soroush to change the schema.
No dissent.


BS: will have a hard stop at 9AM PT

-end