Hello! and SKOS/OWL hybrid modelling possibilities with VocBench
Isabelle Bastien
Roland Wingerter
Armando Stellato
Dear Isabelle,
a few words more to what was already brought by Roland:
on the first question. Projects are for developing a resource (an ontology, a thesaurus, a lexicon, mere data…whatever)..then you can use it. So yes, you will export the ontology you just created in the ontology project and then owl:import it into the project holding your SKOS thesaurus.
You can get more info here: http://vocbench.uniroma2.it/doc/user/namespaces_imports.jsf#imports
Note that this is just a good policy, because you have separated spaces for developing your ontology and your thesaurus, and periodically, when you feel that your ontology has reached a new stable version, you can export it and then owl:import the new exported version into your thesaurus. However, VB does not enforce any method. You can, for instance, maintain your thesaurus and related ontology in the same project (all SKOS projects have all OWL functionalities, they just add support for SKOS) and let them evolve as one resource. However, having a clean and small project dedicated to the ontology is surely a good idea.
Just a minor note: possibly in a next version of VB, we will implement a more “live” functionality for importing an ontology directly from a project, so if you want your data to evolve directly with your ontology and yet keep them in separated projects, you can keep two different projects and yet, with a simple click, feed the ontology directly from the ontology project to the thesaurus project (or data project, in general).
Not sure about this question. I mean, on the one side, I can say: “it works as it works in OWL, VB just follow the specs and use common technologies that do the same”. However, there are a few things I can say:
- In order to see all the consequences of inheritance, you should enable a reasoner. All stores supported by VB offer some kind of reasoning. You can get some general info and pointers to proper documentation here: http://vocbench.uniroma2.it/doc/user/projects.jsf#repository_configuration
- We implemented however some trivial reasoning performed for providing better support on operations. E.g. if you want to add a triple to a certain resource, the classes of that resource (and of all the superclasses of the classes of that resource) are computed, and all the properties that have domain on one of those classes are presented initially to the user for being valued. So, whether a reasoner is configured or not, VB takes into account inheritance in this and in many other similar cases in the UX
- Not directly related to inheritance as it merely touches inverse and symmetric properties, however, since it is related to reasoning I dare to mention it :-)
since version 8.0 of VB3 we provide a trivial reasoning option. It’s a small reasoner we developed that works differently from the typical reasoners as it involves writing. Standards reasoners infer new triples from the explicit ones and show them in a dedicated space. The “eye” button in the resource view toggles in between showing and not showing the inferred triples. Our trivial reasoner will automatically write these inferred triples to the explicit knowledge (and will delete them accordingly, if deletion is inferred). This comes very handy as editors would like very simple facts (as we said, trivially inferable) to be asserted automatically. E.g. if I assert that Tom is the sibling of Jack, I’d like to see immediately that Jack is the sibling of Tom.
Kind Regards,
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/e00aa9b1-6b1c-437c-8740-7691ae18d64cn%40googlegroups.com.
Isabelle Bastien
- I create an owl:medicalEntity class Under owl:thing
- I create a "anatomy" skos concept scheme
- I create a "urinary system" skos top concept
- I give the "urinary system" skos concept the :medicalEntity class under rdf:type
Roland Wingerter
I like your example, it makes things very clear. You are looking for a way to implement facets, like the facets in the Getty AAT Thesaurus.
Here are two ways to model it.
1. Create ‘MedicalOccupations’ and “Medical Discipline’ as skos:ConceptSchemes. You can do it in your ontology or in the thesaurus. When you do it in the thesaurus, it is easier to add new concept schemes.
When adding a new concept, the entry form will present the ConceptSchemes currently enabled in the Scheme section. When a concept is selected in the structure view, try out the rightmost icon (downward pointing arrowhead). There is an option “Add selected concept's subtree to scheme...”. Isn’t it a nice equivalent to PoolParty’s “Apply Class to Concept“?
2. Create 'MedicalOccupation' and 'MedicalDiscipline' as subclasses of skos:Concept in your ontology and use them as Domain and Range for the object Property 'isSpecialistIn'.
When you owl:import your ontology into a thesaurus with existing concepts, you would have to change their class as appropriate.
You may also want to try out what this means for adding narrower concepts in VB3. I don’t think the class would be inherited from the broader.
Hope this helps.
Kind regards
Roland