Closed stap-m closed 2 months ago
Other option: define our own term tracker item and replace IAO:0000223 with our own.
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:
From latest oeo-dev 79:
editor notes
or RDFS:comment
term tracker annotation
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.
@stap-m : Any thoughts about my proposal in the comment above?
I like the proposal. I don't think we should restrict it to the usage within OEO, esp with respect to new energy ontologies. What about: A term tracker annotation is an editor note used to track the history of an entity. For each change, it records the related GitHub issue and pull request.
Being open for other ontologies is a good idea. So I agree to your improved definition.
To move on I suggest the following approach:
term tracker annotation
first.term tracker item
with term tracker annotation
. This can probably be done using search & replace in in a text editor.Sounds good to me. I'll create a PR for the new annotation.
Reopen: Not completely finished, see https://github.com/OpenEnergyPlatform/ontology/pull/1922#issuecomment-2355068869
Reopen: Not completely finished, see #1922 (comment)
@madbkr please have a look again.
I re-open this issue:
While using term tracker annotation
in #1925 I noticed that Protégé does not show the annotation properly:
Which class and module? I cannot reproduce that:
Oh, it is even weirder, the annotation appears twice, at least in oeo.omn:
I don't have that either. Which branch?
Branch feature-1873-licence-axioms of PR #1925.
It appears twice in if I look into the following files:
In oeo-physical-axiom.owl it even shows: Those two have the following IRIs:
Looks like a bug in oeo-physical-axioms.owl. Maybe something with the namespaces?
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:
Ideas of solution
Workflow checklist
I am aware that