W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 1999

RE: Section 23.4 Appendix 4 - XML Namespace in WebDAV

From: John Stracke <francis@ecal.com>
Date: Tue, 30 Mar 1999 13:52:13 EST
Message-Id: <199903301352.AA201457934@appoint.net>
To: w3c-dist-auth@w3.org
---------- Original Message ------------------
>The WebDAV's XML namespace rules only apply to elements used directly to
>execute WebDAV XML commands. Therefore it is NOT safe to assume that XML
>sent as payload inside a PUT request or a GET response follows the WebDAV

Sure; you wouldn't expect it to anyway--we're supposed to be

>You can only be sure that the WebDAV rules are being used for WebDAV
>related command/responses. BTW, webDAV rules do apply to property values,
>this was necessary for consistency.

This one does bother me.  Suppose I have a property whose content
is an XML snippet--for example, a description of the resource which
can be displayed by some client.  The XML in this snippet will
have to follow WebDAV namespace rules, which are slightly more
restrictive than the standard ordered-pair rules (you can't safely
have namespaces http://www.example.com/foo and
http://www.example.com/foob, although you can in the ordered-pair
world).  So, if your snippet is written by an editor that wants
to use tags from two such namespaces, it can't be stored into a
DAV property.

Why is it necessary for DAV to say anything about the namespaces
used in property values, anyway? Shouldn't a server be able to
accept arbitrary XML without caring?

|John Stracke    | My opinions are my own | S/MIME & HTML OK  |
|Chief Scientist | NT's lack of reliability is only surpassed |
|eCal, Inc.      |  by its lack of scalability. -- John Kirch |

Received on Tuesday, 30 March 1999 13:50:22 UTC

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