Garret Wilson <gar...@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 http://www.uberSVN.com
