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

Re: Composibility problems with refps

From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
Date: Mon, 22 Nov 2004 10:32:29 -0800
Message-ID: <41A230BD.4090207@oracle.com>
To: Jonathan Marsh <jmarsh@microsoft.com>
CC: public-ws-addressing@w3.org

Or in the context of SOAP, composability with any specification that 
uses SOAP header(s) as a mechanism to convey information.


Jonathan Marsh wrote:
> Specifically, you're worried about the case where the reference
> properties and reference parameters are in a namespace used by the
> reliability, security, etc. mechanisms, right?
>>-----Original Message-----
>>From: public-ws-addressing-request@w3.org [mailto:public-ws-
>>addressing-request@w3.org] On Behalf Of Anish Karmarkar
>>Sent: Monday, November 15, 2004 11:10 AM
>>To: public-ws-addressing@w3.org
>>Subject: Composibility problems with refps
>>During last week's concall discussion of issue i008 I took an action
>>explain the composibility problem with refps in an email. This email
>>fulfills that action.
>>WS-Addressing [1] Submission includes [reference properties] and
>>[reference parameters] in the info models for EPR. These refps are
>>opaque to the consumer. In the SOAP binding of EPR, the refps are
>>as individual SOAP header blocks. I.e., a consumer of a EPR using SOAP
>>is required to copy the refps as individual SOAP header blocks without
>>understanding what the blocks mean or do.
>>Typically SOAP header blocks are part of a SOAP module and express
>>certain functionality. For example, WSS, WS-Reliability,
>>WS-ReliableMessaging, WS-C, WS-T WS-Context etc, specify header blocks
>>that have a particular meaning that is conveyed from the sender to the
>>receiver. Specifications in the realm of Web services are designed to
>>composible with other specs. For example, WS-Context can be composed
>>with WS-Reliability and WSS.
>>A consuming application that dereferences an EPR that contains refps
>>have some policies in place wrt to reliability, security,
>>transaction, privacy etc. Given that refps may contains any XML and
>>these refps are bound as SOAP header blocks, refps can potentially
>>interfere with composibility of WS-Addressing with other WS-* specs
>>the consumer may be using. The opacity of the refps prevents the
>>consumer from making any inferences about the refps in an EPR.
>>This issue is slightly different from the security of EPRs -- which
>>*may* potentially be resolved by requiring the minter of the EPR to
>>the EPR.
>>HTH to clarify the issue.
>>[1] http://www.w3.org/Submission/2004/SUBM-ws-addressing-20040810/
Received on Monday, 22 November 2004 18:33:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:07 UTC