Closed DrLeturc closed 1 year ago
That could be a good idea, however with low priority wrt other issues
This issue is now related to #65 and could be merged in one issue
I would like to propose that we build and host at Inria an "Ontology Annotation Ontology"
Its namespace would be http://ns.inria.fr/oao Its prefix would be oao: Its content would essentially be annotations properties such as, for example:
After discussion at the heartbeat meeting on 16 June 2023, we decided to close this issue in order to focus on other project priorities.
The issue https://github.com/HyperAgents/ns.hyperagents.org/issues/65 presents the properties we could use to document the ontology.
However when we take a look at LOV, there is no ontology for referring to motivating scenarios, or issues.
Thus one idea could be to group in a meta-ontology our usage to refer to issues, or motivating scenarios that use these classes or properties.
<https://github.com/HyperAgents/ns.hyperagents.org/issues/87> a :Issue
:Agent :hasIssue <https://github.com/HyperAgents/ns.hyperagents.org/issues/87>
<https://github.com/HyperAgents/ns.hyperagents.org/blob/312d115bb202dc76c704261dfe9c34a2bb923e45/scenarios/regulation.md> a :MotivatingScenario
:Agent :hasMotivatingScenario <https://github.com/HyperAgents/ns.hyperagents.org/blob/312d115bb202dc76c704261dfe9c34a2bb923e45/scenarios/regulation.md>
It would translate that
:Agent
is a class presented in the motivating scenario<https://github.com/HyperAgents/ns.hyperagents.org/blob/312d115bb202dc76c704261dfe9c34a2bb923e45/scenarios/regulation.md>
and introduced in the issue<https://github.com/HyperAgents/ns.hyperagents.org/issues/87>
Related links