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

RE: RE: XML parse error: Not well-formed (Not neon-0.24.3/svn bug)

From: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2003-10-09 15:52:23 CEST

> From: Leeuw van der, Tim [mailto:tim.leeuwvander@nl.unisys.com]
> Sent: Thursday, October 09, 2003 3:02 PM
> To: svn-dev list
> Subject: RE: RE: XML parse error: Not well-formed (Not neon-0.24.3/svn
> bug)
> But why would you want to treat the name of a property the same as an
> identifier in XML, or a programming language?

...or a URI.

Why not? It *is* an identifier. It's not a displayable name.

> Why make the property-name an XML element, if it's completely up to the
> to decide what it should be?
> Just make it the value of an attribute or element, like C Mike suggests -
> much more robust!

For instance so that it can inherit XML's namespace handling. As a matter of
fact, I'd say that robustness is a reason for forbidding whitespace. For
instance, is "a b" the same thing as "a b"? Or "a &#160; b"?

But anyway, WebDAV isn't going to change. So either whitespace in property
names is something that SVN wants to support (in which case it needs to
figure out a way to marshall the whitespace through XML), or otherwise SVN
should just forbid that.

I think it's more robust not to allow it, but if it needs to be supported,
it may make sense to take a look at the SOAP spec (that needs to solve a
similar problem, maybe that solution can be used).


<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 Thu Oct 9 15:53:15 2003

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.