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

Re: SOAP Arrays

From: Marc Hadley <marc.hadley@sun.com>
Date: Fri, 18 Jan 2002 14:57:48 +0000
Message-ID: <3C4837EC.2020100@sun.com>
To: Jacek Kopecky <jacek@systinet.com>
CC: xml-dist-app@w3.org
Jacek Kopecky wrote:

> 
>  section 3.4.2, 3rd paragraph seems to indicate that all
> multi-reference value use the href attribute, while it's all but
> one (the one that actually carries the value). I think it should
> be rephrased.
> 

done


>  the BNF notation: I'd rename 'size' to be 'concreteSize' because 
> the current name suggests that '*' is not a size. 
> 

done and notation updated - it may even be correct now ;-)


>  last paragraph before the note: after the recent discussions on 
> the differences between MUST,SHOULD and MAY, I'd reword the 
> paragraph to the following:
>  "A SOAP Encoding array MAY contain an enc:itemType attribute of
> type QName. This type specifies the base type for the type of
> every member of the array. The default value of this attribute is
> xsd:anyType. Each member's type SHOULD be a subtype of itemType
> or it must be the itemType itself. If a member does not specify 
> its type, it is assumed to be the itemType."
>  The weakening of MUST to SHOULD is so as not to require Schema 
> processing. The added last sentence means to explain further the 
> intent of the itemType attribute (not only a constraint on the 
> members, also a default for the members' types).
> 

done


>  the Note: I'd add a sentence to the effect that Partial arrays 
> and Sparse arrays and any other incomplete arrays can be conveyed 
> as higher-level structures constructed of normal structs and 
> complete arrays.
> 

done

New version uploaded at the same URL as last time.


Marc.



-- 
Marc Hadley <marc.hadley@sun.com>
XML Technology Centre, Sun Microsystems.
Received on Friday, 18 January 2002 10:01:01 GMT

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