search

drdozer / oboformat

Automatically exported from code.google.com/p/oboformat
0 stars 0 forks source link

Remove other than annotation axioms when is_obsolete: true #66

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Current:

    <owl:Class rdf:about="http://purl.obolibrary.org/obo/PATO_0000000">
        <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string">pato</rdfs:label>
        <oboInOwl:id rdf:datatype="http://www.w3.org/2001/XMLSchema#string">PATO:0000000</oboInOwl:id>
        <owl:deprecated rdf:datatype="http://www.w3.org/2001/XMLSchema#boolean">true</owl:deprecated>
    </owl:Class>

This treats the class, in most editors, as a direct subclass of OWL:Thing. I 
would prefer to see:

    <rdf:Description rdf:about="http://purl.obolibrary.org/obo/PATO_0000000">
        <rdfs:label rdf:datatype="http://www.w3.org/2001/XMLSchema#string">pato</rdfs:label>
        <oboInOwl:id rdf:datatype="http://www.w3.org/2001/XMLSchema#string">PATO:0000000</oboInOwl:id>
        <owl:deprecated rdf:datatype="http://www.w3.org/2001/XMLSchema#boolean">true</owl:deprecated>
    </rdf:Description>

Now there is no class, as should be the case, and editors don't get confused 
that these should be displayed in class lists. Only downside is that some 
editors (e.g. protege) don't have a mode for displaying or editing annotations 
on URI that are not entities.

Original issue reported on code.google.com by alanruttenberg@gmail.com on 14 Jan 2012 at 11:09