Take a cue from Polifonia ?

[DrLeturc]

Fabien recently shared info on a project Poliphonia.

Poliphonia is a H2020 project where they provide a collection of components for developing intelligent applications leveraging musical cultural heritage by deploying an ecosystem of computational methods and tools supporting discovery, extraction, encoding, interlinking, classification, exploration of, and access to musical heritage knowledge on the Web.

What is interesting in this project is that they use their github in a way similar to ours. For instance they use the notion of stories but this is what we call motivating scenarios. You can get an example of story : here.

I thought it might be interesting to take inspiration from this project and discuss in this issue what should we retain about their methodology and position ours.

Maybe some new issues must be opened like :

• the name we use for the folder motivating_scenarios while they are talking about stories and they have a structured name for each story e.g. Name-of-the-persona#progressive-number_KeywordRepresentingTheMainGoal e.g. a person has a role and it generates stories that justify the ontology vocab. Should we consider a similar structure ?
• they use only a readme.md and not a contributing file, and each story has its own readme.md
• a structure of a story is composed by : Persona, Goal, Scenario, Competency questions (CQs), Resources (optional) while our structure is those of SAMOD : Identifier, Question, Outcome, Example, Depends on
• they explained how to create a story here. Do you see any points that could be relevant to consider in our approach ?
• ...

[DrLeturc]

We decided to not consider the set of Personas since it may represent another additional constraint to take into account when creating a story. Furthermore, it does not seem vital for the construction of a motivating scenario.