Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should the Clade Ontology record specifiers outside of the equivalentClass expression? #62

Open
gaurav opened this issue Feb 27, 2019 · 0 comments

Comments

@gaurav
Copy link
Member

gaurav commented Feb 27, 2019

In Phyx files, we include some information about phyloreference specifiers:

{
  "label": "Alligatorinae",
  "cladeDefinition": "Alligator mississippiensis and all crocodylians closer to it than to Caiman crocodilus.",
  "internalSpecifiers": [{ "scientificNames": [{ "scientificName": "Alligator mississippiensis" }] }],
  "externalSpecifiers": [{ "scientificNames": [{ "scientificName": "Caiman crocodilus" }] }]
}

Should we retain this information when we convert this into OWL? If we choose not to, the specifiers would only be described in the equivalentClass expression. For example, the Phyx file above could be converted into OWL in JSON-LD as follows:

{
  "@type": "owl:Class",
  "label": "Alligatorinae",
  "subClassOf": "phyloref:Phyloreference",
  "obo:IAO_0000115": "Alligator mississippiensis and all crocodylians closer to it than to Caiman crocodilus.",
  "equivalentClass": { "intersectionOf": [
    { "onProperty": "phyloref:includes_TU", "someValuesFrom": { "intersectionOf": [ { "@id": "obo:NOMEN_0000107" }, { "onProperty": "dwc:scientificName", "hasValue": "Alligator mississippiensis" } ] } },
    { "onProperty": "phyloref:excludes_TU", "someValuesFrom": { "intersectionOf": [ { "@id": "obo:NOMEN_0000107" }, { "onProperty": "dwc:scientificName", "hasValue": "Caiman crocodilus" } ] } }
  ]}
}

We could parse this OWL restriction to determine that this phyloreference includes one taxonomic unit (Alligator mississippiensis) and excludes one taxonomic unit (Caiman crocodilus). Including internalSpecifiers and externalSpecifiers in the OWL ontology as Annotation properties would eliminate the need for additional parsing, but would need additional properties to be defined and would introduce some redundancy into the Clade Ontology. What do you all think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant