Relationship between SOAP data model, SOAP encoding, and RPC

As part of the discussions about the SOAP RPC convention in section 7
[1] and how it relates to section 5 [2], the RPC taskforce are
considering the following clarification outlined below. Before we spend
cycles on doing any edits, we would like to get input on whether this is
a reasonable position or whether there are reasons for not doing it. 

This mail is my attempt to summarize the proposal to a larger audience -
please comment as appropriate.

Issue 1: SOAP Section 5 currently defines a directed graph data model
with elements like struct, array, id/href, etc. *as well as* a
particular encoding of that data model without clearly separating the

Clarification 1: We would like to clarify the relationship between the
data model and the particular encoding by saying that the SOAP encoding
is one of several potential encodings of the SOAP data model.  

Issue 2: The formulation of the definition of the root attribute is

Clarification 2: The SOAP Root attribute defined in section 5.6 [3] is
part of the SOAP encoding and can be used to disambiguate roots from
non-roots when this is not apparent from the encoded instance.

Issue 3: The relationship between section 5 and section 7 is unclear

Clarification 3: Make clear that the RPC convention is based on the SOAP
data model and point out that the RPC invocation or the result of an
invocation is modeled as a single-rooted instance of the SOAP data model
where the root of the instance is the RPC invocation or the result of
the RPC invocation.

As for any other data modeled using the SOAP data model, the RPC
convention can use the SOAP encoding to represent an instance of an RPC
invocation or the result of an invocation. In case the SOAP encoding is
used and a single root can not be unambiguously determined, the SOAP
Root attribute can be used to determine roots from non-roots.

Henrik Frystyk Nielsen 


Received on Tuesday, 14 August 2001 13:45:00 UTC