Where to integrate, and how to refer the scenarios in the ontologies ?

[DrLeturc]

Hi all,

"A motivating scenario [1] is a small story problem that provides a short description and a set of informal and intuitive examples to the problem it talks about. " SAMOD

The motivating scenarios justify the choice we did on the ontology. It deserves to be referred in the classes/properties which are justified by this motivating scenario.

However we didn't explicitly set the way we refer a class/property to its corresponding motivating scenarios and where we put the motivating scenarios (either in ns.hyperagents.org/scenarios/ or in ns.hyperagents.org/tests/1/motivating, or elsewhere)?

@maximelefrancois86 proposed to put in ns.hyperagents.org/tests/1/motivating ? Can we refer to it with a rdfs:seeAlso after ? Is it correct to do so ? Would you agree ?

Another idea was to create a class MotivatingScenario ?

Or anything else ?

What are pros and cons ?

[1] Uschold, M., & Gruninger, M. (1996). Ontologies: Principles, methods and applications. IEEE Intelligent Systems, 11 (2): 93-155. http://dx.doi.org/10.1109/MIS.2002.999223

[maximelefrancois86]

In SAMOD a motivating scenario is associated with (informal, then formal) competency questions, and potentially example datasets that illustrate how the ontology can be used to model the motivating scenario.

Fine if we move the motivating scenarios to a more informative folder such as /scenarios/ However I would recommend that their name (and the file name) are used as keys that we can reuse in other folders to define competency questions, or example datasets

[maximelefrancois86]

Suggestion: /scenarios folder contains the high-level scenarios (or integration tests)

then the /tests folder contains smaller-grained scenarios (general motivating unit tests)

[DrLeturc]

https://github.com/HyperAgents/ns.hyperagents.org/issues/56

The project Polifonia gives an interesting way to structure theirs folders. Should we take inspiration from it ?

[DrLeturc]

Conclusion of this issue, it has been proposed in #79 that the good way is :

• to create/modify/delete motivating scenario, you must propose a new issue and put a link towards the related issues that talk about the motivating scenario e.g. https://github.com/HyperAgents/ns.hyperagents.org/issues?q=name-of-the-motivating-scenario
• after the motivating scenario has been accepted, the issue is referred as "valid story", and the motivating scenario is created at the moment the issue is closed.
• in the file of the motivating scenario, there is a link that refers to related issues.