SKOS-THES has poor documentation

[nicholascar]

The reference to SKOS-THES in the skosprovider Glossary leads to an RDF document that has no:

• title
• contributor
• creator
• publisher

It also doesn't have any indication of status or use and no HTML documentation.

Some of the links given in SKOS-THES comment, e.g. http://www.niso.org/schemas/iso25964/correspondencesSKOS/ are broken.

Is SKOS-THES really in use? Perhaps the mappings are given in that RDF file but the only way it is used is via the Skosprovider or Atramhasis tools?

[nicholascar]

I have auto-generated an HTML documentation file for SKOS-THES which can be viewed as rendered here:

https://raw.githack.com/RDFLib/pyLODE/master/pylode/examples/skos-thes.html

I've not done anything other than use the pyLODE tool with default settings and add in a title "SKOS-THES" but still the documentation's not too bad.

[koenedaele]

Hi, thank you for you interest and sorry for me being slow in the uptake.

I've also noticed SKOS-THES is bad when it comes to docs. I'm pretty sure we're not the only ones using it since Getty uses it as well, eg. http://vocab.getty.edu/ontology?documentUri=http%3A%2F%2Fpurl.org%2Fiso25964%2Fskos-thes%23ThesaurusArray#anchor-1991700346 and it's listed here as well: https://lov.linkeddata.es/dataset/lov/vocabs/iso-thes (but as iso-thes).

So, I'm not really sure how to fix this. I don't feel we should maintain the canonical docs for SKOS-THES and I don't want to redefine everything. We could consider hosting some sort of Atramhasis/skosprovider docs, but that might be more work than we can take on.

[nicholascar]

I don't feel we should maintain the canonical docs for SKOS-THES and I don't want to redefine everything

If you were to just add some minimal metadata, such as title, contributor, creator & publisher to the RDF, you could do a one-time HTML document generation from that, using something like hosted pyLODE (http://pylode.surroundaustralia.com/) and then you could just link to a rendered version of that, as I did in my comment above.

That might not be perfect but it's ok! It gives you an indication of the ontology size - 6 classes, a bunch of object properties, one datatype property etc.

So however you're hosting the current RDF file, that wouldn't change, and you wouldn't be redefining anything. You could also deliver the static pyLODE HTML from whereever you're delivering the RDF file from and use the https://raw.githack.com or similar free rendering tool for it.

[koenedaele]

I think there might be a minsunderstanding. I am not hosting the RDF file. I did not develop it or distribute it, nor do I have access to the file. I was not involved in it in any way whatsoever. I just reused what someone else created for ISO. For me and the Atramhasis project, SKOS THES is an external vocabulary.

[nicholascar]

OK, now your comments make sense to me! Well, I would still encourage you to present a documentation version of it if noone else does! Shouldn't be too problematic if you auto-generate it from the source.

I feel your pain: I have very many ontologies/vocabs that I use that are poorly documented so have to decide if I do anything about that...