Re: ETF: Issue 47 (SOAP Data Model)

 Marc,
 first, I apologize for responding this late.
 Now my comments:
 Your text keeps the mention about so called multistructures
which, AFAIK, are not described elsewhere in the spec and no
implementation supports them. Multistructures can be easily
viewed as structures with array members (the members that are
multi) and I think they should be serialized as such for the sake
of simplicity. So I'd like us to remove multistructures from the
data model.
 Generally, I'm not sure the data model should speak about
locally and universally scoped names, I'm also not sure we can
actually have any single-reference values if you define
multi-reference values as such that _can_ be referenced from
multiple locations.
 Finally, I'd certainly not mention the RPC section from the
data-model section as RPC seems just too high above the data
model.
 Also we might want to add a paragraph or two about when this
data model is used (actually here a pointer to RPC might be
appropriate) and that it's not at all mandatory for data carried
in SOAP messages.
 Anyway, I think this is a very good (and long needed) start.
 Best regards

                   Jacek Kopecky

                   Senior Architect, Systinet (formerly Idoox)
                   http://www.systinet.com/



On Wed, 21 Nov 2001, Marc Hadley wrote:

 > During the last ETF con-call I took an AI to propose a resolution for
 > issue 47 [1]. Attached is a first cut at attempting to extract the data
 > model specific text from the SOAP encoding section as candidate text for
 > the SOAP Data Model section in part 2.
 >
 > Assuming this passes muster then the next step is to remove duplicate
 > text from the SOAP encoding section and RPC section and to add
 > references back to the SOAP data model section where appropriate.
 >
 > Comments, flames etc ?
 >
 > Regards,
 > Marc.
 >
 > [1] http://www.w3.org/2000/xp/Group/xmlp-issues.html#x47
 >
 >

Received on Monday, 26 November 2001 16:48:28 UTC