W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2004

Re: Request for feedback: WebDAV property datatype draft

From: Lisa Dusseault <lisa@osafoundation.org>
Date: Tue, 14 Sep 2004 11:05:38 -0700
Message-Id: <AEC9E3C6-0678-11D9-9C6B-000A95B2BB72@osafoundation.org>
Cc: Bernard Desruisseaux <bernard.desruisseaux@oracle.com>, webdav <w3c-dist-auth@w3.org>
To: Julian Reschke <julian.reschke@gmx.de>

I have a nit on the draft: the example shows a boolean value of '1' in  
section 5.1, but the text below says this is a value of 'true'.

More globally, some issues:
  - I had some understanding from previous discussions that this was  
supposed to allow multi-valued properties.  However, it appears that  
the entire property value must be provided in each PROPPATCH request.   
It would be helpful if the specification communicated this.

  - I'm a little concerned that the multi-valued stuff is in an  
appendix.  If this functionality MUST be supported (by servers that  
support the draft) then the examples should be in the main text, so  
that server implementors aren't tempted not to support it.

  - The draft should make more explicit requirements on server  
implementors, to help ensure more interoperable and consistent  
implementations.  For example, the draft should say something along the  
lines of "Servers supporting this feature MUST support the following  
list of data types and the array data type... [etc] "

  - Should there be a way for clients to detect whether the server  
supports this feature?  I would think that would be better.  However,  
if there's no way, then there should be some guidance for clients along  
the lines of "If the client supports this draft, the client SHOULD send  
data typing information for all non-string data types, without even  
knowing whether the server supports the feature."


On Sep 1, 2004, at 12:15 AM, Julian Reschke wrote:

> Hi,
> I just submitted draft 07 of draft-reschke-webdav-property-datatypes:
> <http://www.ietf.org/internet-drafts/draft-reschke-webdav-property- 
> datatypes-07.txt>
> As previously announced, this draft removes the definition of various  
> property flags and DASL extensions, concentrating on the core property  
> datatyping as implemented / being implemented in SAP's Enterprise  
> Portal and SAP Netweaver, and Xythos WebFile Server.
> This part of the spec has been stable for several years now, and as  
> far as I can tell, the WebDAV working group currently lacks the time  
> to transform this into a Working Group activity. On the other hand,  
> this work not only is implemented in shipping products, it should also  
> be valuable for anybody looking at adding typing to WebDAV properties.  
> Thus, it probably makes sense for it being published by the IETF,  
> either as experimental or proposed protocol.
> I hereby invite all readers to review the spec (both for content and  
> editorial aspects). Unless no new issues are raised, I plan to  
> last-call it and then submit it to the IESG as a private submission.  
> I'd also appreciate feedback on which publication status  
> (experimental/proposed) I should target.
> Note that those sections that were removed (see change information in  
> <http://greenbytes.de/tech/webdav/draft-reschke-webdav-property- 
> datatypes-07.html>) will later appear in a separate draft built on top  
> of the core property types spec.
> Best regards, Julian
> -- 
> <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 14 September 2004 18:06:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:32 UTC