[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [xliff] Re: Motion to progress towards XLIFF 2.1 csd01/csprd01 in today's meeting
Hello again, all,
since it transpired in the last meeting on 4th October 2016 that the validation artifacts were not ready for the csd01/csprd01 vote, the editorial team has been working hard on the validation artifacts fixes and improvements.
Chances are that we will have during today or very early tomorrow European time a votable set of validation artifacts.
I also used the extra time for a QA check of the prose draft and fixed a number of issues some of them major, such as wrong declaration of the ctr namespace in the front matter and adding a missing conformance statement in CTRM. Some of them minor, like spellcheck of the media type registration template, adjustment of the CTRM tree etc.
Since we have a new working draft printout and a number of important fixes and additions made both in the prose spec and the validation artifacts, I need to repeat the motion to approve the current working draft as csd01/csprd01
*I need a second*
Please note that this is a Full majority Vote that will go out to our current 8 Voters, from which at least 5 need to cast their ballot in favor for the ballot to succeed and allow me to work with OASIS Admin to publish the csd01/csprd01 versions on official OASIS URIs like this:
The ballot text that we pre-aproved by consensus in the last meeting
needs to change as follows:
Title: Approve XLIFF Version 2.1 Working Draft 01 as CSD/CSPRD
A) XLIFF Version 2.1 Working Draft 01 from 05 October 2016 https://tools.oasis-open.
org/version-control/browse/*. wsvn/xliff/trunk/xliff-21/ xliff-core-v2.1-wd01.html pdf, and *.xml and all associated artifacts athttps://tools.oasis-open. org/version-control/svn/xliff/[ trunk/xliff-21/schemas/ Revision 7[2|3]#] as a Committee Specification Draft, designating the html version of the specification as authoritative and
B) releasing the Committee Specification Draft for a 30 days public review and
2) direct the TC officers to work with OASIS TC Administration on all tasks required to carry out publishing of the above approved drafts.
Once the ballot is set up, all Voters will keep getting notifications from time of the opening of the ballot until they have voted. All will get the final notification when the ballot closes.
Cheers and thanks
On Tue, Oct 4, 2016 at 1:11 PM, David Filip <email@example.com> wrote:
you are aware the editorial team (Yves, Felix, Soroush, Tom, and myself) have been working since July to progress our working draft towards the first public review.
The editors feel that it's time to make the move and start tracking changes to the spec in a more official manner towards the higher levels of OASIS approval.
This is the proposed motion language that I'd like to vote on in the upcoming meeting.
I move that the TC approve XLIFF Version 2.1 Working Draft 01 from 03 October 2016 https://tools.oasis-open.org/
version-control/browse/wsvn/*.pdf*, and *.xml* xliff/trunk/xliff-21/xliff- core-v2.1-wd01.html?rev=706& sc=1
and all associated artifacts at https://tools.oasis-open.org/
version-control/svn/xliff/[Revision 70#] as a Committee Specification Draft, designating the html version of the specification as authoritative, and that the TC further approve releasing the Committee Specification Draft for a 30 days public review and direct the TC officers to work with OASIS TC Administration on all tasks required to carry out these directions. trunk/xliff-21/schemas/
Thanks for your attention and talk soon