Re: Request for feedback: WebDAV property datatype draft

Can we include an example of an array of XML elements in the draft, so 
that implementors are likely to do it the same way?

I would also like to request some words on ordering in the draft, 
although I agree that the W3C Note says that ordering is significant 
that doesn't say everything.
  - Say that "servers MUST preserve ordering if the server is storing a 
dead property in array format" or something equivalent
  - What clients should do is a little less clear but let's take a stab 
at it:  clients that are adding a new value, removing a value, or 
changing a value in an array SHOULD maintain the rest of the array 
ordering, unless the user actually intends to resort the array to a 
different order.

thanks,

Lisa

On Sep 23, 2004, at 6:49 AM, Julian Reschke wrote:

> Lisa Dusseault wrote:
>
>> Bernard & I came up with more questions yesterday:
>> Can there be untyped arrays?  How would I show an array of XML 
>> elements?
>
> 1) Yes. You can have whatever datatypes you want.
>
> 2) It's up to you to define a type for that (so far, we haven't needed 
> that).
>
>> E.g.  would this be valid?
>>   <supportedliveproperties xsi:type="soap-enc:Array">
>>     <supportedliveproperty><getetag/></supportedliveproperty>
>>     <supportedliveproperty><resourcetype/></supportedliveproperty>
>>     ...
>>   </supportedliveproperties>
>
> As far as I can tell, it would be legal according to 
> <http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383522>.
>
>> Are arrays assumed to be ordered or unordered?  Would it be legal for 
>> a  server to reorder array values when returning them?
>
> "The representation of the value of an array is an ordered sequence of 
> elements constituting the items of the array."
>
> Best regards, Julian
>
> -- 
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760