- From: Jacek Kopecky <jacek@systinet.com>
- Date: Tue, 4 Dec 2001 12:01:05 +0100 (CET)
- To: <xml-dist-app@w3.org>
Jean-Jacques,
by deserializing something I understand deserializing a data
graph rooting in the something. In case of your two headers, for
example
<env:Header>
<ns:a actor="next" href="#1" encodingStyle=".../encoding" />
<ns:b actor="none" id="1">blah</ns:b>
</env:Header>
The deserialization layer is asked to deserialize a graph
rooting in <ns:a>. It is true that the deserialization process
will also read and interpret the element <ns:b>, but the
processing model won't know about this and therefore from the
point of view of SOAP Processing Model the header ns:b is _not_
being processed.
What I meant in the text below is that the following would _not_
result in a fault:
<env:Header>
<ns:a actor="none" href="http://there.is.no/such/thing"/>
</env:Header>
Best regards
Jacek Kopecky
Senior Architect, Systinet (formerly Idoox)
http://www.systinet.com/
On Tue, 4 Dec 2001, Jean-Jacques Moreau wrote:
> 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 06:01:07 UTC