RE: Clarification on use of encodingStyle attribute

I seem to remember that we dealt with these questions as part of issues
169 [1] and 170 [2]. Issue 170 addresses the issue of header blocks
referencing each other and Jacek's email [3] which 169 is drawn from
talks about cross references between multiple graphs (in particular
between header blocks and body). My impression is that we do allow
multiple encodings (there is of course no hard requirement that an
encoding is based on a graph model) in a single SOAP message and that it
is not to be considered part of a single graph.

Henrik 

[1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x169
[2] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x170
[3] http://lists.w3.org/Archives/Public/xml-dist-app/2001Oct/0231.html

>Did we ever settle the question of how many disjoint graphs 
>there could be 
>within a single soap envelope, and if so how are they delimited?  For 
>example, if two separate header entries are each marked with 
>the encoding 
>style attribute (for the standard soap encoding), can there be href/id 
>connections across the two?  How about if two sibling elements 
>elements 
>within the same header entry or body are similarly marked 
>separately with 
>an encoding style attribute?  Is all the encoded data in one envelope 
>conceptually in one graph?  Does the answer change if the 
>actual href/id 
>patterns results in two disjoint sets of nodes that just 
>happen not to be 
>cross connected?  I think the answers to these questions are 
>indirectly 
>related to where you can put the encodingStyle attribute.  Thank you.

Received on Wednesday, 20 March 2002 13:15:14 UTC