- From: Savas Parastatidis <Savas.Parastatidis@newcastle.ac.uk>
- Date: Tue, 26 Apr 2005 14:40:54 +0100
- To: <public-ws-addressing@w3.org>
- Cc: <humphrey@cs.virginia.edu>, <wasson@virginia.edu>
Dear all, This issue came up during some discussions with folks at the University of Virginia (Marty and Glenn cc'd) while discussing an implementation of WS-Transfer and how EPRs were used... My understanding of the Ws-Addressing specification is that the [Reference Parameters] information element item is opaque and that its children should be included in messages as header information elements without change. The specification states: "Reference parameters are provided by the issuer of the endpoint reference and are assumed to be opaque to consuming applications." The "assumed" bit is the reason for this message. Should there be normative language here? Either SHOULD or MUST? Are the consumers of an EPR allowed to reason about the contents of the [reference parameters]? My apologies if the above has already been discussed and a decision already made. Regards, -- Savas Parastatidis http://savas.parastatidis.name
Received on Tuesday, 26 April 2005 13:41:13 UTC