W3C home > Mailing lists > Public > xml-dist-app@w3.org > November 2001

Re: updated proposal on issue #144 - array metadata in SOAP Encoding

From: Jacek Kopecky <jacek@systinet.com>
Date: Wed, 7 Nov 2001 18:38:57 +0100 (CET)
To: Rich Salz <rsalz@zolera.com>
cc: <xml-dist-app@w3.org>
Message-ID: <Pine.LNX.4.33.0111071833560.32183-100000@mail.idoox.com>
Rich, you have showed an example where the asterisk is at the
first position, a situation excluded by the beginning of the text
you'd like to change:

 >  In case there is an asterisk on other than the first position,
 > all the members in the array MUST specify their position.

I agree that the only asterisk at the first position in the size
attribute brings virtually no problem to deserialization because
the problems with asterisks can be summarized as "don't know when
to overflow and increment the previous dimension" but in this
case there is no overflowing and no previous dimension. I don't
want to require position attributes on members in such a case, if
the text inadvertedly does, it's my phrasing mistake.

Best regards,


                   Jacek Kopecky

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



On Wed, 7 Nov 2001, Rich Salz wrote:

 > I agree arrays with unsized internal dimensions are difficult.
 >
 > If the array size is "* 2" then this seems to meet your current wording:
 > 	<tns:foo>
 > 	 <i enc:offset="3 0"><x>r2</x><y>c0</y></i>
 > 	 <i><x>r2</x><y>c1</y></i>
 > 	 <i><x>r3</x><y><c0></y></i>
 >
 > Do you want to say that enc:position MUST be used to specify the
 > position?  That's fine with me; handling all the possible cases where
 > offset and size together "are enough" would be too complicated.  If so,
 > then I think you need to explicitly say that.
 >
 >
Received on Wednesday, 7 November 2001 12:39:00 GMT

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