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