URI for terms

[jeblad]

I would propose to create an endpoint for the terms, with a proper redirects for machine-readable content and human-readable content. (W3: Cool URIs for the Semantic Web) Such entries should also contain SKOF entries to properly relate them. (W3: SKOS – Simple Knowledge Organization System)

The simplest would be to either rewrite verifiserte_termer.csv as JSON-ld and serve that from index.html with RDFa piggybacked, or rewrite verifiserte_termer.csv as an XML file with a browser-based XSLT rewrite. After a rewrite you can add JS if you want to get paging back in.

Done right you will then be able to reference terms as semantic resources like https://matematikkradet.no/ordliste/#kropp

Note that for use on Wikidata the only thing necessary would be to have some kind of identifier inside some kind of URI that identified the correct term in your dataset.

There are other ways to do this, but I believe I would used XSLT and stored verifiserte_termer as a RDF graf (that is an XML file).

[jfremstad]

Thanks for an interesting proposal! I have to say that I'm not too familiar with the Semantic Web or its advantages, but I assume it makes it easier for other computer systems to use the data.

Although you have linked to some good documentation, it is too terse for me to get a good overview. Do you have any introductory sources that you could recommend?

Some things worth mentioning is that the technology used in this project was specifically chosen to be very user friendly (CSV file), easy to maintain and have no (or minimal) system dependencies (no PHP, web-backend, database etc.). I also think some of our less technically adept contributors would not be comfortable editing XML or JSON files.

[jeblad]

Make a single term form, not the usual pagination with several terms, and identify that term like https://matematikkradet.no/ordliste/#kropp. This is the minimum necessary to create a semantic cool URI.

To do this really simple you add id="term"(whatever term would be) to each td-element. That makes the cool uri work. Then you turn off pagination if you see a hash in the incoming URL, and highlight the target id.

Something like

$('tr').hide()
$('td:target').parent().show()

You also need some other small fixes, but it should be pretty stright forward.

[jeblad]

Simple fix to get the cool URIs to work is provided in #60. The search URI is actually enough, but the linked terms should be identifiable. The provided fix has ids, which is sufficient for cool URIs.

[jfremstad]

Thanks for your PR :+1:. I will have a look at it once I have some more time on my hands.