Is it enough to onyl use 'denoted by' & 'denotes' to relate between enties and their identifiers? #133
Labels
question
Further information is requested
Comments
StroemPhi
added a commit
that referenced
this issue
Aug 29, 2022
StroemPhi
added a commit
that referenced
this issue
Aug 29, 2022
* Update README-editors.md * relabel deprecated classes to be OBO QC conform * fix CI badge link * refresh import modules * #144 forgot to subsume 'event organizer role' under CRO:'contributor role' * delete subclassOf axiom for the clustering of deprecated classes to avoid warings in ROBOT report * delete wrong file * fix wrong IRIs (due to wrong Protégé settings) * check in Protege's alphabetical ordering * update IRI pf example individuls * add Munin2022 and change range of event number to xsd:integer * refactor term IRIs to proper AEON identifiers * add example instances * add 'http://' to example instance IRIs * new Protege order and fix of typo in Munin2022 IRI * add call for submissions and its missing subclasses * add example data * fix wrong subclassOf axiom on organizer and sponsor role * add members of Munin2022 general committee * use ro:member of instead of obi:member of organization in example data * add example data * closes #28, add Twitter handle as data property with example * add annotations * improve readability of definitions & add annotations * relabel AEON_0000134 (general organizing event committee) * delete the 'academic' in front of event in definitions * add 'event series maintainer role' (AEON:0000184), related to #144 * closes #135 * link to #138 * update annotations wrt term status * link to #133 wrt iao:'denoted by' subproperties * adding ISO 3166-1 alpha-2 code as interim identifier class #153
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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').The text was updated successfully, but these errors were encountered: