import redundancy

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

import redundancy

grantpax
I am developing a modular, tiered ontological structure with a multiple inheritance of sorts. A subset example:

 


In Protege 5 beta-16, if ontology Final imports ontologies Modules A and B, both of which import ontology CoreCore shows up twice in the "Indirect Imports" section of the "Active Ontologies -> Ontology Imports" tab of Final


Is this strictly a cosmetic issue or could something get screwed up?


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user

PastedGraphic-4.pdf (54K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: import redundancy

Csongor Nyulas-2
Administrator
It is "strictly a cosmetic issue", if you will. There are some benefits of seeing that a given ontology is imported several times, in different ways (for example if you try to remove a given ontology from the import closure, it could be helpful to know how many times is an ontology imported).

Anyway, having an ontology imported multiple times should not screw up anything.

Csongor


On 12/10/2014 08:35 AM, Grant Pax wrote:
I am developing a modular, tiered ontological structure with a multiple inheritance of sorts. A subset example:

 



In Protege 5 beta-16, if ontology Final imports ontologies Modules A and B, both of which import ontology CoreCore shows up twice in the "Indirect Imports" section of the "Active Ontologies -> Ontology Imports" tab of Final


Is this strictly a cosmetic issue or could something get screwed up?



_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: import redundancy

grantpax
Excellent. Thank you.

On Dec 10, 2014, at 1:20 PM, Csongor Nyulas <[hidden email]> wrote:

It is "strictly a cosmetic issue", if you will. There are some benefits of seeing that a given ontology is imported several times, in different ways (for example if you try to remove a given ontology from the import closure, it could be helpful to know how many times is an ontology imported).

Anyway, having an ontology imported multiple times should not screw up anything.

Csongor


On 12/10/2014 08:35 AM, Grant Pax wrote:
I am developing a modular, tiered ontological structure with a multiple inheritance of sorts. A subset example:

 



In Protege 5 beta-16, if ontology Final imports ontologies Modules A and B, both of which import ontology CoreCore shows up twice in the "Indirect Imports" section of the "Active Ontologies -> Ontology Imports" tab of Final


Is this strictly a cosmetic issue or could something get screwed up?



_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user