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

> 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
user
> 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   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).

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