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

Re: Issue 1971: certain property names cause non-wf XML responses

From: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2005-01-19 01:56:17 CET

Colin Bendell wrote:
> http://subversion.tigris.org/issues/show_bug.cgi?id=1971
> The problem is that colon is not a valid character in the qname in an
> xml element. The SVN DAV exposes the custom property as having a
> namespace of "http://subversion.tigris.org/xmlns/custom/" and a qname of
> the property name. What if the namespace for a custom property was
> taken from the property instead? Why not use the namespace the property
> is suggesting. For example, "cvs2svn:cvs-rev" would be broken out as
> having a namespace of "cvs2svn" and a qname of "cvs-rev"? Colons are
> permissible values inside the namespace, so if the property were
> foo:bar:property it should be broken out as "foo:bar" and "property" for
> the namespace and qname respectively.

A valid XML namespace is an (absolute) URI (reference) that the creator
of the element's definition controls. I don't think that a string like
"cvs2svn" qualifies as a good namespace name.

On the other hand, if you consider "cvs2svn" a namespace *prefix* (as
defined per XMLNS), and have a separate prefix-to-namespaceUri lookup
table, things may look better.

Best regards, Julian

<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 19 01:57:32 2005

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.