- From: Linked Data Platform (LDP) Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Mon, 06 May 2013 15:15:57 +0000
- To: public-ldp-wg@w3.org
ldp-ISSUE-63 (Collation Support): Need to be able to specify collation with container ordering [Linked Data Platform core] http://www.w3.org/2012/ldp/track/issues/63 Raised by: Ashok Malhotra On product: Linked Data Platform core On the May 5, 2013 telcon we resolved issued 14 with the proposal: An LDPC server can indicate to a client the ordering of members in a container page using an ldp:containerOrder property. This property has as range a list of resources with two properties: ldp:containerSortPredicate, which defines the property used for sorting and ldp:containerSortOrder, which defines the ordering (ascending or descending) and is optional. Eric pointed out that the ordering uses SPARQL ORDER BY which is based on the 2 parameter fn:compare(A,B) function which takes no collation parameter. This means that e.g. "รถ" and "oe" don't order next to each other in German. To fix this problem I propose that we add an optional container property ldp:containerSortCollation. When this property is present the ordering should use the 3 parameter fn:compare(A,B,C) function. If the property is absent the 2 parameter fn:compare(A,B) function should be used.
Received on Monday, 6 May 2013 15:15:58 UTC