- From: Martin Duerst <duerst@w3.org>
- Date: Mon, 22 Jul 2002 01:41:40 +0900
- To: "Julian Reschke" <julian.reschke@greenbytes.de>, <uri@w3.org>, ietf-xml-use@imc.org
I fully agree with Julian. I just have seen some other such examples in the jabber protocol at the IETF BOF, and have pointed this out as a mistake. I propose that we add something like this to the XML guidelines (http://www.ietf.org/internet-drafts/draft-hollenbeck-ietf-xml-guidelines-05. txt), just before 4.8.1: "Although there are some examples where this has been done in the past, specifications MUST NOT create new URI schemes to define namespaces." Regards, Martin. At 12:26 02/07/21 +0200, Julian Reschke wrote: >Sadly, many projects are following WebDAV's example of defining a special >URI scheme just for the purpose of identiying their namespaces. In the case >of WebDAV (RFC2518), the scheme was at least registered, and the official >errata document recognizes this as a valid issue with the protocol. > >Subversion (http://subversion.tigris.org) sadly is doing the same thing -- >it defines a new URI scheme ("svn:") for internal identifiers which now >shows up as XML namespace both in internal files (entries files for >instance) and in external marshalling (WebDAV request/response bodies). It >would be nice if this would be fixed before they reach 1.0. The issue has >certainly been raised but was rejected by their respective developers. > >Julian >
Received on Sunday, 21 July 2002 12:42:08 UTC