- From: Marc Hadley via cvs-syncmail <cvsmail@w3.org>
- Date: Fri, 22 Apr 2005 19:46:49 +0000
- To: public-ws-addressing-eds@w3.org
Update of /sources/public/2004/ws/addressing
In directory hutz:/tmp/cvs-serv22542
Modified Files:
ws-addr-soap.xml
Log Message:
Added resolution to lc30 - added new section for definition of IsReferenceParameter attribute.
Index: ws-addr-soap.xml
===================================================================
RCS file: /sources/public/2004/ws/addressing/ws-addr-soap.xml,v
retrieving revision 1.52
retrieving revision 1.53
diff -C2 -d -r1.52 -r1.53
*** ws-addr-soap.xml 22 Apr 2005 19:26:53 -0000 1.52
--- ws-addr-soap.xml 22 Apr 2005 19:46:47 -0000 1.53
***************
*** 83,89 ****
lines (010) to (012).</p>
<p>Lines (003) to (008) contain the message addressing properties serialized as SOAP
! header blocks. Specifically, line (003) specifies the identifier for
! this message and lines (004) to (006) specify the endpoint to which replies to
! this message should be sent as an Endpoint Reference. Line (007) specifies the
address URI of the ultimate receiver of this message. Line (008) specifies an
action URI identifying expected semantics.</p>
--- 83,89 ----
lines (010) to (012).</p>
<p>Lines (003) to (008) contain the message addressing properties serialized as SOAP
! header blocks. Specifically, line (003) specifies the identifier for this
! message and lines (004) to (006) specify the endpoint to which replies to this
! message should be sent as an Endpoint Reference. Line (007) specifies the
address URI of the ultimate receiver of this message. Line (008) specifies an
action URI identifying expected semantics.</p>
***************
*** 260,265 ****
addressing properties defined by &wsa-core.title;[<bibref ref="WSADDR-CORE"
/>]. The SOAP 1.2 Addressing 1.0 Module defines SOAP headers corresponding to
! the XML Infoset representation of
! the abstract message addressing properties defined in &wsa-core.title;.</p>
<p>When sending a message each property is represented using the appropriate element
information item as a SOAP header block. The resulting header blocks are
--- 260,265 ----
addressing properties defined by &wsa-core.title;[<bibref ref="WSADDR-CORE"
/>]. The SOAP 1.2 Addressing 1.0 Module defines SOAP headers corresponding to
! the XML Infoset representation of the abstract message addressing properties
! defined in &wsa-core.title;.</p>
<p>When sending a message each property is represented using the appropriate element
information item as a SOAP header block. The resulting header blocks are
***************
*** 274,295 ****
message path.</p>
</div2>
<div2 id="bindrefp">
<head>Binding Message Addressing Properties</head>
! <p>When a message is to be addressed to an endpoint, the XML
! representation of each SOAP 1.2 WS-Addressing 1.0 Feature property is
! inserted into the message as a SOAP header block subject to the
! following additional constraints:</p>
<ulist>
<item>
<p>The value of the &nsuri;/feature/ReferenceParameters property is
! added to the SOAP message header. The element information item of each of the
! [reference parameters] (including all of its [children], [attributes] and
! [in-scope namespaces]) is added as a SOAP header block in the new
! message.</p>
</item>
<item>
<p>Each header block added as a result of the above rule is annotated with a
! wsa:IsReferenceParameter attribute whose value is <attval>true</attval>.
! </p>
</item>
<item>
--- 274,310 ----
message path.</p>
</div2>
+ <div2 id="additionalinfoset">
+ <head>Additional Infoset Items</head>
+ <p>The SOAP 1.2 Addressing 1.0 Module defines the following additional XML Infoset
+ items:</p>
+ <glist>
+ <gitem>
+ <label>/[reference parameters]/@wsa:IsReferenceParameter</label>
+ <def>
+ <p>This REQUIRED attribute (of type xs:boolean) signifies whether the
+ message information header is a reference parameter, see section
+ <specref ref="bindrefp"/> for more details on its use.</p>
+ </def>
+ </gitem>
+ </glist>
+ </div2>
<div2 id="bindrefp">
<head>Binding Message Addressing Properties</head>
! <p>When a message is to be addressed to an endpoint, the XML representation of each
! SOAP 1.2 WS-Addressing 1.0 Feature property is inserted into the message as a
! SOAP header block subject to the following additional constraints:</p>
<ulist>
<item>
<p>The value of the &nsuri;/feature/ReferenceParameters property is
! added to the SOAP message header. The element information item of each
! of the [reference parameters] (including all of its [children],
! [attributes] and [in-scope namespaces]) is added as a SOAP header block
! in the new message.</p>
</item>
<item>
<p>Each header block added as a result of the above rule is annotated with a
! wsa:IsReferenceParameter attribute (see <specref ref="additionalinfoset"
! />) whose value is a valid xs:boolean representaion of
! <attval>true</attval>. </p>
</item>
<item>
***************
*** 394,402 ****
addressing properties serialized as SOAP headers in generated fault messages. Fault
messages are correlated as replies using the [relationship] property as defined in
! &wsa-core.title;[<bibref ref="WSADDR-CORE"/>]. Note that omission of the [message id]
! property in an input message may impact the ability of a fault message receiver to
! correlate the fault message to the message that caused the fault message to be
! generated. Omission of the [fault endpoint] or [reply endpoint] properties in input
! messages may impact the delivery of a generated fault message</p>
<p>The [action] property below designates WS-Addressing fault messages:</p>
<eg xml:space="preserve">
--- 409,417 ----
addressing properties serialized as SOAP headers in generated fault messages. Fault
messages are correlated as replies using the [relationship] property as defined in
! &wsa-core.title;[<bibref ref="WSADDR-CORE"/>]. Note that omission of the
! [message id] property in an input message may impact the ability of a fault message
! receiver to correlate the fault message to the message that caused the fault message
! to be generated. Omission of the [fault endpoint] or [reply endpoint] properties in
! input messages may impact the delivery of a generated fault message</p>
<p>The [action] property below designates WS-Addressing fault messages:</p>
<eg xml:space="preserve">
Received on Friday, 22 April 2005 19:46:51 UTC