- From: Wilfredo Sánchez Vega <wsanchez@wsanchez.net>
- Date: Wed, 16 Nov 2005 14:55:54 -0800
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: webdav WG <w3c-dist-auth@w3.org>
Hate to sound ignorant again, but, well I guess I don't hate it
that much...
Recognizing that we can't say that XML sub-elements aren't allowed
in property elements because of history, the spec should encourage
clients that want to know that their data will be preserved exactly
as-is (comments and all) SHOULD encode their content, and perhaps the
spec should recommend an encoding (eg. escaped XML/CDATA) for
property contents. This has the advantage of working reliably on
100% of existing servers, regardless of how they expand namespaces,
ignore comments (or not), use CDATA or escaped XML, etc.
Clients putting sub-elements into properties should accept that
the server will likely parse those elements, potentially storing that
into some normative form, then re-render that into XML when asked for
it later, and that semantically equivalent but byte-for-byte
different data may come back. I think forcing a server author to
care about preserving the original XML rendering at all is a bad idea.
WebDAV is already pretty complicated. XML with namespaces is no
small part of that complexity. Why make it harder when an easy
solution is already available in current implementations?
-wsv
On Nov 16, 2005, at 10:42 AM, Julian Reschke wrote:
> Yes, sure. The trouble actually is to figure out what this is.
>
> For instance, I do agree with you that comments do not need to be
> preserved, but I don't agree that namespace prefixes are irrelevant.
>
> And of course there's the separate issue that we can't simply
> invent new requirements without also thinking about how to get
> servers to quickly support these....
>
> Best regards, Julian
Received on Wednesday, 16 November 2005 22:56:15 UTC