Reputation: 3083
I noticed that GraphDB, in contrast to RDF4J, does not allow dots in repository IDs. We have versioned repositories containing some taxonomies. The version number is used in repository ID, so for example: taxonomy-0.1.3
.
While this works fine in RDF4J, I have to call such a repository differently in GraphDB, e.g. taxonomy-0_1_3
. I'd like to be able to use the same set of queries with federation (SERVICE
calls referencing the taxonomy repositories) on both RDF4J and GraphDB, so that I could switch between the two based on the use case. In RDF4J, I could work around version numbers by having a federated store with version-less ID pointing to a specific versioned repository. But, as far as I know, GraphDB does not support federated repositories.
Does anyone have an idea how to overcome such a problem? Or are there any plans for supporting less restrictive repository IDs in GraphDB?
Thanks a lot
Upvotes: 1
Views: 80
Reputation: 2601
GraphDB supports SPARQL Federation (or do you mean something else by "federated repositories"?)
I'll post your request as an enhancement task (GDB-5023
), but without business context it'll have low priority...
Upvotes: 0