[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrf] WS-Resource specification; section 2.1 - properties
Part of the definition of WS-Resource is: "The set of properties of the resource MUST be expressed using an XML Infoset described by XML schema. " WSRF_RP defines how this MUST be described by a resource properties document associated with the portType. A portType that offers no resource properties document would have pretty limited value in WSRF terms - what aspect of WSRF would it be using? On the other hand, there may be periods of time when a WS-Resource has no properties and so the resource properties document could be empty. That is why the resource has a set of zero or more properties, all of which can be described in the resource properties document. Regards, Ian Robinson STSM, WebSphere Messaging and Transactions Architect IBM Hursley Lab, UK ian_robinson@uk.ibm.com Rich Thompson <richt2@us.ibm.co m> To wsrf@lists.oasis-open.org 04/10/2004 16:14 cc Subject [wsrf] WS-Resource specification; section 2.1 - properties I am trying to see the value in the statement: It MUST have a set of zero or more properties which are expressible in XML infoset. The inclusion of zero appears to cancel the MUST. My understanding of properties is that they offer a view onto some portion of the state of the resource. I'm guessing that the reason for including the zero in the statement is that some WS-Resources may choose to only offer operation-based access to their internal state. From that as a basis, I would offer the following alternate text: It MAY expose some portion of its state using properties which are expressible in an XML infoset. Of course, another alternative is that offering zero properties is a standard Web service and outside the domain of WSRF, in which case the original text just needs the "zero" changed to "one". Rich Thompson Steve Graham/Raleigh/IBM@IBMUS 10/01/2004 06:22 PM To wsrf@lists.oasis-open.org cc Subject [wsrf] [wsr] WS-Resource specification WSRFers: The task force to formalize the WS-Resource definition has completed a draft and posted it to the WSRF site [1] This reflects the hard work and tough discussions amongst the team, primarily: Steve Graham, Anish Karmarkar, Jeff Mischkinsky, Ian Robinson, and Igor Sedukhin. I want to thank this task force for a month or so that was never dull, and very informative. The document accomplishes the following: a) defines terms: resource, resource identifier, WS-Resource, WS-Resource Reference b) defines the concept of a WS-Resource Access Pattern (the new improved name for "implied resource pattern") c) defines 5 embodiments of WS-Rsource Access Pattern: 1. WS-Addressing using Reference Properties 2. WS-Addressing without Reference Properties 3. WSDL 1.1 Service element 4. WSDL 1.1 Binding element 5. WS-Message Delivery. Now, the work is not complete. There are some remaining items that the TF knows needs clarification and there may be other issues that are raised when more eyes and minds are focused on the problem. Known remaining issues: a) The definition of a Ws-Resource has some fine tuning needed. There are comments in section 2.3 regarding this. b) The second WSDL 1.1 embodiment (section 3.4) is subtle and could use some further clarification, motivation, explanation. [1]http://www.oasis-open.org/apps/org/workgroup/wsrf/download.php/9547/wsrf-WS-Resource-1.2-draft-01.doc sgg ++++++++ Steve Graham (919)254-0615 (T/L 444) STSM, On Demand Architecture Member, IBM Academy of Technology <Soli Deo Gloria/> ++++++++
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]