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

Re: ETF and editors: Issue 17 and 48: Proposal for describing when to use SOAP encoding

From: Marc Hadley <marc.hadley@sun.com>
Date: Tue, 19 Feb 2002 16:09:43 +0000
Message-ID: <3C7278C7.6040009@sun.com>
To: Henrik Frystyk Nielsen <henrikn@microsoft.com>
CC: xml-dist-app@w3.org
This looks good as far it goes, I'm not sure that it captures the issue 
48 resolution completely, in particular that the RPC representation is 
specifically dependent on the data model and encoding.

Regards,
Marc.

Henrik Frystyk Nielsen wrote:

> This mail is primarily for ETF and SOAP 1.2 editors but others are free
> to read along.
> 
> Issue 17 [1] references a mail [2] from Bryan Murry bringing up the
> issue of when and why to use the SOAP data model and encoding. This mail
> provides a proposal for how to address the issue by proposing some text
> that may fit in SOAP 1.2 part 2 section 2 [3].
> 
> Issue 17 is marked as editorial. Note that issue 48 [4] is already
> marked as closed, however, the editors still have it on their to-do
> list.
> 
> PROPOSAL OUTLINE
> ----------------
> 
> The proposal is to provide two text clarifications
> 
> A) In part 2 section 2 [3], clarify the optionality of the model and the
> encoding
> 
> B) In part 2, section 3 [5], clarify the relationship between the data
> model and the encoding
> 
> C) Remove the last paragraph in section 3 [5]
> 
> PROPOSAL
> --------
> 
> A) Change the introductory text in section 2 [3] from
> 
> "The SOAP data model represents information as a graph of typed nodes.
> The type system used in the SOAP data model is a generalization of the
> common features found in type systems in programming languages,
> databases and semi-structured data. A type is either a simple (scalar)
> type or is a compound type constructed as a composite of several other
> typed parts. Examples of simple types are "string," "integer,"
> enumeration, etc. Compound types are described as follows:"
> 
> To
> 
> "The SOAP data model represents information as a graph of typed nodes.
> The type system used in the SOAP data model is a generalization of the
> common features found in type systems in programming languages,
> databases and semi-structured data.
> 
> The purpose of the data model is not to introduce a programming model in
> SOAP but rather to provide a mapping of non-XML based instance data to
> some wire representation. It is important to note that use of the SOAP
> data model and the SOAP data encoding is optional. Applications which
> already model data in XML, for example using W3C XML schema, may never
> have any need for using the SOAP data model. Because of the optionality
> of using the SOAP data model and encoding, it is NOT a requirement to
> implement it as part of a SOAP node.
> 
> A type is either a simple (scalar) type or is a compound type
> constructed as a composite of several other typed parts. Examples of
> simple types are "string," "integer," enumeration, etc. Compound types
> are described as follows:"
> 
> B) Change first paragraph in part 2, section 3 [5] from
> 
> "SOAP encoding describes how to serialize instances of data that conform
> to the data model described in 2 The SOAP Data Model for inclusion in
> SOAP messages."
> 
> To
> 
> "SOAP encoding describes how to serialize instances of data that conform
> to the data model described in 2 The SOAP Data Model for inclusion in
> SOAP messages. Note that nothing precludes the specification of
> different encodings based on other data models, or indeed that make
> different use of the SOAP data model. The SOAP encodingStyle attribute
> information item (see [1] SOAP Encoding Attribute) can be used to
> indicate the encoding used."
> 
> C) The last part of the edit is to remove the paragraph:
> 
> "Use of the data model and encoding style described in this section is
> encouraged but not required; other data models and encodings can be used
> in conjunction with SOAP (see [1]SOAP Encoding Attribute)."
> 
> as we already address this in section 2.
> 
> Comments?
> 
> Henrik Frystyk Nielsen
> mailto:henrikn@microsoft.com
> 
> [1] http://www.w3.org/2000/xp/Group/xmlp-issues#x17
> [2]
> http://discuss.develop.com/archives/wa.exe?A2=ind0008&L=soap&F=&S=&P=257
> 26
> [3] http://www.w3.org/2000/xp/Group/1/10/11/soap12-part2.html#datamodel
> [4] http://www.w3.org/2000/xp/Group/xmlp-issues#x48
> [5] http://www.w3.org/2000/xp/Group/1/10/11/soap12-part2.html#soapenc
> 
> 


-- 
Marc Hadley <marc.hadley@sun.com>
XML Technology Centre, Sun Microsystems.
Received on Tuesday, 19 February 2002 11:09:52 GMT

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