-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SPARQL endpoint #9
Comments
Hab' mit @lehkost über Wikidata-SPARQL-Abfragen über das dracor-Datenset gesprochen; Endpoint über eXist wäre wirklich sehr cool, momentan geht's mit externem Endpoint: Metadaten aus gerdracor mit Wikidata-Verknüpfung als RDF (nur mal als Vorschlag, vielleicht gibt's da bei den einzelnen Properties bessere Vorschläge..)
Hab' die Daten aus der gerdracor/wikidata-Liste angelegt, allerdings nur in dieser Form (@lehkost, wie ging das nochmal per API, damit ich an die Metadaten für alle Stücke komm'?):
Minimalversion der Verknüpfung:
Hab' dazu die Daten testweise in einen Triple Store eingespielt (Jena-Fuseki als Docker Container). SPARQL Endpoint ist hier (experimentell): (http://digitalhumanities.germ.univie.ac.at/jena/gerdracor/query) Idealerweise würde natürlich die eXist-DB den SPARQL Endpoint bereitstellen. Query-Interface (YASGUI): (https://gist.github.com/ingoboerner/5df5118814e6dc4322376da52c591dc7) und würde dann so aussehen: Funktioniert allerdings nur, wenn unsichere Skripte im Browser zugelassen werden, weil der SPARQL-Endpoint nicht über https:// läuft. Mit folgendem Query kann man dann die Aufführungsorte (P4647) und die jeweiligen Koordinaten aus wikidata ziehen:
Kartendarstellung funktionier mit YASGUI: |
using easyrdf seems to generate no overhead on our side. see https://gist.github.com/mathias-goebel/aba533f715bd616f9be8903a69d41e28 |
Dockercontainer: stain/jena-fuseki:latest |
Generate Basic RDF: |
as API-Function: ingoboerner@a578401 |
I skeched an ontology for dracor that would allow us to also provide the network-mesures as rdf: |
@ingoboerner The installation of the ontology has been added to the deployment and it's available at https://dracor.org/ontology. |
the sparql-endpoint in the api is implemented in a way, that it returns the results in xml, instead of json. maybe we could even leave it this way for now and change the configuration of the sparql query interface yasgui, that could be implemented in the frontend. it seems that yasgui can also handle the results in xml; it can be even changed in the settings tab here: ...and maybe it's possible to preconfigure it. See documentation here: http://yasqe.yasgui.org/doc/ |
While an
It seems that the posted query needs to be decoded before it can be used. |
I tried to change the function that generates the rdf in load.xql with commit 4f72dc9 (maybe take only the code that concerns this function and undo the rest? sorry);
I generate a blank node for the author because within dracor it does not have its own dracor-id; I tested example-rdf in my local installation of Jena and it worked. |
@cmil one more thing, is there a way to access the metrics when I generate the RDF from within the load-module? Is it |
As of 0.35.1 we have a working
Feel free to open new issues to deal with remaining problems. |
may with the rdf indexer by ljo: https://github.com/ljo/exist-sparql
The text was updated successfully, but these errors were encountered: