reconsidering the usage of term tracker item

[stap-m]

Description of the issue

This comes from https://github.com/information-artifact-ontology/ontology-metadata/issues/175

We discussed this in the last oeo-dev meeting:

• IAO proposal: tighten range of IAO:0000223 to URL
• In future, only URLs are allowed, not comments, strings etc

Ideas of solution

• think of a solution how we deal with that:
  • only link to issue or PR
  • add several term tracker items (issues/PRs) for discussion history
• Update IAO import once the changes are released
• apply solution to existing entities, i.e. write a script
• document in wiki

Workflow checklist

• [ ] I discussed the issue with someone else than me before working on a solution
• [ ] I already read the latest version of the workflow for this repository
• [ ] The goal of this ontology is clear to me

I am aware that

• [ ] every entry in the ontology should have a definition
• [ ] classes should arise from concepts rather than from words

[l-emele]

Other option: define our own term tracker item and replace IAO:0000223 with our own.

[stap-m]

Other option: define our own term tracker item and replace IAO:0000223 with our own.

Sure. Maybe we can even combine our own annotation and the proper usage of IAO:0000223. Topic for next dev meeting❗

Just as an example, this is how IAO document the devolopment history:

[stap-m]

From latest oeo-dev 79:

• discussion:
  • only URLs as range and no longer plain strings: this may be a lot of work - we have many URLs to add and thousands of term trackers
  • alternative: replace IAO:0000223 with editor notes or RDFS:comment
  • we could do more research before decision?
  • implementation could be done by @madbkr
  • having the history of issues is nice
• decision: create subannotation of "editor note" -> term tracker annotation

[l-emele]

First try for a definition of term tracker annotation: A term tracker annotation is an editor note used within the Open Energy Ontology to track the history of a term. It tracks for each change the related GitHub issue and pull request.