Closed proycon closed 2 years ago
@proycon This looks good to me... I'm not really familiar with this stuff, but I don't really see any reason not to merge this and release it as 2.1.1.
Regarding serving the JSON via content negotiation, unfortunately, I don't think that's possible. repostatus.org is currently served from GitHub Pages. Unfortunately, I don't have any desire to set up any more involved hosting for this.
This looks good to me... I'm not really familiar with this stuff, but I don't really see any reason not to merge this and release it as 2.1.1.
Thanks!
Regarding serving the JSON via content negotiation, unfortunately, I don't think that's possible. repostatus.org is currently served from GitHub Pages. Unfortunately, I don't have any desire to set up any more involved hosting for this.
I understand, that's ok, people can always still reference the JSON-LD file directory from their @context
.
@waldyrious Does this look ready to merge to you? If so, I can merge and release this tomorrow.
@waldyrious Does this look ready to merge to you?
Absolutely :) Thanks for asking.
(friendly reminder: this is still awaiting merge)
may i give this another bump?
So sorry!
So sorry for letting this sit so long. Thank you for this! It's now live on the site.
No problem, thanks!
In order to allow repostatus.org to be used in the linked open data world, it would help to have the concepts expressed in a way that allows linking with the wider semantic web. This is my attempt at doing so in an as unobtrusive way as possible. I opted for JSON-LD as the serialisation format, which is easily parsable and even retains some value even if you were ignore the context that maps it to an RDF model.
I defined the all of the concepts defined in repostatus as SKOS Concepts (https://www.w3.org/TR/skos-reference/), as that is a common and relatively simple way to organize knowledge. The concepts together form a ConceptScheme. I added opengraph vocabulary to link to the badge image (as SKOS has no vocabulary for that).
Ideally this ontology.jsonld file should be served on repostatus.org if the client sends an HTTP request with header
Accept: application/json+ld
(content negotation).