Re: draft-newman-i18n-comparator: affected protocols/drafts

Hi,

I was recently asked to have a look at the latest draft 
(<http://www.w3.org/2004/08/ietf-collation/draft-newman-i18n-comparator.txt>) 
and to comment on possible effects on the WebDAV family of specs.

There are basically three groups of specs to consider here:

1) Almost all of the base specs (published: WebDAV [1], DeltaV [2], 
WebDAV ACLs [3]; in progress: BIND [4], REDIRECT [5])) do not include 
any concept of sorting at all; thus names of collations are irrelevant.

2) The WebDAV Ordered Collections Protocol ([6]) currently only defines 
client-maintained orderings. If it ever gets extended to support 
server-maintained orderings, the work done here may become interesting. 
A potential problem would be that this protocol uses URIs to identify 
orderings of WebDAV ressources, not character sequences; and it's 
perfectly ok to define an ordering on resource metadata (such as a date 
or another WebDAV property).

3) WebDAV Search ([7], also known as "DASL") could *possibly* benefit 
from a collation registry. Last time members of the WebDAV WG discussed 
this issue (almost two years ago), the consensus seemed to be to let the 
XQuery WG do the work, and then to consider how the results can be 
re-used in WebDAV SEARCH (little work has been done since, people 
interested in WebDAV SEARCH may want to review the open issues list in 
latest draft and possibly subscribe to <www-webdav-dasl@w3.org>).


Best regards, Julian


[1] <http://greenbytes.de/tech/webdav/rfc2518.html>
[2] <http://greenbytes.de/tech/webdav/rfc3253.html>
[3] <http://greenbytes.de/tech/webdav/rfc3744.html>
[4] <http://greenbytes.de/tech/webdav/draft-ietf-webdav-bind-latest.html>
[5] 
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-redirectref-protocol-latest.html>
[6] <http://greenbytes.de/tech/webdav/rfc3648.html>
[7] 
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html>

Received on Sunday, 19 December 2004 19:40:30 UTC