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

Obsolete IAO:0000117 (term editor) in favour of dc:creator #76

Open
matentzn opened this issue Nov 1, 2021 · 4 comments
Open

Obsolete IAO:0000117 (term editor) in favour of dc:creator #76

matentzn opened this issue Nov 1, 2021 · 4 comments

Comments

@matentzn
Copy link
Contributor

matentzn commented Nov 1, 2021

In an attempt to standardise:

#60

@StroemPhi
Copy link

Would it be possible to use ROBOT and a SPARQL generate querry to change this in existing ontologies that are not using ODK? And if yes a short how to would be much appreciated ;)

@zhengj2007
Copy link
Contributor

zhengj2007 commented Nov 2, 2021

I think the IAO:0000117 (term editor) may be different from dc:creator. See: information-artifact-ontology/IAO#115.

The annotation is used to "(i) this would better reflect the fact that the definition editor is the person editing the definition, but also the label, example of usages etc (ii) this would still be inline with the purpose of that annotation property, which is indicating a point of contact/reference should any question about the term arise.".

So, the person who add the term in the OWL file may not be the 'term editor' of the term. I have added the terms in the ontology without adding my name as the 'term editor' before. Besides, some time the term was created by a group. We used the group like VEuPathDB in this field. In this case, I am not sure whether ORCID is available.

@matentzn
Copy link
Contributor Author

matentzn commented Nov 3, 2021

@zhengj2007 I appreciate the subtle distinction you make here. It is my mission to break the isolation of OBO and integrate it with the wider world of FAIR semantics by adopting as much standard vocabulary from the outside as possible - even if it means that we lose some degree of discrimination.

The related issue is this one:
#60

Lets continue the discussion there instead.

@StroemPhi We have plans for a command in ROBOT that will do this sort of standardisation: ontodev/robot#901

@cthoyt
Copy link
Contributor

cthoyt commented Nov 3, 2021

I support Nico's assessment that a tiny loss of granularity would be worth the gains from standardizing.

As devil's advocate: are there practical use cases that would rely on this distinction that someone could point me to? If this isn't so obvious, then I think the discussion about the distinction isn't so relevant.

@matentzn matentzn added this to New properties in OBO Metadata Apr 8, 2022
@matentzn matentzn moved this from New properties to Property Standardisation in OBO Metadata Apr 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
OBO Metadata
Property Standardisation
Development

No branches or pull requests

4 participants