At the moment AEON defines subproperties of the object properties iao:'denoted by' (obo:IAO_0000235) and iao:denotes in order to set domain and range, e.g. 'has ORCID' has domain 'Homo sapiens' and as range aeon:ORCID.
It seems as if this is too much and was designed that way under the assumption that on the application level one would specify the object property instead of the identifier class, similar to Wikidata.
Thus, it probably would be better to define the needed identifier subclasses (e.g. ORCID, DOI...) via equivalentTo statements.
For example: aeon:ORCID owl:equivalentClass 'centrally registered identifier' and (denotes only 'Homo sapiens').
At the moment AEON defines subproperties of the object properties
iao:'denoted by' (obo:IAO_0000235)and iao:denotes in order to set domain and range, e.g. 'has ORCID' has domain 'Homo sapiens' and as rangeaeon:ORCID.It seems as if this is too much and was designed that way under the assumption that on the application level one would specify the object property instead of the identifier class, similar to Wikidata.
Thus, it probably would be better to define the needed identifier subclasses (e.g. ORCID, DOI...) via equivalentTo statements.
For example:
aeon:ORCIDowl:equivalentClass'centrally registered identifier' and (denotes only 'Homo sapiens').