W3C home > Mailing lists > Public > xml-dist-app@w3.org > March 2002

Re: Clarification on use of encodingStyle attribute

From: <noah_mendelsohn@us.ibm.com>
Date: Wed, 20 Mar 2002 11:14:14 -0500
To: "Herve Ruellan" <ruellan@crf.canon.fr>
Cc: Henrik Frystyk Nielsen <henrikn@microsoft.com>, Martin Gudgin <marting@develop.com>, soap@zaks.demon.co.uk, xml-dist-app@w3.org
Message-ID: <OFC32E5439.F01096A6-ON85256B82.0059D71B@lotus.com>
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.

------------------------------------------------------------------
Noah Mendelsohn                              Voice: 1-617-693-4036
IBM Corporation                                Fax: 1-617-693-8676
One Rogers Street
Cambridge, MA 02142
------------------------------------------------------------------







"Herve Ruellan" <ruellan@crf.canon.fr>
Sent by: xml-dist-app-request@w3.org
03/20/2002 10:47 AM

 
        To:     Henrik Frystyk Nielsen <henrikn@microsoft.com>
        cc:     xml-dist-app@w3.org, soap@zaks.demon.co.uk, Martin Gudgin 
<marting@develop.com>, (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        Re: Clarification on use of encodingStyle attribute


Henrik,

Henrik Frystyk Nielsen wrote:
>  [snip]
> As a result, it makes sense to allow encodingStyle on Body - it doesn't
> apply to the Body element information item but to its contents. On the
> other hand, it doesn't make sense to put the attribute on the Envelope
> and Header element information items as Header blocks don't follow any
> particular encoding style and neither does Envelope contents.

I think it would be usefull to allow the use of the SOAP Data Model and 
of the SOAP Encoding in the content of Header blocks.

If we allow this, I think we should follow the same reasoning for the 
Envelope and Header element information items as for the Body element 
information item: the encodingStyle attribute is allowed on all these, 
it doesn't apply on these but only on contained element information 
items for which an encodingStyle is meaningfull.

In this way, by defining the encodingStyle for the Envelope element 
information items, a sender is able to define once the encoding it used 
for a Header block content, for the Body content...

Does it make sense ?

Hervé.
Received on Wednesday, 20 March 2002 11:37:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:59:09 GMT