Use new GTAA SPARQL endpoint

[ddeboer]

• added one GTAA dataset for testing
• added query variable as filter

[ddeboer]

Please make sure the filenames of the .rq files match those in the jsonld data. Use dashes - (not underscore _) everywhere for consistency.

Also remove the old files to remove confusion: the new endpoint should replace the old one.

[ddeboer]

I cannot test these queries locally (because I have no access to the SPARQL endpoint), so I’m assuming they are correct.

[wmelder]

The GTAA URIs have HTTP as protocol, not https. They can be dereferenced without any authentication. Verstuurd vanaf mijn iPhone

…

Op 26 feb. 2022 om 17:49 heeft David de Boer ***@***.***> het volgende geschreven: @ddeboer commented on this pull request. In packages/network-of-terms-catalog/catalog/datasets/gtaa_persoonsnamen.jsonld: > + ***@***.***": "https://schema.org/docs/jsonldcontext.jsonld", + ***@***.***": "http://data.beeldengeluid.nl/gtaa/Persoonsnamen", + ***@***.***": "Dataset", + "name": [ + { + ***@***.***": "nl", + ***@***.***": "GTAA Persoonsnamen" + } + ], + "creator": [ + { + ***@***.***": "https://www.beeldengeluid.nl/" + } + ], + "url": [ + "http://data.beeldengeluid.nl/gtaa/Persoonsnamen" I’ve just added some documentation to explain the need for the prefix. The Network of Terms has its own lookup functionality to present the same SKOS representation to clients as when they search for terms. Lookup is needed because: some sources dereference URIs correctly but return it in their own vocabulary, such as Schema.org, rather than SKOS, which clients expect from the Network of Terms other sources use SKOS internally but fail to dereference URIs, including GTAA (as of now): $ curl -v -H Accept:application/ld+json https://data.beeldengeluid.nl/gtaa/30369 < HTTP/1.1 500 Internal Server Error Could not find acceptable representation even if sources dereference correctly and use SKOS, they may return values different from those returned by the Network of Terms search, which may be confusing for clients. To know which term to source for a certain URI, the Network of Terms needs to know those prefixes. Does that clear things up? — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.

[wmelder]

The Genre_Filmmuseum dataset can be left out of the network of terms for now. I will prepare a commit for that.

[wmelder]

After merging master into branch these errors arise when running npm dev:

10:55:51 AM - File change detected. Starting incremental compilation...
../network-of-terms-catalog/src/catalog.ts(11,9): error TS2595: 'globby' can only be imported by using a default import.
../network-of-terms-catalog/src/catalog.ts(104,15): error TS7006: Parameter 'file' implicitly has an 'any' type.
10:55:52 AM - Found 2 errors. Watching for file changes.

[ddeboer]

And… merged. Thanks a lot for your contribution and patience @wmelder!

[ddeboer]

🎉 This PR is included in version 1.49.7 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[ddeboer]

🎉 This PR is included in version 5.7.0 🎉

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

Your semantic-release bot 📦🚀

[ddeboer]

🎉 This PR is included in version 1.0.7 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[ddeboer]

🎉 This PR is included in version 1.1.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[ddeboer]

🎉 This PR is included in version 1.2.0 🎉

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

Your semantic-release bot 📦🚀