W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2003

RE: Namespace of attributes in DAV:property element

From: Julian Reschke <julian.reschke@greenbytes.de>
Date: Wed, 9 Jul 2003 22:01:18 +0200
To: "John R Vasta" <jrvasta@us.ibm.com>, <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCOEOJHMAA.julian.reschke@greenbytes.de>

I agree that this should be added to the issues list (basically, RFC3253bis
should clarify the role of the DTD segments, just like what we're doing with
the other news specs right now).

<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760

> -----Original Message-----
> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of John R Vasta
> Sent: Wednesday, July 09, 2003 9:42 PM
> To: ietf-dav-versioning@w3.org
> Subject: Namespace of attributes in DAV:property element
> In RFC 3253, the DTD for the DAV:property element in the
> DAV:expand-property report is
> <!ELEMENT property (property*)>
> <!ATTLIST property name NMTOKEN #REQUIRED>
> name value: a property element type
> <!ATTLIST property namespace NMTOKEN "DAV:">
> namespace value: an XML namespace
> Since all element names defined by the protocol are understood to be in
> the DAV: namespace, I would assume that attributes would be too, except
> that the example in section 3.8.1 uses the "name" attribute without a
> namespace. Was that really the intent, and if so, wouldn't it be better,
> or at least a little more consistent, to put the attributes in the DAV:
> namespace?
> In any case, I think this needs to be clarified, since the DTDs do not
> explicitly define namespaces.
> John Vasta
Received on Wednesday, 9 July 2003 16:01:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:48 UTC