Skip to end of metadata
Go to start of metadata

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


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.

EDMC wiki is our main archive. Some FCTs and other working groups might be using 3rd party tooling to conduct reviews of FIBO. Content such as comments and questions could be created with these tools (e.g. FIBO Debt review in Cameo Collaborator). In-line with the council's policy this content needs to be archived on the wiki.
Confluence has capabilities to manually import content. But doing so doesn't scale up. It is cumbersome and it results in synchronization issues, for example: Confluence cannot handle the following scenario: when comments (for example) are created in a 3rd party tool and are imported back manually into Confluence using built-in importers, if other comments where made in Confluence meanwhile (on the previous version of the page being updated by the import), the built-in importers will overwrite them.
We need to develop code that uses the Confluence API to programmatically import this content to the wiki and deal with synchronization issues.



  1. We are specifically talking about tools that allow for collaborative editing of the models.  Cameo Collaborator, EVN, Pool Party, etc. are examples of this. 

    We want all of them to store the comments into a common place (e.g., Jira)

    We don't want to try to do the modeling during the meeting.  We want to collect them during the meeting, and then have them as workflow tasks to take care of later. 

    1. In the case of Pool Party (and any other SKOS-based tool), there is an extra step of "forwarding" the comment to the OWL model.  That isn't a consideration for OWL-based collaboration environments like Collaborator or EVN. 

  2. Current status, comments in Cameo are moved by hand to an appropriate confluence page (by Elie Abi-Lahoud!)   

    He wants to automate this. 

  3. Tried to rephrase so that it looks more like a real User Story but the wording of the "outcome" doesn't make much sense yet. It should be written from the perspective of the Persona, who expects the "outcome" (to have certain benefits).

  4. By the way, these User Stories are not really meant to dive deep into the "how" but are focussing on the "what".