I noticed a couple problems in the foundational "Building Blocks" requirements for sorting while trying to integrate the basic requirements for sorting in OGC API - Common - Part 4: Discovery within many collections:
- The requirement part for a
sortables resource assumes that a resource exists at /collections/{collectionId}/sortables. This only makes sense for the OGC API - Features ("Searchable Catalog") Deployment Type -- not for the Local Resource Catalog, or Crawlable Catalog. That requirement expressed this way should probably be in the Searchable Catalog requirement instead, with something more flexible at this level.
- The requirement part defining the pattern for
sortby values seems unnecessarily limiting, supporting only alphabetic properties. Shouldn't any valid property identifier be allowed (i.e., something like the propertyName rule in the CQL2 BNF grammar), with the option to use double quotes to escape properties if necessary? I would expect that especially with OGC API - Features when you want to sort items.
We're currently wondering where that sortables resource should be for Common-4 -- possibly something like /collectionsSortables. There is a need to distinguish between sortables / queryables about the data (you might potentially want to expose data queryables from multiple collection at /sortables with the Root DGGS / CQL2 Filtering Requirement Classes in particular) vs. about the collections themselves, so I'm wondering how we will handle multiple such links with the same relation type at the landing page.
@pvretano @joanma747
I noticed a couple problems in the foundational "Building Blocks" requirements for sorting while trying to integrate the basic requirements for sorting in OGC API - Common - Part 4: Discovery within many collections:
sortablesresource assumes that a resource exists at/collections/{collectionId}/sortables. This only makes sense for the OGC API - Features ("Searchable Catalog") Deployment Type -- not for the Local Resource Catalog, or Crawlable Catalog. That requirement expressed this way should probably be in the Searchable Catalog requirement instead, with something more flexible at this level.sortbyvalues seems unnecessarily limiting, supporting only alphabetic properties. Shouldn't any valid property identifier be allowed (i.e., something like thepropertyNamerule in the CQL2 BNF grammar), with the option to use double quotes to escape properties if necessary? I would expect that especially with OGC API - Features when you want to sort items.We're currently wondering where that sortables resource should be for Common-4 -- possibly something like
/collectionsSortables. There is a need to distinguish between sortables / queryables about the data (you might potentially want to expose data queryables from multiple collection at/sortableswith the Root DGGS / CQL2 Filtering Requirement Classes in particular) vs. about the collections themselves, so I'm wondering how we will handle multiple such links with the same relation type at the landing page.@pvretano @joanma747