Re: Referring to classes outside an ontology

Matthew Horridge <[email protected]>
Newsgroups gmane.comp.misc.ontology.protege.general
Message-ID <[email protected]>
Hi Joachim,

This seems o.k. to me.  (Providing faldo;Region expands to the full IRI of the class in the external ontology).  The light font-weight (as opposed to bold) indicates that you haven't said anything about the class in the current ontology.  

Cheers,

Matthew

On 16 Oct 2012, at 16:39, Joachim Baran wrote:

> Hello,
> 
>  I would just like to hear some feedback whether my approach of integrating classes outside of my own ontology is correct.
> 
>  I added the following snippet to my ontology, where I basically want to express that the range of my "region" object property is an instance of the "Region" class from the FALDO ontology.
> 
>    <owl:ObjectProperty rdf:about="http://www.sequenceontology.org/gff3#GFF3_0021">
>        <rdfs:label>region</rdfs:label>
>        <rdfs:domain rdf:resource="http://www.sequenceontology.org/gff3#GFF3_0002"/>
>        <rdfs:range rdf:resource="&faldo;Region"/>
>    </owl:ObjectProperty>
> 
>  When I load the ontology in Protege 4.1, I see that "Region" has been added to the class list, but it is shown in a normal type rather than bold faced.
> 
>  Is this the right approach to link out to other ontologies and is it expected that the other class appears among my defined classes?
> 
> Thanks,
> Joachim
> 
> _______________________________________________
> protege-discussion mailing list
> [email protected]
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
> 
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

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

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.