W3C home > Mailing lists > Public > www-webdav-dasl@w3.org > April to June 1999

use of DAV namespace

From: Jim Davis <jdavis@coursenet.com>
Date: Mon, 17 May 1999 16:01:59 -0700
Message-Id: <4.1.19990517154213.00a268e0@192.168.254.128>
To: ietf-dav-versioning@w3.org, www-webdav-dasl@w3.org
The Versioning Extensions (Kaler et al, Jan 20, 1999) draft defines a
number of XML elements (some are properties, others just elements) , all in
the DAV: namespace.  Of these, at least three conflict with elements
defined by DASL.  (DAV:and, DAV:or, and  DAV:not). 

Thus It would not be possible to construct a single DTD for WebDAV with
both versioning and DASL.  I understand that, in general, WebDAV XML can't
be validated (because we allow undefined elements to be used, for
extensibility), still it seems bad if two different DAV extensions are
incompatible.

I suggest that both extensions (DeltaV and DASL) used a new namespace, at
least for those elements they introduce.

Would it be possible to use DAV://versioning/ and DAV://dasl/ respectively?

Besides the three conflicting elements, there are a number of others that
seem to me to have rather "generic" names, that is, I could imagine other
DAV extensions that might want to use these names.  I understand that tag
element names are not user visible, but still for the sake of programmers
it is useful to have meaningful names.  To avoid future confusion, it might
be better to put all new versioning elements in a new namespace.

The potentially conflicting elements names include:

DAV:comment
DAV:report
DAV:basetime
DAV:inheritancetype

I've only just joined the deltaV list, sorry if this has already come up.

regards

Jim Davis

please reply to jrd3@alum.mit.edu, despite the Reply-To address in the header.
Received on Monday, 17 May 1999 19:02:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 22 March 2009 03:38:04 GMT