Re: [SOAP Encoding Issue] Most to least specific encodingStyles,HOW?

 Asir,
 when using the word "restriction" I think I meant that any data
serialized according to the restriction MUST be a valid
serialization of the data according to the "unrestricted" rules
while it may not be true the other way around.
 While SOAP Encoding (the particular encoding) does not
explicitly allow subsetting, I can imagine other data models and
encodings to allow it.
 But still, unless somebody brings up a valid and important case,
I think we can siplify SOAP here. 8-)

                   Jacek Kopecky

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



On Tue, 30 Oct 2001, Asir S Vedamuthu wrote:

 > Jacek,
 >
 > Thank you for looking into this.
 >
 > > If it is useful for a receiver to know that this data was
 > > serialized according to the subset (2), while other receivers
 > > might just fall back to the general set (1) not knowing/caring
 > > about the restriction, the multiplicity of encodingStyle might be
 > > justified.
 >
 > As you said, this needs to be clarified with lots of text and examples.
 > Also, per your description, then we need additional constraints,
 >
 > - any most specific encodingStyle in the whitespace delimited list must be a
 > valid restriction of the next encodingStyle in this list. BTW, I do not know
 > what restriction means in this context.
 >
 > - all of the encodingStyles in the whitespace delimited list must use the
 > same data model (there is some contention if encodingStyle implicitly
 > specifies a data model)
 >
 > > If it is useful for a receiver to know that this data
 > > was serialized according to the subset (2)
 >
 > Are there any benefits in knowing that this data was serialized according to
 > the subset?
 >
 > Lets say a receiver implements only a subset of SOAP Encoding and likes to
 > know if parts of the message were serialized using a subset. Per issue 48
 > resolution [1], I do not believe that we encourage subsetting SOAP Encoding.
 > It is in take it or leave it mode - "but if they claim conformance with the
 > SOAP encoding they must pass the SOAP encoding conformance tests". Then this
 > hypothetical receiver does not conform to SOAP Encoding.
 >
 >
 > Like Rich and you, I vote for simple things and will be happy to see this go
 > ..
 >
 > [1] http://lists.w3.org/Archives/Public/xml-dist-app/2001Oct/0242.html
 >
 >
 > Regards, Asir

Received on Tuesday, 30 October 2001 12:48:02 UTC