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

Re: Rework on SOAP 1.2 Part 2: Section 2 and 3

From: Herve Ruellan <ruellan@crf.canon.fr>
Date: Fri, 15 Mar 2002 16:25:05 +0100
Message-ID: <3C921251.2090208@crf.canon.fr>
To: "Williams Stuart" <skw@hplb.hpl.hp.com>
CC: "'Martin Gudgin'" <marting@develop.com>, Noah Mendelsohn <noah_mendelsohn@us.ibm.com>, xml-dist-app@w3.org
Hi Stuart,

Williams, Stuart wrote:
 >>>Consider this graph:
 >>>
 >>>          edgeB       +-------------+
 >>>      +-------------->+ "terminalB" |
 >>>      |               +-------------+
 >>>      |
 >>> +----+----+  edgeA   +-------------+
 >>> | structA +--------->+ "terminalA" |
 >>> +----+----+          +-------------+
 >>>      |
 >>>      |    edgeC      +---------+ edgeD  +-------------+
 >>>      +-------------->+ structB +------->+ "terminalD" |
 >>>                      +----+----+        +-------------+
 >>>                           |
 >>>                           |   edgeF     +-------------+
 >>>                           +-------------+ "terminalE" |
 >>>                                         +-------------+
I would encode this graph like this:

   <myGraph>
     <edgeA>terminalA</edgeA>
     <edgeB>terminalB</edgeB>
     <edgeC>
       <edgeD>terminalD</edgeD>
       <edgeF>terminalF</edgeF>
     </edgeC>
   </myGraph>

The "myGraph" element representing the context in which you want to pass 
your graph (it might be the element corresponding to an argument of a 
RPC for exemple).

Hope this helps,

Hervé.
Received on Friday, 15 March 2002 10:27:05 GMT

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