Statements of Use

["Patil, Sanjay" <sanjay.patil@sap.com>]

 

It seems that the TC process requires three Statements of Use to be presented to the TC before the TC resolves  to submit the specifications for an OS vote. In anticipation of the TC making a resolution on the next conf-call (11/20) to go for an OS vote, I would like to ask the TC members to review their internal status of using our specifications and consider issuing Statement of Use via an email before the conf-call.

 

Here is cut-paste of the definition of the term 'Statement of Use' from the TC process document:

"Statement of Use", with respect to a specification, is a written statement by an OASIS Organizational Member stating that it is successfully using or implementing that specification in accordance with the conformance clauses specified in Section 2.18, and stating whether its use included the interoperation of multiple independent implementations.

 

Thanks,

Sanjay

---

From: Ram Jeyaraman [mailto:Ram.Jeyaraman@microsoft.com]
Sent: Tuesday, Nov 11, 2008 14:18 PM
To: Doug Davis
Cc: ws-rx@lists.oasis-open.org
Subject: RE: [ws-rx] [NEW ISSUE] MC Action URI is poorly defined

I am fine with this change. I suggest we resolve this and proceed to a member vote during the next TC call on Nov 20^th as described in Section 3.4 of the OASIS technical committee process [1]:

 

“Simultaneously with the approval of a Committee Specification or at a later date, and after three Statements of Use have been presented to the TC, a TC may resolve by Special Majority Vote to submit the Committee Specification to the Membership of OASIS for consideration as an OASIS Standard.”

 

[1] http://www.oasis-open.org/committees/process.php#OASISstandard

 

From: Doug Davis [mailto:dug@us.ibm.com]
Sent: Monday, November 10, 2008 6:02 AM
To: ws-rx@lists.oasis-open.org
Subject: [ws-rx] [NEW ISSUE] MC Action URI is poorly defined

 

When MC was pulled out of the RM spec it was pretty much a cut-n-paste action. As a result, since the RM ActionURIs are defined by a set of rules rather than defining each ActionURI along with each message (see section 3.3 of the RM spec), the MC ActionURI was never explicitly defined.  The wsdl and examples in the MC spec clearly show what the ActionURI is meant to be, but since we're opening up the MC spec to fix other typos I'd like to suggest that we add the following to the MC spec just to be explicit about it:

In section 3.2, right before the exemplar that defines the MC body, add:

When the MC protocol, defined in this specification, is composed with the WS-Addressing specification, the value of the wsa:Action header would be:
        http://docs.oasis-open.org/ws-rx/wsmc/200702/MakeConnection

While this isn't quite a typo, its pretty obvious and will help new readers.  Perhaps we could even discuss it thru email and if there's no objection I can have a draft ready to go for the next meeting - along with the other 2 issues we've resolved.

thanks
-Doug
______________________________________________________
STSM  |  Web Services Architect  |  IBM Software Group
(919) 254-6905  |  IBM T/L 444-6905  |  dug@us.ibm.com