Hi all,

I'm extracting a SKOS lexicon automatically from a site, and I'm having some issues. To validate the file I'm using the online validator and Protege. Some examples of valid SKOS files are available here. These files are valid and open correctly on Protege. However, these files contain OWL definitions, which don't seem useful in my context.

My SKOS file is marked as valid by the online validator, but when I load in Protege I can't see any content (I only see a "thing" root node). How can I debug the file to figure out what's wrong with it? Are there other resources to validate and debug SKOS files?

Thanks for any hint!

asked 23 Aug '12, 07:11

mulone's gravatar image

accept rate: 0%

Well, I'm going to suggest taking a look at TopBraid products (disclosure - I work for TopQuadrant). You can try to open the file in TopBraid Composer (download here), which is a general Semantic technology IDE. Enterprise Vocabulary Net is a SKOS-based vocabulary editor and application server. EVN is a server product, but you can get a preview by downloading Composer-ME and opening it on a localhost address in any browser. Both of these products should be able to display the SKOS file. "Debugging" will depend on what may be wrong. The association view, choosing skos:broader, skos: narrower, etc. will display the property hierarchy - same as rdfs:subClassOf, but using the property instead. You can add the skos relationships you need in either editors.

There are elements of OWL in SKOS. skos:transitiveProperty, for example. And OWL is fully compatible with SKOS, so I'm not sure this should be a big issue for you. Depends on the details..


answered 24 Aug '12, 00:00

scotthenninger's gravatar image

scotthenninger ♦
accept rate: 17%

Thanks for your answer! Actually I want to able to open the SKOS vocabulary on Protege, so my question should be re-formulated as: how can I debug a file on Protege?

(28 Aug '12, 16:25) mulone mulone's gravatar image

As far as I understand it, Protégé does not support SKOS out of the box, hence why it might not show content. You may want to check out some extensions to Protégé like the SKOS Editor or SKOSEd.

In any case, Protégé is really for dealing with complex OWL ontologies involving lots of class axioms and such and not (originally) designed for processing individuals. @scott gives a good suggestion for an alternative tool in his answer (ahem).

Other possibilities for dedicated SKOS tools are listed here.


answered 28 Aug '12, 16:31

Signified's gravatar image

Signified ♦
accept rate: 38%

edited 28 Aug '12, 16:34

thanks! In the meantime I found the issue with SKOS + Protege: http://code.google.com/p/skoseditor/issues/detail?id=15

(28 Aug '12, 17:39) mulone mulone's gravatar image

Actually, the SKOS specification is independent from OWL. If your SKOS file has OWL definitions, that is a choice of the author and it has nothing to do with SKOS itself. You can check for those in an OWL validator, as it seems you already did.

However, if you want to check the SKOS consistency rules themselves, there are tools for that. From the W3C SKOS site:

PoolParty offers a free SKOS Thesaurus Consistency Checker service that lets you upload a thesaurus file in SKOS format and checks if the data is consistent. Consistency conditions defined in the SKOS specification are checked as well as some conditions that are mandatory for a thesaurus to be compatible for the PoolParty thesaurus management software. Check out this page on the SKOS wiki for most recent information and links.

I have been using PoolParty's online consistency checker quite successfully. Pretty much all RDF serialization formats are accepted. A minor problem is that if your SKOS file has more than one instance of the same type of error (e.g. double skos:prefLabel on the same language), it will spot only the first one it finds. You must then correct it and run the consistency checker again in order to find the next one.


answered 29 Jan '13, 07:07

Herrmann's gravatar image

accept rate: 36%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 23 Aug '12, 07:11

Seen: 953 times

Last updated: 29 Jan '13, 07:07