[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn log causes XML parse error (internal error)

From: <kfogel_at_collab.net>
Date: 2004-07-23 17:25:01 CEST

Julian Reschke <julian.reschke@gmx.de> writes:
> Subversion may own the "svn:" namespace in the context of Subversion,
> but it certainly doesn't in the context of XML namespaces (and thus
> WebDAV). The simple reason being that it's not a registered URI scheme
> and thus is owned by nobody (as far as the IETF is concerned).

What I'm trying to get us away from is the idea that the Subversion
property namespace is an XML namespace. The "context of XML
namespaces" does not matter, if we're talking about ownership.

It happens that one of our transport layers uses XML to send
Subversion property names, and does so in such a way that some of the
limitations of XML end up being imposed on the names. This is
unfortunate. The best solution seems to be to have Subversion impose
the limitation on users up front, so the "dangerous" data doesn't
enter the system. Okay, that's fine.

However, this solution to an implementation bug does *not* mean that
Subversion properties are anything other than just that: Subversion
properties. For over 4 years, since even before there were any
Subversion repositories in the world, Subversion has clearly
documented that property names beginning with "svn:" are under
Subversion's control.

Subversion is perfectly free to declare that. It invented Subversion
properties. They do not exist apart from Subversion. It's too bad
about the implementation bug, and we're having to take some practical
steps to deal with that. But that's no reason to suddenly declare
that Subversion properties are officially defined by the
specifications of some other piece of software (or protocol, or
format, or whatever).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 23 18:56:30 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.