You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Leeuw van der, Tim" <ti...@nl.unisys.com> on 2003/10/09 13:02:03 UTC

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

But why would you want to treat the name of a property the same as an
identifier in XML, or a programming language?
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!

regards,

--Tim


-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: donderdag 9 oktober 2003 14:53
To: C. Michael Pilato; Julian Reschke
Cc: Jani Averbach; svn-dev list
Subject: RE: XML parse error: Not well-formed (Not neon-0.24.3/svn bug)


> From: cmpilato@localhost.localdomain
> [mailto:cmpilato@localhost.localdomain]On Behalf Of C. Michael Pilato
> Sent: Thursday, October 09, 2003 2:25 PM
> To: Julian Reschke
> Cc: Jani Averbach; svn-dev list
> Subject: Re: XML parse error: Not well-formed (Not neon-0.24.3/svn bug)
>
>
[...]
> That's exactly the kind of DAV-ism I'm talking about.  Had the
> DAV folks been
> thinking beyond the ends of their noses, properties would look
> something like:
>
>    <prop>
>      <name>the name</name>
>      <value>the value</value>
>    </prop>

Well.

That's not a DAV-ism. Actually I'm, not aware of any language/format in
which identifiers can contain whitespace. Why is this a problem in WebDAV,
but not in XML (XML names), HTTP (message header names, method names) or
Java/C/whatever?

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

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

Posted by Julian Reschke <ju...@gmx.de>.
> 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 &#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).

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