Properties between a skos:Concept and an owl:Class
Pedro Paulo Favato Barcelos
Dear VB community,
I am a new user trying my first steps on VB and this is my first message on this board. I would like to thank you in advance for helping me with the following doubt.
In order to create a thesaurus, I have created a new SKOS project. In my thesaurus, I would like to say that a skos:Concept is defined by an external resource: an OWL ontology that is not part of my thesaurus.
Let us say, for example, that I would like to state that my thesaurus entry Pizza (a skos:Concept) is defined by http://example.com/ontology#Pizza (an owl:Class).
Using VB, I have imported the example ontology (http://example.com/ontology#) and tried to use an object property to link my entry to the Pizza class, but it was not possible. After that, I tried to use an annotation property, but again I it was not possible. Seems that VB only allows properties (of any kind) between skos:Concepts and instances.
I did that on Concept tab -> selected a concept -> Add property button at other properties field -> at Select range type I have selected “resource”. The OK button is not available when choosing only a class – it is mandatory that an instance must be selected.
1) How can I set a property between a skos:Concept and an owl:Class?
2) Considering that annotations can be between anything in OWL, why in VB annotation properties are not allowed between a skos:Concept and any type of resource?
Note that I do not want to use the SKOS Mapping Properties because “they are used to state mapping (alignment) links between SKOS concepts in different concept schemes” (and the external resource http://example.com/ontology#Pizza is not a skos:Concept, but it is simply an owl:Class.
I appreciate your help!
Kind regards,
Pedro Paulo Favato Barcelos
Armando Stellato
Dear Pedro Paulo,
this is indeed possible. Please forgive us if this is not so immediate as it could be (we could consider in the future an explicit way for telling VB to really pick the class that is selected on the left panel of the resource chooser, instead of the following method).
Basically, you can pick any class as an instance of rdfs:Class or owl:Class
How to do it?
By default, you can only see owl:Thing as the root of everything. This is limiting if you need to do some meta-modeling, but it’s very convenient and clean in most of the cases. Since you need to link an instance (of skos:Concept) to a class, you need to move to a more complete view
So, click on the gear button on the class panel and access the Class tree settings:
From there, select rdfs:Resource as the root class.
Then, if you like to see part of the tree of core rdf/rdfs/owl classes, you can perform a further step by clicking on rdfs:Resource and telling that you want to see rdfs:Class (tick rdfs:Class) on the right panel. Then add rdfs:Class on the left panel and on the list of subclasses, tick owl:Class. This will show you the rdfs:Resource-->rdfs:Class-->owl:Class branch any time there is a class tree opened on any panel in VocBench.
Now, go back to the action you were performing: add a value to a property of your concept.
As you can see, now rdfs:Class and owl:Class are visible. Pls notice that, even if you only configured rdfs:Resource as the root in the previously described steps and you did not configure the visibility of the subclasses, you can still see all classes by unticking the additional option of the left panel: “SubClass filter”.
Now, select, for instance, owl:Class: on the right you will see the list of classes available from your data (both explicit and imported). At this point, you can select your class from the list on the right side.
Hope it helps!
Armando
--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
vocbench-use...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vocbench-user/2ed0d741-01ce-49a9-8213-685a1d1eaa56n%40googlegroups.com.
Pedro Paulo Favato Barcelos
Armando, thank you very much for the support!
I have done the recommended steps, but unfortunately I did not have the expected results.
Let me show my steps: (1) I have clicked on the gear button on the Class tab, (2) then selected rdfs:Resource, (3) ticked all classes and finally (4) clicked on OK.
After that, even (5) clicking on the reload button, the class tree hasn't changed.
At the resource selection pop-up I still have the same visualization, with owl:Thing as the root class, and no classes are available as resources for an annotation property.
What have I done wrong?
Once again, grazie mille!
Kind regards,
Pedro Paulo Favato Barcelos
Armando Stellato
Hi!
You missed the first (and only necessary) step :-)
“From there, select rdfs:Resource as the root class.”
It’s the textfield at the top of the settings.
The other steps you did are optional, in that you can select later the de-filter option,
Cheers,
Armando
From: Pedro Paulo Favato Barcelos <pedrop...@gmail.com>
Sent: Wednesday, May 5, 2021 3:54 AM
To: Armando Stellato <stel...@uniroma2.it>
Cc: vocbench-user <vocben...@googlegroups.com>
Subject: Re: [vocbench-user] Properties between a skos:Concept and an owl:Class
Armando, thank you very much for the support!
I have done the recommended steps, but unfortunately I did not have the expected results.
Let me show my steps: (1) I have clicked on the gear button on the Class tab, (2) then selected rdfs:Resource, (3) ticked all classes and finally (4) clicked on OK.
After that, even (5) clicking on the reload button, the class tree hasn't changed.
Pedro Paulo Favato Barcelos
Armando Stellato
No worries, glad it works :-)
To view this discussion on the web visit https://groups.google.com/d/msgid/vocbench-user/dd5f9187-c5d9-4f57-8d6b-308cb33a7e82n%40googlegroups.com.