Event Title: Regular 3rd Tue teleconference
Date: Tuesday, 16 January 2018, 04:00pm to 05:00pm WET
Location: the usual Skype for Business dial in
Call details inside private AI:
This meeting counts towards voter eligibility.
Approve COS02 and request Special Majority Ballot to approve OASIS wide call for consent for XLIFF Version 2.1 COS02
4 Voters out of 6
dF, Phil, Tom, Yves
Regrets: Bryan, Lucía
Meeting minutes from 19th Dec 2017 approved via working list
Discussion of COS01 Issues
https://issues.oasis-open.org/browse/XLIFF-71 - no action
https://issues.oasis-open.org/browse/XLIFF-72 - feature request rejected [no action] / editorial clarification
https://issues.oasis-open.org/browse/XLIFF-73 - all occurences of typo fixed. Validation artifacts had all the correct namespace, but the prose typos were confusing
XLIFF TC having received comments during the 60 day public review period of XLIFF V2.1 COS01, those comments having resulted in non-material error corrections and editorial improvements in the current working draft labeled in advance as COS02 (http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-21/xliff-core-v2.1-cos02.html [revision 983]), and the corrections made being described in the error log on our SVN (http://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-21/%21Admin/COS01_CommentsDisposal/Simple-comment-resolution-log_XLIFF_2.1_cos01.pdf), I now move that the TC approve the above identified draft as XLIFF Version 2.1 Candidate OASIS Standard 02 and further request the TC Officers to request that TC Administration open a Special Majority Vote to approve submitting COS02 to the OASIS membership in a call for consent. By this motion, the TC confirms that all changes made were non-material and only made to address the reported issues.
dF: I need a second
Phil: I second
Roll call ballot: all present voters in favor
dF: Motion aproved unamimously
Request from XLIFF OMOS TC to clarify XLIFF TC prefix registration procedure
For both JLIFF and XLIFF, it would be an issue if module or extension prefixes contained colon(s). Currently we request that the prefix is an NMTOKEN not shorter than a number charatcters. But do not explicitly prohibit a colon. But colons in prefixes would cause confusion in both XLIFF and JLIFF implementations.
Therefore our sister committee requests that we clarify the registration procedure by explicitly prohibiting appearance of colon(s) ":" in registered prefixes.
dF: Let's make a call for dissent.. This needs formally brought up in XLIFF TC to make the change..
I move that our prefix registration procedure is clarified as proposed by XLIFF OMOS TC.
Yves: I second
dF: I hear no dissent, so this is approved.
AI Yves: Fix the prefix
dF: One last info. I checked with OASIS Admin and we should be able to submit also XLIFF 2.1 for ISO fast track publication, se we sould talk about this is February..
dF: Meeting adjourned
Owner: Dr. David Filip
Group: OASIS XML Localisation Interchange File Format (XLIFF) TC
Sharing: This event is not shared to any other groups.
This event is part of a series with 34 more events. The next 4 events in this series:
Tuesday, 20 February 2018, 04:00pm to 05:00pm WET
Tuesday, 20 March 2018, 04:00pm to 05:00pm WET
Tuesday, 17 April 2018, 04:00pm to 05:00pm WEST
Tuesday, 15 May 2018, 04:00pm to 05:00pm WEST
- Learn more about subscribing here.
- View the OASIS XML Localisation Interchange File Format (XLIFF) TC calendar here.
- You may receive future notifications with updates to this event. Update the event on your calendar by accepting the changes.