RE: [wsrf] Is WSRF9 the only issue from WS-RF and is there anything el

Subject: RE: [wsrf] Is WSRF9 the only issue from WS-RF and is there anything else in WSRF that WSDM uses?

Perhaps we can cut and paste the WSDM text below into the WSRF App Note, or atleast reference the sections in MUWS.

Which sections of MUWS for what you write below: MUWS refers to WS-ResourceLifetime for use to manageable the lifetime of relationships. WS-ServiceGroup is listed as one possible way to advertise manageable resources

----- Original Message -----
From: "Vambenepe, William N" <VBP@HP.COM>
To: "Alan Weissberger" ,
Subject: RE: [wsrf] Is WSRF9 the only issue from WS-RF and is there anything else in WSRF that WSDM uses?
Date: Fri, 29 Oct 2004 08:27:16 -0700

1.1 Use of WS-ResourceFramework

MUWS leverages the Web Services Resources Framework ([WSRF]), in which, the MUWS manageable resources are represented by Web services as “resources”, in the WSRF sense of the term. This implies that references to manageability endpoints in MUWS use the mechanism defined by WSRF, leveraging endpoint references (EPR) as defined by WS-Addressing.

I f the manageability endpoint corresponds to a variable number (zero or more) of manageable resources, then the WSRF Implied Resource Pattern MUST be followed. This means that the element(s) listed in the ReferenceProperties of a WS-Resource qualified EPR must be included in the header of messages sent to such manageability endpoints. This specification does not currently define how to obtain the EPR. There may be an out-of-band agreement between provider and consumer on how to obtain EPRs or future versions of this specification would clarify this subject.

In the specific case where a manageability endpoint corresponds to one and only one manageable resource, then either the WSRF Implied Resource Pattern, as above, or the singleton WS-Resource implied pattern MUST be used. If the singleton WS-Resource implied pattern is used, this means that the manageability endpoint does not expect to receive the elements listed in the ReferenceProperties section of WS-Resource qualified EPRs in the message headers to indicate which resource is being managed. A manageability consumer who does not have an EPR for a manageability endpoint MAY try to invoke manageability operations without including reference properties information[WV1] . If such an invocation succeeds, the manageability consumer can infer it is talking about a manageable resource through a manageability provider.

[WV2] [IS3] Further, management properties defined in MUWS are represented as “properties”, in the WSRF sense of the term, using the mechanisms defined in WS-ResourceProperties ([WS-ResourceProperties]). This means that each manageable resource exposes a resource properties document and makes this document available as specified in WS‑ResourceProperties.

Supporting WS-ResourceProperties means that any implementation of an interface that includes properties MUST include access methods to these properties as defined by WS‑ResourceProperties. Specifically, the interface MUST include the GetResourceProperty operation defined by WS-ResourceProperties and MAY include the GetMultipleProperties, SetResourceProperties and QueryResourceProperties operations. If the QueryResourceProperties operation is provided, it SHOULD support the XPath 1.0 query expression dialect, represented by URI http://www.w3.org/TR/1999/REC-xpath-19991116.

[WV1]Clarify that it should still have the other addressing headers (to, action…)

[WV2]Do we need to update because of the changes to IRP in WSRF?

[IS3]This may just refer to WS-Resource spec. May be just clarify with a picture here.

wsrf message

1.1 Use of WS-ResourceFramework