OASIS Member Certifications of XRI Syntax usage

XRI TC Members and Observers,

15 of 22 voting members have voted in favor of advancing XRI Syntax 2.0 CD02 to Committee Specification status (and I just sent a reminder email to the rest). Since Nov. 15th is the deadline for making a submission for a December vote, and it follows immediately after the ballot closes next Monday, we are working with our TC administrator Mary McRae to prepare the submission in advance.

Copied below are the OASIS TC Process rules governing submissions of specifications for an OASIS Standard vote. All of these Gabe and I can write up and publish to the list for feedback EXCEPT item (f): "Certification by at least three OASIS member organizations that they are successfully using the specification".

I have sent a message to Mary asking for clarification about the format that this certification statement needs to take (I believe an email will be sufficient), but this is a heads up that we'd like TC members who would like to provide such a certification to be ready to do so tomorrow or Thursday once we hear back from Mary, so we can include this in our submission.

Thanks,

=Drummond

Excerpt of section 3.4 of TC Process (http://www.oasis-open.org/committees/process.php#3.4):

Simultaneously with the approval of a Committee Specification or at a later date, a TC may resolve by Special Majority Vote to submit the Committee Specification to the membership of OASIS for consideration as an OASIS Standard. Upon resolution of the TC to submit the specification, its Chair shall submit the following items to the TC Administrator:

a. Links to the approved Committee Specification in the TC's document repository, and any appropriate supplemental documentation for the specification, both of which must be written using the OASIS templates. The specification may not have been changed between its approval as a Committee Specification and its submission to OASIS for consideration as an OASIS Standard, except for the changes on the title page and running footer noting the approval status and date.

b. The editable version of all files that are part of the Committee Specification;

c. Certification by the TC that all schema and XML instances included in the specification, whether by inclusion or reference, including fragments of such, are well formed, and that all expressions are valid;

d. A clear English-language summary of the specification;

e. A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations;

f. Certification by at least three OASIS member organizations that they are successfully using the specification;

g. The beginning and ending dates of the public review(s), a pointer to the announcement of the public review(s), and a pointer to an account of each of the comments/issues raised during the public review period(s), along with its resolution;

h. An account of and results of the voting to approve the specification as a Committee Specification, including the date of the ballot and a pointer to the ballot;

i. An account of or pointer to votes and comments received in any earlier attempts to standardize substantially the same specification, together with the originating TC's response to each comment;

j. A pointer to the publicly visible comments archive for the originating TC;

k. A pointer to any minority reports submitted by one or more Members who did not vote in favor of approving the Committee Specification, which report may include statements regarding why the member voted against the specification or that the member believes that Substantive Changes were made which have not gone through public review; or certification by the Chair that no minority reports exist.

xri message