- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sat, 30 Dec 2006 15:43:49 +0100
- To: www-webdav-dasl@w3.org
Jim Whitehead schrieb:
>> Right. I'm currently tempted to close this issue as WONTFIX for the
>> initial revision, and add an appendix discussing the issues and
>> potential approaches.
>
> I'd love to hear a better solution, but I think what you are stating is
> realistic.
OK, see
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html#rfc.issue.language-comparison>,
in particular the summary at
<http://greenbytes.de/tech/webdav/draft-reschke-webdav-search-latest.html#unresolved.issues.collations>:
B.1. Collation Support
Matching and sorting of textual data relies on collations. With
respect to WebDAV SEARCH, a combination of various design approaches
could be used:
o Require server support for specific collations.
o Require that the server can advertise which collations it
supports.
o Allow a client to select the collation to be used.
In practice, the current implementations of WebDAV SEARCH usually
rely on backends they do not control, and for which collation
information may not be available. To make things worse,
implementations of the DAV:basicsearch grammar frequently need to
combine data from multiple underlying stores (such as properties and
full text content), and thus collation support may vary based on the
operator or property.
Another open issue is what collation formalism to support. At the
time of this writing, the two specifications below seem to provide
the necessary framework and thus may be the base for future work on
collation support in WebDAV SEARCH:
1. "Internet Application Protocol Collation Registry" (<http://
www.ietf.org/internet-drafts/draft-newman-i18n-comparator-14>).
2. "XQuery 1.0 and XPath 2.0 Functions and Operators"
(<http://www.w3.org/TR/xquery-operators/#collations>).
Best regards, Julian
Received on Saturday, 30 December 2006 14:50:40 UTC