W3C home > Mailing lists > Public > public-ws-resource-access-notifications@w3.org > April 2010

[Bug 9607] New: Support for WS-Management's RequestEPR feature

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Apr 2010 21:41:38 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-9607-2780@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9607

           Summary: Support for WS-Management's RequestEPR feature
           Product: WS-Resource Access
           Version: LC
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Transfer
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: gilbert.pilz@oracle.com
         QAContact: public-ws-resource-access-notifications@w3.org


WS-Management v1.1 [1] Section 6.5 defines a mechanism wherein, if an operation
causes the EPR of a resource to change, the new EPR can be returned to the
requester. This is useful in environments in which the value of the EPR is
derived from attributes that are themselves modifiable by wst:Put operations.
Without getting into whether or not deriving an EPR from modifiable attributes
is, in general, a good idea, we have to accept that there are systems in which,
architecturally, the costs of allowing this are less than the costs of not
allowing this.

The WS-Man WG requests that the WS-RA WG include this extension an as optional
feature of WS-Transfer.

[1] http://www.dmtf.org/standards/published_documents/DSP0226_1.1.pdf

---

Proposal: Although WS-Management defines “RequestEPR” as a general purpose
feature, this proposal narrows its application to the wst:Put/wst:PutResponse
message exchange.

1. Modify the wst:PutResponse message to have the following form:
[Action]
  http://www.w3.org/2002/ws/ra/edcopies/ws-tra/PutResponse

[Body]
  <wst:PutResponse ...>
    <wst:Representation ...>
      xs:any?
    </wst:Representation>?
    <wst:ResourceChanged>
      <wsa:EndpointReference>
        wsa:EndpointReferenceType
      </wsa:EndpointReference> |
      <wst:EPRInvalid/> |
      <wst:EPRUnknown/>
    </wst:ResourceChanged>?
    xs:any*
  </wst:PutResponse>

2. Add language to the description of PutResponse that says, effectively, “When
a service detects that a successful Put operation has changed the EPR of the
resource it MUST include the wst:ResourceChanged element in the PutResponse.”

3. Define the wst:ResourceChanged element using language similar to the
definition of wsman:RequestedEPR in Section 6.5 of WS-Man.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Wednesday, 28 April 2010 21:42:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 28 April 2010 21:42:21 GMT