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:
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?
In Phyx files, we include some information about phyloreference specifiers:
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:
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
andexternalSpecifiers
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?