depedencies between ontology files

[joakim.s...@blippar.com]

Hi,

I am looking for a way to enforce consistency between two or more ontology files.
Say for example ontology1.ttl defines a class with an equivalence to another class in ontology2.ttl

ont1:Author
  rdf:type owl:Class ;
  owl:equivalentClass ont2:Writer ;

Assume someone makes an edit to ontology2.ttl and renames ont2:Writer to ont2:WriterPerson. The mapping in ontology1.ttl is no longer valid.
Can TopBraid detect this inconsistency and notify the editor?

thanks
-J

[Holger Knublauch]

Hi Joakim,

if ontology2 owl:imports ontology1 and you have both files in TopBraid, the system will know that there is a dependency. Then, when you rename a resource, TopBraid will either automatically rename that resource (if the file is imported) or ask you whether it should also rename it in files that owl:import it.

I would encourage you to try it out in practice. Note that both files should be *saved* with TopBraid so that the system can inject some # comments into the header of the file which help manage such dependencies.

HTH
Holger

--
You received this message because you are subscribed to the Google Group "TopBraid Suite Users", the topics of which include the TopBraid Suite family of products and its base technologies such as SPARQLMotion, SPARQL Web Pages and SPIN.
To post to this group, send email to topbrai...@googlegroups.com
---
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[joakim.s...@blippar.com]

Hi Holger
Yes that was helpful. After owl:importing the file containing the external class references I get a notification dialog when renaming a class.
The classes from the imported file is now also visible together with local classes - in lighter yellow color. Is it possible to hide them? It's somewhat distracting when there are many classes.

[Irene Polikoff]

They can’t be hidden from the tree that shows the class hierarchy because these classes are typically connected.

However, you can switch the class and property trees to the namespace oriented display using icons at the bottom next to the search field - e.g., 

With this, you will no longer see the subclass relationships - all classes will be presented on the same level, but you could collapse other namespaces and only expand the one you are currently working with.

Another option is to display only locally defined resources using  icon at the top (also available under the Model menu). This will give you a grid of all “local” resources.

Irene

[Joakim Soderberg]

Perfect, that’s just what I need.

Thanks

Joakim

On Mar 13, 2017, at 11:23 AM, Irene Polikoff <ir...@topquadrant.com> wrote:

They can’t be hidden from the tree that shows the class hierarchy because these classes are typically connected.

However, you can switch the class and property trees to the namespace oriented display using icons at the bottom next to the search field - e.g., <PastedGraphic-8.tiff>

With this, you will no longer see the subclass relationships - all classes will be presented on the same level, but you could collapse other namespaces and only expand the one you are currently working with.

Another option is to display only locally defined resources using <PastedGraphic-9.tiff> icon at the top (also available under the Model menu). This will give you a grid of all “local” resources.

You received this message because you are subscribed to a topic in the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/topbraid-users/AddYlbyECmU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to topbraid-user...@googlegroups.com.