Subject: Modified: XLIFF TC Meeting
Event Title: XLIFF TC Meeting
Date: Tuesday, 15 December 2015, 11:00am to 12:00pm EST
Please get the dial in information from our private Action Item here:
This meeting counts towards voter eligibility.
I Administration (0:00 - 0:10)
B. Approve meeting minutes, 17 November 2015
D. Requesting progress of ISO submision of XLIFF 2.0
E. Mandate extension of the XLIFF P&L Subcommittee - Lucía, second from Fredrik
F. * Okapi XLIFF Toolkit 1.1 Available (Yves)
G. * XLIFF Support - Survey (Lucía)
II XLIFF 2.1 (0:10 - 0:45)
* indicates new topic, not yet discussed
A. Discuss whether can be allowed at all extension points (Ryan)
M. * ITS text analytics (David)
N. Internationalization and beyond related metadata for JSON - XLIFF perspective? (Felix)
III Sub Committee Report (0:45 - 0:55)
IV Current and New Business (0:55 -
B: Meeting minutes approved.
-- Requesting progress of ISO submission of XLIFF 2.0
David Filip, these are Alan Melby questions: As for XLIFF at the TC 37 conference in Copenhagen at the end of June, I have not heard a recent status. Has an official ISO TC 37 NWIP (New Work Item Proposal) ballot been issued? If so, did it end up in SC 4 or SC 5?
DF: Fast track still needs an approval.
F: yes, it still needs approval, fast track just accelerates things.
DF: I will address those questions to Peter.
Df: I might try to go Copenhagen.
F: It might be doable for me as I can go on a day and be back on the same day.
DF: The meeting will take place in June/July. I am in contact with ISO and I am seeing if I should join the Irish or the Czech delegation.
-- Okapi XLIFF Toolkit 1.1 Available (Yves)
B: That is good news.
-- Lucia. XLIFF Support - Survey (Lucía)
L: No answers yet. The survey is open for tool developers within the TC.
Df: we'd like to address the TC members first.
F: It is too late to change the deafult for source and target in the schema.
DF: I agree, but we need to describe the best practice in the pec. It needs some normative language to obtain predictable results.
F: you can just apply general XML preservation rules
DF: the use case is mixed behavior.
F: we should have a note explicitating it.
Df: We actually have a problem if we have mixed behavior within a segment. We need exact procedure to indicate what to do if we have mixed space handling within segment or unit. You need to normalise what needs to be normalised, but not normalise where white spaces need preserved. The issue is that other vocabularies do have mixed behavior, but we cannot have it becuse of pesudospans in inline content.
F: that information can be added with ITS.
Df: probably the best to address would be a note or a warning in core and just quote it in the ITS description, becuase the issue is not ITS specific, ITS just used xml:space.
Df: We need to have somebody to write the text that is spec ready. Yves had the AI.
B: I will refer to these minutes.
-- Implementing XLFF 2.0 test suite files (Ryan)
B: Ryan has made some discoveries on the files that Yves and I created. I will take care of the change tracking ones. I can ask Yves to have a look at the core ones.
F: We should have one error only for file, it is a good a practise to do that.
B: I agree, that is a good practise.
Df: for the advance validation, we might need more than the artefacts. For example, using the test files. If people want to help Souroush with the prose spec for advanced validation...
S: I can take care of some of the issues of the validaditon, but I need to do a list. I will send that list to the TC asking for comments.
III Sub Committee Report (0:45 - 0:55)
Df: The sister committee has started last week. We will need close liaison between committees. The next meeting will take place in January. I was elected chair of the committee. Microsoft joined, also SDL and Yves. The liaison to the XLIFF TC was also formed, Yves was the link. Alan Melby volunteered for the liaison with TBX but he wanted to transfer the TBX mapping to the sister committee.
I would like to ask the TC next month, if the TC would hand over the work on the TBX mapping to the OSMOS TC? The OMOS TC has mappings explicitly in scope.
B: I would support it.
F: I do not have any objections for that.
Df: I kindly ask all the tool implementers on the TC if they please could fill out the survey by Christmas.
B: We hear that
B: TC adjourned
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
Microsoft Outlook users: You will see event notifications requiring further
action in your Outlook mail application.
BEGIN:VCALENDAR CALSCALE:GREGORIAN METHOD:REQUEST 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 STATUS:CONFIRMED TRANSP:OPAQUE DTSTAMP:20151217T190950Z DTSTART;VALUE=DATE-TIME;TZID=America/New_York:20151215T110000 DTEND;VALUE=DATE-TIME;TZID=America/New_York:20151215T120000 SEQUENCE:2 SUMMARY:XLIFF TC Meeting LAST-MODIFIED:20151217T190950Z ORGANIZER:firstname.lastname@example.org DESCRIPTION:Please get the dial in information from our private Action I tem here:\nhttps://www.oasis-open.org/apps/org/workgroup/xli ff/members/action_item.php?action_item_id=3663\n\nAgenda: I Administration (0:00 - 0:10)\n A. Roll call\n\n B. Approve meeting minutes\, 17 November 2015\n https://lists.oasi s-open.org/archives/xliff/201511/msg00028.html\n \n C. Revise scheduled for XLIFF 2.1 \n https://lists.oasis -open.org/archives/xliff/201504/msg00009.html\n https:// lists.oasis-open.org/archives/xliff/201504/msg00014.html\n\n D. Requesting progress of ISO submision of XLIFF 2.0\n https://lists.oasis-open.org/archives/xliff/201506/msg00002 .html\n https://lists.oasis-open.org/archives/xliff/2015 11/msg00002.html\n\n E. Mandate extension of the XLIFF P&L Subcommittee - Lucí\;a\, second from Fredrik\n htt ps://lists.oasis-open.org/archives/xliff/201511/msg00011.htm l\n\n F. * Okapi XLIFF Toolkit 1.1 Available (Yves)\n h ttps://lists.oasis-open.org/archives/xliff/201512/msg00009.h tml\n\n G. * XLIFF Support - Survey (Lucí\;a)\n h ttps://lists.oasis-open.org/archives/xliff/201512/msg00023.h tml\n\nII XLIFF 2.1 (0:10 - 0:45)\n\n* indicates new topic\, not yet discussed\n\n A. Discuss whether can be allowed at all extension points (Ryan)\n https://lists.oasis-open. org/archives/xliff/201506/msg00013.html\n B. Inline attribu tes and canCopy (Ryan)\n https://lists.oasis-open.org/ar chives/xliff/201506/msg00015.html\n D. Typo in example (4.3 .1.10 dataRefEnd) (Yves)\n https://lists.oasis-open.org/ archives/xliff/201506/msg00022.html\n E. Add N Constraint t o the core order attribute\n DF will make a CFD for this on mailing list. This has been now sufficiently discussed. [pending AI for dF]\n F. Template/Model for TBX Mapping wit h XLIFF v2.0 and Higher Version 1.0 (DavidF)\n https://l ists.oasis-open.org/archives/xliff/201411/msg00091.html [pen ding AI for Fredrik]\n G. ITS storage size restriction\n Fredrik to propose slr profile for ITS storage size data c ategory [pending AI for dF]\n H. Mistakes in the spec (Soro ush)\n https://lists.oasis-open.org/archives/xliff/20150 2/msg00009.html\n I. NVDL for the core is updated (Soroush) \n https://lists.oasis-open.org/archives/xliff/201503/ms g00009.html\n J. NVDL validation for XLIFF 2.0 (Soroush)\n https://lists.oasis-open.org/archives/xliff/201509/msg00 002.html\n K. * Comment on 2.1 draft (Yves)\n https://l ists.oasis-open.org/archives/xliff/201509/msg00023.html\n L . * CanReorder Validation error (Ryan)\n https://lists.o asis-open.org/archives/xliff/201509/msg00031.html\n\n M. * ITS text analytics (David)\n\n N. Internationalization and beyond related metadata for JSON - XLIFF perspective? (Felix )\n https://lists.oasis-open.org/archives/xliff/201510/m sg00006.html\n O. * XLIFF Support Survey Draft (Lucí\ ;a)\n https://lists.oasis-open.org/archives/xliff/201511 /msg00005.html\n P. * Question on namespace re-writing and ITS text analysis (Felix)\n https://lists.oasis-open.org /archives/xliff/201511/msg00013.html\n Q. * Proposal For Ch ange Tracking in XLIFF 2.1 (Phil)\n https://lists.oasis- open.org/archives/xliff/201511/msg00024.html\n R. Errors in test suite for Change Tracking module (Yves)\n [action item: Bryan to fix]\n https://lists.oasis-open.org/archi ves/xliff/201511/msg00026.html\n S. CTR test suite files\n https://lists.oasis-open.org/archives/xliff/201511/msg00 027.html\n [action item: Bryan to fix]\n T. * Preservin g spaces inline (Yves)\n https://lists.oasis-open.org/ar chives/xliff/201512/msg00008.html\n U. * Inline codes in Ch ange Tracking (Yves)\n https://lists.oasis-open.org/arch ives/xliff/201512/msg00010.html\n V. * Implementing XLFF 2. 0 test suite files (Ryan)\n https://lists.oasis-open.org /archives/xliff/201512/msg00019.html\n\nIII Sub Committee Re port (0:45 - 0:55)\n\nIV Current and New Business (0:55 -\n Group: OASIS XML Localisation Interchange File Format (XLIFF ) TC\nCreator: Bryan Schnabel URL:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=41566 UID:https://www.oasis-open.org/apps/org/workgroup/xliff/event.php?event_id=41566 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT00H15M00S END:VALARM END:VEVENT END:VCALENDAR