Requirements will be specified as User Stories where each User Story has the following format:

As a <persona>, I want to <feature>, in order to <outcome>

See Personas, User Stories and Outcomes.

Outcomes — The Outcomes of the User Stories
Personas — The Personas that we recognize
- Subject Matter Expert — "A subject-matter expert (SME) or domain expert is a person who is an authority in a particular area or topic. The term domain expert is frequently used in expert systems software development, and there the term always refers to the domain other than the software domain.
- Council Member — "Council Member" refers to an organisation that is a member of the EDM Council or any member of such organisation. A list of EDM Council members is available at this URL: http://edmcouncil.org/councilmembers http://edmcouncil.org/councilmembers
- End User — The Persona "End User" is someone who would look at an application that has been based on the ontologies that are published by the RDF Toolkit.
- Regulator — The Persona "Regulator" is someone who would ask common sense questions like "can you show the full trace of changes and decisions that lead to this change in the data"? Which includes changes in the ontologies.
- Ontologist — The Persona "Ontologist" is a user who just wants to use the FIBO ontologies for her/his own project, importing it and extending it in her or his own ontologies.
- Developer — The Persona "Developer" is someone who would use the published artifacts in a software program that he/she is developing.
- Data Expert — A "data expert" is an individual with expertise in data management including but not limited to modelling, mining, analytics. In the context of the RDF toolkit user stories, a "data expert" is someone typically working at of the member institutions and making use of/looking to use FIBO. See also another type of experts from member institutions: Subject Matter Expert.
- Vocabulary User — TODO
User Stories
- Consistent "sorted" serialized RDF file — As an Ontologist, I want to be able to get a consistent "sorted" serialized / formatted RDF file, in order to ensure that we don't get "false positives" for changes detected by Git/Github
- have access to all Products in the Product Family — Links to FIBO Beta, FIBO Release, fibo.schema.org http://fibo.schema.org, fibo html, fibo UML diagrams with link to corresponding OWL
- Top-level file that imports "all of FIBO" — As an End User, I want a top-level file that imports "all of FIBO", in order to make it easier to load FIBO in standard tools like Topbraid, Collibra, Allegrograph, Protege
- be able to see a visualization of an Ontology — As an End User, I want to be able to see a visualization of an Ontology, in order to get a much quicker grasp of what the Ontology is about.
- Programatically know what to include in an Artifact or a Product (or part-of) — As a developer, the Artifact Ontology to tell me which domains (or ontologies) to consider valid in order to include them in an automatically created artifact
- Support "build ontologies" command in CLI — As an Ontologist, I want to be able to run the "build ontologies" command from the command line, in order to make sure that tests are run with the published artifacts and not with the sources
- browse reviews of FIBO and express my opinion — As a Council Member, i want to browse reviews of FIBO and express my opinion, in order to guarantee the transparency of FIBO BTDM with a focus on the review phase.

Browser not supported