[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrf] Comments on wsrf-ws_resource-1.2-spec-wd-07
The reason ResourceIdentifier is NOT used is that an EPR does not provide "identity" for a resource. An EPR is only a reference to a resource. The use and rules associated with reference parameters is covered in WS-Addressing and should not be covered in this spec. Bryan -----Original Message----- From: Wilson, Kirk D [mailto:Kirk.Wilson@ca.com] Sent: Tuesday, September 06, 2005 12:08 PM To: ian_robinson@uk.ibm.com; wsrf@lists.oasis-open.org Subject: [wsrf] Comments on wsrf-ws_resource-1.2-spec-wd-07 There now seems to be three concepts used with the space two pages: Resource Identifier Reference to a WS-Resource (which is structurally tied to WS-Addressing) And, in the SOAP example: SomeDisambiguatorElement These three concepts are never explicitly related to one other. Obviously, SomeDisabmiguator is part of the reference to a WS-Resource (ReferenceParameters). Further, I assume, after carefully trying to connect things that are in the text, that the Resource Identifier is at least one possible "disambiguator element". If so, would be clearer to use <ResourceIdentifier>R1</ResourceIdentifier> rather than <SomeDisambiguatorElement> in the example? After all, the text does say that "R1" "identifies" the resource Kirk Wilson Architect, Development Office of the CTO 802 765-4337
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]