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 20th 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:] 

Sent: Monday, November 10, 2008 6:02 AM

To: 

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  |