sparna-git / skos-testing-tool Goto Github PK

Hi,

is the Turtle format recognised ?

Best,

When giving a URL in http://labs.sparna.fr/skos-testing-tool/, I note that the accept header sent by your service to resolve such URL is:

text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2

that is, basically always indicating preference for resolution in HTML format! Ontology servers that follow content negotiation practices may consequently reply to your service with HTML, surely the wrong format for use by your service.

So, the suggestion here is simply to adjust your Accept header so it reflects the formats supported by your service.

BTW, great tool!

See https://github.com/cmader/qSKOS/blob/master/README.rdoc#label-What+are+-22Authoritative+Concepts-22-3F

qSkos guesses which concepts are "authoritatives" vs. concepts that are "external" by examining the host part of the URI only. This is problematic when checking mapping relations between vocabularies that are in the same namespace : since RDFS inference is applied, mapped URIs are typed Concept, and if they have the same base URI, they are validated as well as authoritative concepts.

An option should be added to the input form to provide the substring of the URI that defines which are authoritative concepts.

Similar to what Skosify does : https://github.com/NatLibFi/Skosify/wiki/Validation
Possible fixes are :

• Generate skos:broader/skos:narrower inverses
• Delete empty labels
• Generate skos:related as symetric properties
• Delete skos:related when redundant with skos:broader/narrower
• Remove extra whitespaces or non-printable characters in the labels
• Keep only one prefLabel per language and save the others as altLabels (warniing : handle SKOS-XL !)
• Remove overlapping labels
• Cut the cycles in the hierarchy
• Automatically add documentation properties based on the Concept URI and/or label
• Remove the topConceptOf pointing to Concepts having broaders
• Delete all triples with "Undefined SKOS resources"

Concepts and Collections are disjoint classes in SKOS. Having an instance of both is bad. This could happen typically if mapping properties are used on a Collection; since mapping properties have domain skos:Concept, this would make the Collection an instance of skos:Concept too.

The "Orphan Concepts" rule should not be triggered if no skos:broader/skos:narrower/skos:related is found in the data; this indicate that it is an authority list with no semantic relations inside. Example : http://publications.europa.eu/mdr/resource/authority/continent/skos/continents-skos.rdf

Bonjour
dans mon fichier rdf plusieurs concept schemes sont declarés ainsi il est possible d'avoir aussi les liens broadMatch narrowMatch.
des redundances hierarchiques entre concept appartenant à des concepts schemes differents sont detectés.
sauf que la redundance hierarchique ne s'applique que sur les concepts d'un meme concept scheme, d'apres la doc
https://github.com/cmader/qSKOS/wiki/Quality-Issues#hierarchical-redundancy

voir le gitlab institutionnel https://gitlab.irstea.fr/copain/phenologicalstages
dans le repertoire grapevine
le fichier grapevine_scales_latest.rdf
le fichier owl est visible aussi sur agroportal https://agroportal.lirmm.fr/ontologies/PPD-GV

Hello @tfrancart ,

I am doing a catalogue of tools related to RDF/SKOS and I don't find the license of the skos-testing-tool.

Can you also confirm that the tool is maintained ?

SKOS testing tool is reporting "ol - Overlapping Labels on altLabels" among several concepts that have same altLabel. I understand a need to not allow this for prefLabel among several concepts, but to my understanding of SKOS, several SKOS concepts can have the same altLables.

Hello, I've been using skos-testing-tool with my students for small projects. I've discovered recently that this service is not working. I've tried to upload a small vocabulary but I get an empty page. The same happens when I try to use your example. Could you please take a look at this issue?
All the best
Marcin

Great tool! It would really help if the SKOS testing tool could generate a simple pass / fail result from the test that could in turn be used to generate a shields.io badge. These are really useful for showing the user a status of their .ttl file, for example.