- From: Jean-Jacques Moreau <moreau@crf.canon.fr>
- Date: Tue, 04 Dec 2001 09:33:43 +0100
- To: Jacek Kopecky <jacek@systinet.com>
- CC: xml-dist-app@w3.org
Is this the correct behaviour? Presumably, if a first header references a second header targeted at '.../none', it does depend on that second header... and hence I would expect the "SOAP Encoding processor" to deserialise both the first and the second header. Or am I misinterpreting what you were suggesting? Jean-Jacques. Shouldn't the "SOAP Encoding processor" Jacek Kopecky wrote: > I just disagree with the fact that whether or not to dereference > the href attribute in SOAP Encoded data is dependent on > application semantics. > If the application requires to be able to decide whether or not > to dereference some URI, the URI must be a value in the data > graph. IMO it's the SOAP Encoding processor that MUST handle SOAP > Encoding references. > It is true though that the data wouldn't be deserialized (and > therefore references needn't be resolved) for example on a header > targeted at '.../none'. [...]
Received on Tuesday, 4 December 2001 03:34:08 UTC