Query for specific ConceptScheme when SPARQL endpoints contains more than one.

[wmelder]

Some thesauri, like the GTAA, are partitioned using the skos ConceptScheme as categories. When the data for multiple ConceptSchemes is all in the same SPARQL endpoint, it is necessary to specify separate queries for every single ConceptScheme. The main difference in the queries is the object of the skos:inScheme property of the skos:Concepts, being the ConceptScheme itself. It would be beneficial if the skos:ConceptScheme somehow could be seen as a variable for a query, just like the search term is.

[ddeboer]

This is a good use case for #503 and is similar to netwerk-digitaal-erfgoed/requirements-datasets#46.

A more standard way to provide multiple datasets from a single SPARQL endpoint is to use named graphs, which is expressible in SPARQL Service Descriptions.

@wmelder Are you already using named graphs? If not, what is the reason to use skos:inScheme instead?

[ddeboer]

We could generalise this by providing the dataset IRI as a SPARQL query parameter. As long as that matches the skos:inScheme (which indeed is the case in #515), you have what you need.

[ddeboer]

🎉 This issue has been resolved in version 1.0.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[ddeboer]

🎉 This issue has been resolved in version 5.6.7 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[ddeboer]

🎉 This issue has been resolved in version 1.49.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[ddeboer]

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on npm package (@latest dist-tag)

Your semantic-release bot 📦🚀

[ddeboer]

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀