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: Fri, 11 Jul 2003 23:57:57 +0200
To: "Geoffrey M Clemm" <geoffrey.clemm@us.ibm.com>, <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCGEGBHNAA.julian.reschke@greenbytes.de>

> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Geoffrey M Clemm
> Sent: Friday, July 11, 2003 11:39 PM
> To: ietf-dav-versioning@w3.org
> Subject: RE: Namespace of attributes in DAV:property element
> What about John's particular question ... should we modify 3253 in
> the next revision to state that the "name" and "namespace" attributes
> are in the DAV: namespace, and then modify the example in 3.8.1
> to reflect this?  If there aren't many implementations yet of the

For heaven's sake, no!!!!! That would be an incompatible change.

We should clarify that the attributes are in no namespace.

> DAV:expand-property report, we could get this change publicized now,
> to minimize interoperability issues in the future.

There are. Speaking of which -- I think several server implementors claim to
support RFC3253 (basic versioning). I'd certainly hope that they all support
DAV:expand-property, as it's a required report.

> I could go either way on this, but just to get the voting started,
> I'll vote, yes, we should make this change.

No. Not only because it is a incompatible change (that breaks our server),
it's also a very unusual usage of namespaces in XML. For instance, check
XSLT: XSLT attributes are in no namespace, unless they appear on an element
which itself is not in the XSLT namespace.


<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Friday, 11 July 2003 17:58:15 UTC

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