W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2001


From: Jim Amsden <jamsden@us.ibm.com>
Date: Wed, 11 Apr 2001 14:08:25 -0400
To: w3c-dist-auth@w3c.org
Message-ID: <OFC3982E27.9DBA97EA-ON85256A2B.00639CFF@raleigh.ibm.com>
 Boy we've got to put our old thinking caps on for these issues! Anyway, as
 has been pointed out many times in the past, WebDAV does not specify the
 persistence format or semantics of (at least) dead properties, it only
 specifies how properties are marshalled on the wire using the protocol. It
 also does not specify anything but the property name and that its value is
 some XML element. I think WebDAV has the right to define the PROPPATCH
 prop, set, multistatus, etc. elements including the property name and any
 of their associated attributes. But it should not have anything to say
 about the value of the property other then that it is marshalled in well
 formed XML. Clients/servers can use whatever they want for attributes or
 content model for the value element, but must use the attributes (if any)
 and content specified by the WebDAV protocol for the parent of the value.

 If there is some conversion from a property value to some underlying
 storage mechanism, it is the responsibility of the server to figure out
 what to do with the properties value element, attributes, content model,
 and all. Servers may have restrictions about what value types the can
 support, how well they can serialize generic objects in XML, if they use
 RDF, XML Schema, or DTDs to validate, etc. WebDAV shouldn't need to
 concern itself with this. Any attributes on DAV defined elements that are
 not defined in the protocol should be ignored.

  "Jim Whitehead"                                                         
  <ejw@cse.ucsc.edu>                       To:        "WebDAV WG"         
  Sent by:                         <w3c-dist-auth@w3.org>                 
  w3c-dist-auth-request@w3.org             cc:                            
                                           Subject:        Issue:         
  04/10/2001 08:53 PM                                                     

 As mentioned in a previous post, now is the time to start resolving issues
 on the RFC 2518 issues list.  As fate would have it, the first issue on
 list is one that has been contentious in the past. Can we come to
 on it now?



 What is a WebDAV server required to do with XML attributes other than
 xml:lang submitted with a PROPPATCH?  This affects how well WebDAV will be
 able to support RDF, since RDF uses attributes extensively.

 Greg Stein originally raised this issue:


 See also:

Received on Wednesday, 11 April 2001 14:13:28 UTC

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