- From: Clemm, Geoff <gclemm@rational.com>
- Date: Wed, 24 Oct 2001 00:05:11 -0400
- To: ietf-dav-versioning@w3.org
From: Julian Reschke [mailto:julian.reschke@gmx.de] DeltaV Draft 20 says: <!ELEMENT supported-method-set (supported-method*)> <!ELEMENT supported-method ANY> <!ATTLIST supported-method name NMTOKEN #REQUIRED> name value: a method name a) Why is the content model for supported-method "ANY"? Just for extensions? Yes. b) Do we agree that the attribute name is not qualified (so it is in no namespace)? The intention was for every element and attribute type to be declared in the DAV: namespace, so the attribute "name" is declared in the DAV:namespace, as is the element type "supported-method-set" and the element type "supported-method". In retrospective, just defining properties in terms of DTDs -- while DTDs can by definition not be normative for WebDAV (*) -- isn't a good idea. (*) DTDs can not properly capture namespace information. Neither can they adequately model the extensible model defined in section C.2.2 of RFC2518 (<http://www.greenbytes.de/tech/webdav/rfc2518.html#rfc.section.C.2.2>). I'll let the folks that like DTD's respond to that (:-). Cheers, Geoff
Received on Wednesday, 24 October 2001 00:05:44 UTC