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

Re: request to clarify and improve Subversion property name specification

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Mon, 23 Jan 2012 17:55:38 +0000

Garret Wilson <garret_at_globalmentor.com> writes:

> On 1/23/2012 9:23 AM, Philip Martin wrote:
>> What constitutes a valid XML name? I suppose it's things that don't
>> require XML escaping?
> An XML name is things like the name of an element, e.g. <fooBar>. You
> can't "escape" in an XML name, anyway. The specification of a valid
> XML name is here:
> http://www.w3.org/TR/REC-xml/#NT-Name

So lots of high range Unicode points are allowed. How will we validate
that? Do we have any suitable code in Subversion? Do we write an XML
validator? Use some other existing validator? Do we have to extract
UTF8 multibyte characters first?

>> So you would relax the restrictions in svn_prop_name_is_valid which
>> would relax the restrictions libsvn_client. That in turn would relax
>> the restrictions in JavaHL, the other bindings and the command line
>> client. No protocol changes would be required.
> That sounds correct, although I don't know the code well enough to
> speak to actual API calls.

I thought you were proposing to write the code?

> Basically I'm proposing that we set
> publicly what constitutes a valid Subversion name, and then make
> whatever code changes are needed to conform. A test suite comes to
> mind as a tool to assist in this, but that's another subject
> altogether.

Subversion has a testsuite.

uberSVN: Apache Subversion Made Easy
Received on 2012-01-23 18:56:16 CET

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