Proposed resolution to issue 127

[Ian Robinson <ian_robinson@uk.ibm.com>]

During the discussion of the proposed resolution to issue 127, I took an AI
to produce drafts of the specs that replaced the term "WS-RAP" with text
that requires the use of WS-Addressing for consideration by the TC. I have
also produced an example of how this would affect the WS-ResourceProperties
specification - if we accept this approach as the resolution to issue 127
then there are a small number of similar changes to make in WSRF-RL and
WSRF-SG.

(Updated) proposed resolution text to issue 127 >>>>>>>>>>>>

Previously all message exhanges defined by the WS-RF specifications stated
that the request messages "MUST follow the WS-Resource Access Pattern.".
The intent of this statement is a normative requirement for the use of a
WS-Addressing EndpointReference, containing the resource identifier, to
represent the reference to a WS-Resource. The precise location of the
resource identifier in a message to a WS-Resource is dependent on its
location in the EPR and on the protocol binding used to interact with the
WS-Resource endpoint but is normatively defined in the appropriate
WS-Addressing binding specification.
This issue has been resolved by a clarification to the WSRF-RP, WSRF-RL and
WSRF-SG specifications that replaces the normative reference to WS-RAP with
a normative reference to the WS-Resource definition in the WS-Resource
specification. The WS-Resource definition states the normative requirement
to use WS-Addressing EPRs.

<<<<<<<<<<<<<<<<<<<<<<<<

(See attached file: wsrf-ws_resource-1.2-spec-issue127.noRAP.doc)(See
attached file: wsrf-ws_resource_properties-1.2-spec-pr-01.127.noRAP.doc)


If we decide we prefer to retain the normative term WS-RAP, then we still
also have the original proposed resolution:
http://www.oasis-open.org/apps/org/workgroup/wsrf/email/archives/200508/msg00003.html

Regards,
Ian Robinson
STSM, WebSphere Messaging and Transactions Architect
IBM Hursley Lab, UK
ian_robinson@uk.ibm.com

wsrf-ws_resource-1.2-spec-issue127.noRAP.doc

wsrf-ws_resource_properties-1.2-spec-pr-01.127.noRAP.doc