RE: Proposal for resolving 144, 161, 117: array serialization

I respectfully disagree that a SOAP layer that loses such information
could be described as "compliant" if by that is meant compliant with the
full SOAP specification in a general-purpose way.  (The absence of full,
general-purpose compliance may be perfectly satisfactory for many
applications; that is a different matter.)

First, the SOAP specification explicitly sanctions the use of a post
schema validation infoset.  See, for instance, SOAP 1.1 section 5 rule 2
part c. I believe that the proposed SOAP 1.2 is even more strong and
clear on this point.

Second, the encoding rules describe mapping between XML instances and
graphs.  If a particular SOAP support library happens to lose some
information along the way, information that is clearly described as part
of the mapping, then the support library does not support that part of
the spec, not in a general purpose way.  

-----Original Message-----
From: Rich Salz [] 
Sent: Wednesday, December 26, 2001 5:46 PM
To: Andrew Layman;;
Subject: RE: Proposal for resolving 144, 161, 117: array serialization

>While the element names are not significant qua array element, they may
>be significant in other ways, such as affecting the post schema
>validation infoset, I would think.

I don't think you can count on that, when the SOAP layer assigns its own
names or strips them before passing the data up, that's compliant.

Received on Thursday, 27 December 2001 15:40:51 UTC