RE: [ws-tx-editors] Draft CS specs

Hi everyone,

Actually, if the specs to be voted on are going to be different than those submitted for public review, the revised specs will first need to be approved as CDs and should therefore be identified as Committee Draft 02 *once that ballot has actually passed.* Remember, *all* works of a technical committee are always publicly available; identifying something with a status that the document has not yet achieved is not only against the rules, it’s misleading.

Thanks,

Mary

From: Ian Robinson [mailto:ian_robinson@uk.ibm.com]
Sent: Friday, July 25, 2008 8:22 AM
To: ws-tx-editors@lists.oasis-open.org
Subject: [ws-tx-editors] Draft CS specs

Editors,
Please could you prepare draft C, AT and BA specs.
These should update the status to "Committee Specification" and be dated when the CS approval ballot completes. That isn't scheduled yet so a suggested date (that will have to be changed later) is Aug 28 2008. We only need Word Doc format at present.
The only changes needed are the formats of the references to the SX and other TX specs.
Any TX refs should appear like this:

[WSCOOR] OASIS Public Committee Specification, Web Services Coordination (WS-Coordination) 1.2, http://docs.oasis-open.org/ws-tx/wscoor/2006/06, May 2008

Currently, any SX references should look like this:

[WSTrust] OASIS Committee Draft 01, WS-Trust 1.4, http://docs.oasis-open.org/ws-sx/ws-trust/200802, June 2008

[WSSecPolicy] OASIS Committee Draft 01, WS-SecurityPolicy 1.3, http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200802

[WSSecConv] OASIS Committee Draft 01, WS-SecureConversation 1.4, http://docs.oasis-open.org/ws-sx/ws-secureconversation/200512

Regards,
Ian Robinson

----- Forwarded by Ian Robinson/UK/IBM on 25/07/2008 13:00 -----

Ian Robinson/UK/IBM

24/07/2008 17:08

To	wstx
cc
Subject	WS-TX 1.2 designated cross references

As discussed on the TX call, the result of my action item to follow up with the TC Admin on the use of the designated cross-reference change process is this:

We should modify our references to work-in-progress to identify the level of the specification we are referring to. For example, where we currently say:

[WSTrust] WS-Trust 1.4, http://docs.oasis-open.org/ws-sx/ws-trust/200802

[WSCOOR] Web Services Coordination (WS-Coordination) 1.2, http://docs.oasis-open.org/ws-tx/wscoor/2006/06, OASIS, January 2008

we should instead say:

[WSTrust] OASIS Committee Draft 01, WS-Trust 1.4, http://docs.oasis-open.org/ws-sx/ws-trust/200802, June 2008

[WSCOOR] OASIS Public Review Draft, Web Services Coordination (WS-Coordination) 1.2, http://docs.oasis-open.org/ws-tx/wscoor/2006/06, May 2008

At Committee spec stage, our internal cross-references will be to other committee specifications but we might still refer to WS-Trust 1.4 Public Review Draft. We would have a ballot to approve CS drafts without any designated cross-reference changes and to advance to OASIS Standard with designated cross-reference changes.
If the OS member ballot passed but the referenced spec (e.g. WS-Trust) lagged by 4 months then during that 4 month period the published latest version of WS-TX would be the CS but would automatically be replaced by an OS containing the changed cross references once the referenced specs were finalized.

Regards,
Ian Robinson

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

ws-tx-editors message