W3C home > Mailing lists > Public > public-ws-addressing@w3.org > November 2004

NEW ISSUE: Marking RefProps/RefParams using attributes

From: Srinivas, Davanum M <Davanum.Srinivas@ca.com>
Date: Tue, 30 Nov 2004 13:01:07 -0500
Message-ID: <87527035FDD42A428221FA578D4A9A5B0879C552@usilms24.ca.com>
To: <public-ws-addressing@w3.org>

Title: Marking RefProps/RefParams using attributes

Description: As mentioned in several threads, currently there is no way
to distinguish between regular soap headers and RefProps and RefParams
just by looking at the soap message on the wire. One could use xml
attributes to add extra information on soap headers which have been
added ONLY because they were part of the original EPR. This is basically
to be in tune with the "Self-description" mantra. 

Justification: Different types of intermediaries can use this
information for various purposes (say caching, monitoring,
logging/auditing). For example a transparent (does not generate EPR's
and is not an endpoint for soap messages) intermediary will be able to
track all Refp's flowing in the system without a user having to input
all QName's being used in the system or use some other out of band
mechanism. Another benefit is that one can even use the same QName in
both RefParams and RefProps IF we are able to mark them in some fashion
and we will be able to apply different policies based on whether a QName
is being used as a RefParam or present in RefProps. We also need a way
to ensure that attribute is understood by all nodes (and more
importantly fail when the soap nodes does not know how to handle
RefParams/RefProps attribute stuff)

Target: Core

- SOAP Headers that are added because they were part of an EPR's
ReferenceProperties are marked by adding the following attribute:
- SOAP Headers that are added because they were part of an EPR's
ReferenceParameters are marked by adding the following attribute:
- If there's at least one soap header marked with the wsa:type
attribute, then add a new header to ensure that the attribute is not
ignored silently:
<wsa:RefPs soap:mustUnderstand="true"/>

Complete Sample:
         <wsa:ReferenceParameters soap:mustUnderstand="true"/>		
         <wsa:ReferenceProperties soap:mustUnderstand="true"/>		

         <tns:expires wsa:type="parameter">32000</tns:expires>

[1] Possible Schema validation problem mentioned by Glen:
[2] Possible Signing RefProps/RefParams problem mentioned by Rich:

Discussion Threads: 

Davanum Srinivas
Computer Associates
Senior Architect, Web Services Group
Tel: +1 508 628 8251
Received on Tuesday, 30 November 2004 18:01:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:28:21 UTC