- From: Jim Whitehead <ejw@soe.ucsc.edu>
- Date: Fri, 9 Dec 2005 10:06:56 -0800
- To: Wilfredo Sánchez Vega <wsanchez@wsanchez.net>
- Cc: WebDAV WG <w3c-dist-auth@w3.org>
Wilfredo writes: >> I still maintain that it is unreasonable to require a server to >> preserve namespace prefixes. WebDAV requires that server authors >> understand XML and XML namespaces. I'd like to better understand what the perceived implementation issues are. One issue we create by preserving namespaces is the potential for inconsistency. Consider: Request A uses namespace mapping foo="http://www.webdav.org/" and sets the value of property foo:prop1 using it. Request B uses namespace mapping foo="http://www.ucsc.edu/" and sets the value of property foo:prop2 using it. Request C requests properties prop1 and prop2. Servers could handle this by using appropriately scoped namespace declarations. It would involve a change in XML handling for some servers that put all namespace declarations at the beginning of the multistatus XML response. > >> This is especially bothersome given that if a client cares about >> preserving XML exactly as given, than a simple encoding of the XML >> will guarantee that, and the server can remain blissfully ignorant >> of that content. If you instead put the XML elements in a >> property, the server *has to* parse them, and clients should be >> willing to accept the consequenses of that. > > Escaping XML so it becomes string data solves one problem, but > creates lots of others (including weird display in generic clients, > and surprising results in SEARCH requests). So I really don't buy > in it being a proper solution to this problem in the generic case. I agree. - Jim
Received on Friday, 9 December 2005 18:09:36 UTC