- From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
- Date: Tue, 29 Jun 2004 20:22:25 -0700
- To: "Xml-Dist-App@W3. Org" <xml-dist-app@w3.org>
During last week's concall I took an action to propose draft text to make the Resource Representation header a SOAP feature and a SOAP module. This email fulfills that action. 1) Insert a new section: --8<-- 2. SOAP Feature Name The Resource Representation header block defined by this document embodies the SOAP feature [ref to section 3.1, SOAP 1.2 part 1] [ref to section 2, SOAP 1.2 part 1] identified by the URI * "http://www.w3.org/2004/02/representation" The above SOAP feature URI can be used to identify the semantics and serialization of the Resource Representation header block. -->8-- 2) Insert a new section: --8<-- 3. SOAP Module Name The SOAP Module [ref to section 3.3, SOAP 1.2 part 1] that realizes the SOAP feature defined in [ref to section 2 of this spec] is identified by the URI * "http://www.w3.org/2004/02/representation" The above SOAP Module URI can be used to identify the semantics and serialization of the Resource Representation header block. -->8-- Please note that the URIs used to identify the feature and module are the same as the header block namespace URI. This was done because the module refers to only one header block and realizes only one feature. The feature also refers to only one header block. Is there a particular reason to make the URIs different from the namespace URI (and each other)? How we define the URIs will probably create a precedence. 3) We should also consider changing the title of the document from: "SOAP Resource Representation Header" to: "SOAP Resource Representation Header Block" Or to: "SOAP Resource Representation {Module|Feature}" Comments? -Anish --
Received on Tuesday, 29 June 2004 23:23:06 UTC