-
Notifications
You must be signed in to change notification settings - Fork 108
Adopt RDF/Sparql's entity format #6
Comments
It seems to be standard for Upsides to expanding: Some downsides:
In balance I wonder whether it's worth deviating from standard practice here. One useful feature would be to allow standard prefixes to be defined in the store to simplify use. Side note: Blazegraph supports some [default prefixes],(https://www.mediawiki.org/wiki/Wikidata_Query_Service/User_Manual#Automatic_prefixes) so you don't need to specify them in queries. |
Entities are specified by using
<entity>
orprefix:entity
. When a prefix is used, no URI is associated with it, and the prefix itself is used for sorting etc. This should be updated to match Sparql, to allow URIs to be associated with prefixes, and to handle sorting correctly. How this ends up encoded in the eventual KV store key needs some thought as well.The text was updated successfully, but these errors were encountered: