[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [ws-rx] v1.2CD01 ready for review
Thanks Mary for the clarification. I assume that this means that a reference to a target specification
should reflect the current status of the target specification, such as ‘Editors
Draft’ or ‘Working Draft’. This makes the recent changes to
the SX references in the RX specifications correct and consistent with this principle. > Committee Specification – Committee Specification
ballots are conducted electronically by the TC Administrator. Should a TC wish
to identify Designated Cross-references, the chair or secretary will so
indicate in their request to TC Admin, along with the other requisite
information (comment resolution log, meeting minutes, links to the documents).
The TC Admin would then verify that each specification identified as a
Designated Cross-reference is either pending in my queue (I have received
notification and am in the process of validating the request) or a ballot is
currently underway. The results of the ballot will not be announced until any
other ballots for specifications identified as a Designated Cross-reference
have completed. Once all ballots have completed, the TC will be notified as to
which cross-references can be updated. The date of approval will be the date the
last related ballot closed. Am I correct in interpreting that the RX specifications can now proceed
without delay up to Committee Specification ballot and then the RX
specifications would need to wait until the SX specifications are approved as a
Committee Specification? From: Mary McRae
[mailto:marypmcrae@gmail.com] On Behalf Of Mary McRae Hi Doug and Ram, Not quite as you stated … both specs must be
“in progress”. Here’s the rule and how I’ve notified
the board that I will implement it. Note that the board could come back and
tell me to do something different, but having been in all the meetings I
believe this meets the intent. This rule goes into effect 1 March 2008. Cross-references: “Designated Cross-reference Changes A TC wishing to update the Normative References or
Non-Normative References in one of its OASIS specifications to reflect the
outcome of a pending status change in another OASIS specification may do so, by
adopting a "Designated Cross-reference Change" as part of its
Specification Approval Motion, which must include: (a) a list designating
each of the other OASIS specifications (including version number) that are
referenced by that Specification and whose cross-references should
conditionally be updated; (b) a reference to this Section 2.18; and
(c) an acknowledgement that approval and publication of the specification
may be delayed by the Designated Cross-reference Changes. “The text of a proposed Designated Cross-reference
Change to a specification must include and may only include: the name,
version and revision number; expected approval status; date; and
URI for each other specification to be cross-referenced. The effectiveness of a
proposed Designated Cross-reference Change in a specification is conditioned on
the resolution of the expected approval action for each cross-referenced
specification. Therefore, if a Specification Approval Motion includes
proposed Designated Cross-reference Changes, the effectiveness of the subject
specification's approval will be delayed until the resolution of all other
cross-referenced specification approval actions. The TC Administrator
will withhold announcement and certification of the specification itself until
all such cross-referenced resolutions are complete. “If the Specification Approval Motion (which includes
Designated Cross-reference Changes) passes, then, when the last
cross-referenced approval is resolved, the final approved version will be
published with all of its conditional descriptions of the cross-referenced
specifications updated to reflect their correct status at that time.” My recommendation for implementation is as follows: Committee Draft – I have no direct involvement in
balloting/approval of Committee Draft status. Until we have a mechanism in
place that allows us to validate Committee Drafts (such as the OASIS Library)
there will be no checks/balances in place. If asked to upload the CD to the
OASIS Library I will perform the requisite checks. Public Review Draft – the current practice calls for
the chair or secretary to send a request to TC Admin to start a public review.
That request must include links to the documents to be published, links to
meeting minutes containing the approval motion, and a list of public mailing
lists that should be notified of the review. If such motion contains designated
cross-references, they will be QC’d along with the other aspects of the
document that are checked before announcing the review to membership. Committee Specification – Committee Specification
ballots are conducted electronically by the TC Administrator. Should a TC wish
to identify Designated Cross-references, the chair or secretary will so
indicate in their request to TC Admin, along with the other requisite
information (comment resolution log, meeting minutes, links to the documents).
The TC Admin would then verify that each specification identified as a
Designated Cross-reference is either pending in my queue (I have received
notification and am in the process of validating the request) or a ballot is
currently underway. The results of the ballot will not be announced until any
other ballots for specifications identified as a Designated Cross-reference
have completed. Once all ballots have completed, the TC will be notified as to
which cross-references can be updated. The date of approval will be the date the
last related ballot closed. OASIS Standard – there are two pieces to an OASIS
Standard vote. The first is a motion by the TC for the TC Admin to start a
ballot to approve the submission of the specification to the OASIS membership.
It is that motion that will need to identify any Designated Cross-references,
along with the existing requirements. Similar to a CS ballot, the OASIS
Standard ballot results will not be announced until any other ballots for
specifications identified as a Designated Cross-reference have completed. At
that time the TC will be notified as to which cross-references can be updated.
The date of approval will be the date the last related ballot closed. Regards, Mary From: Doug Davis
[mailto:dug@us.ibm.com]
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]