[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:23:44 +0000

Garret Wilson <garret_at_globalmentor.com> writes:

> 1. That the restriction in JavaHL svn_prop_name_is_valid() be lifted to
> allow a Subversion property to be any valid XML name, and
> 2. That there be a public specification that rigorously defines what
> makes a valid Subversion property name to prevent contradictory
> implementation issues like this in the future.

svn_prop_name_is_valid is part of libsvn_subr so this isn't just a
JavaHL thing, it's used by libsvn_client for example, but it doesn't
appear to be used by the RA or FS layers. At the FS level the property
name can be any null-terminated C string.

What constitutes a valid XML name? I suppose it's things that don't
require XML escaping?

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.

uberSVN: Apache Subversion Made Easy
Received on 2012-01-23 18:24:26 CET

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