Scientific report for STSM within the COST Action FP0804 FORSYS

Semantic wiki on Decision Support Systems for
Forest Management
Period: 20/01/2013 to 25/01/2013
STSM Applicants:
● Alexandra Fonseca Marques, Inesc Porto, alexandra.s.marques@inescporto.pt
Host: Professor Christian Rosset, Bern University of Applied Sciences, School of Agricultural,
Forest and Food Sciences, christian.rosset@bfh.ch
1. Purpose of the visit
The main purpose of this STSM was to pursue with the work of developing a semantic wiki for
the FORSYS project. Special attention goes to the definition of the wiki structure accounting for
all the FORSYS working domains (DSS, case studies, guidelines, country reports), reviewing
the wiki content and identifying the relevant queries.

Figure 1: Roadmap for the STSM

2. Description on the activities and the results carried
out during the STSM
A. Hand-on experiment in defining the wiki structure using the
ConceptMe
Hands-on experiment description:

Results:
● Concept Models of Dominique + Proof of concept in the wiki

● Concept Models of Group 1 and 2
(ConceptMe_model_for_categories_in_SMW.PNG)

(ConceptMe_more_extended_model_not_only_categories.PNG)
● Default Model: initial consolidated version
● Default Model final version: including DSS, Lessons, Case, CR/FMP type
(ConceptMe_DSS_LL_CR_CS_Final.PNG)
●
●
●
●
●
● Paper prototyping
DSS form

Lessons

20130124_171820.jpg

20130124_171558.jpg
Country reports/FMPlanning problem

Case study:

20130124_171558.jpg

20130124_171429.jpg
(partial photos: )
20130124_171300.jpg

20130124_171328.jpg
20130124_171351.jpg

● Consolidated Property Sheet
● Updated script
● New semantic wiki structure implemented
Rough evaluation of the experiment:
Advantages
● Clarify concepts within a group and
identify problems/Clarify the way to
collaborate, to elaborate a model
● Helps reaching consensus in a
relatively short time
● Helps approaching a complex model
and in an hierarchical way: first
defining the categories, then detailing
the problems
● Easy to use
● Share models among the group: good
to have a common starting point and
then continue
● Seems to have the potential to
manage and map the content of a wiki

Disadvantages
● The definition on how to integrate
ConceptMe and the wiki should be
defined in the first step and not in the
course of the model-> this is
important to define the future
experiment
○ Not obvious to find a way to
formalize the process in order
to develop a useful model (1
model? a combination of
models, pre-defined relations?,
levels of concepts?)
● Lack of important functionalities
related with the GUI
● Not obvious how to connet to the
semantic wiki (nor the methodology
nor the tool)
● Difficult to start from the scratch

List of suggestions about improvements in the ConceptMe:
Basic
●
●
●
●
●
●

functionalities:
pan
rename concepts and relationships (without having to erase these items previously)
expand/reduce the content of the model (e.g. like MindMap)
undo/redo
print
copy of model (without having to export it and import it back)

Setting standards at model level:
● list of relationship types (has, is a, is part of, …), which can be set at the model level
● list of color related to the type of concept (e.g. blue: category in semantic wiki, green:
property in semantic wiki)
Merging of models:
● highlight the differences with a color codification system
● make it possible to grasp different levels of detail (while defining similar concept names
during the merging process: one concept name could be set similar to more than one
concept names of the other models > hierarchical relationship > e.g. temporal scale <>
short term + medium term + long term)
● button merge is at the top of the webpage and no more visible at the end of the matching
process between the concept names (position at the bottom of the webpage)

B. Maps ConceptMe->Wiki
Why ConceptMe:

Conceptual aspects: (Christian)
Technical aspects
Results:
New deeper semantic structure for the entire wiki the pages generated automatically based on a
script that uses Property sheet/ConceptMe model
C. Content of the wiki
Finalise the semantic structure of the wiki based on the ConceptMe/property sheet model (Jussi)
DSS
● Will have new DSS descriptions due to the migration of CR results;
● No advances on migrating DSS non-semantic-> semantic
● Need to migrate existing DSS semantic -> new semantic
Country Reports/Problem types
● Input file will be ready this week
● Need to migrate directly to wiki data base (Jussi)
Case studies
● Case study task force will be responsible for inputting date
● Need to migrate existing CS semantic -> new semantic
Lessons learned
● Need to consolidate lessons-learned from the article into an excel sheet (Alexandra)
● Need migrate directly to wiki data base (Jussi)

E. Queries
F. Prepare article on Forsys Semantic wiki (Christian)
G. Article ConceptMe->Wiki (Christian)
List of co-authors:
Comment of Lucas article structure
Proposal for a new experiment (article 2)

Semantic wiki on Decision Support Systems for Forest Management

  • 1.
    Scientific report forSTSM within the COST Action FP0804 FORSYS Semantic wiki on Decision Support Systems for Forest Management Period: 20/01/2013 to 25/01/2013 STSM Applicants: ● Alexandra Fonseca Marques, Inesc Porto, alexandra.s.marques@inescporto.pt Host: Professor Christian Rosset, Bern University of Applied Sciences, School of Agricultural, Forest and Food Sciences, christian.rosset@bfh.ch
  • 3.
    1. Purpose ofthe visit The main purpose of this STSM was to pursue with the work of developing a semantic wiki for the FORSYS project. Special attention goes to the definition of the wiki structure accounting for all the FORSYS working domains (DSS, case studies, guidelines, country reports), reviewing the wiki content and identifying the relevant queries. Figure 1: Roadmap for the STSM 2. Description on the activities and the results carried out during the STSM A. Hand-on experiment in defining the wiki structure using the ConceptMe Hands-on experiment description: Results:
  • 4.
    ● Concept Modelsof Dominique + Proof of concept in the wiki ● Concept Models of Group 1 and 2 (ConceptMe_model_for_categories_in_SMW.PNG) (ConceptMe_more_extended_model_not_only_categories.PNG)
  • 5.
    ● Default Model:initial consolidated version ● Default Model final version: including DSS, Lessons, Case, CR/FMP type
  • 6.
  • 7.
    ● ● Paper prototyping DSSform Lessons 20130124_171820.jpg 20130124_171558.jpg Country reports/FMPlanning problem Case study: 20130124_171558.jpg 20130124_171429.jpg (partial photos: )
  • 8.
  • 10.
    20130124_171351.jpg ● Consolidated PropertySheet ● Updated script ● New semantic wiki structure implemented Rough evaluation of the experiment: Advantages ● Clarify concepts within a group and identify problems/Clarify the way to collaborate, to elaborate a model ● Helps reaching consensus in a relatively short time ● Helps approaching a complex model and in an hierarchical way: first defining the categories, then detailing the problems ● Easy to use ● Share models among the group: good to have a common starting point and then continue ● Seems to have the potential to manage and map the content of a wiki Disadvantages ● The definition on how to integrate ConceptMe and the wiki should be defined in the first step and not in the course of the model-> this is important to define the future experiment ○ Not obvious to find a way to formalize the process in order to develop a useful model (1 model? a combination of models, pre-defined relations?, levels of concepts?) ● Lack of important functionalities related with the GUI ● Not obvious how to connet to the semantic wiki (nor the methodology nor the tool) ● Difficult to start from the scratch List of suggestions about improvements in the ConceptMe: Basic ● ● ● ● ● ● functionalities: pan rename concepts and relationships (without having to erase these items previously) expand/reduce the content of the model (e.g. like MindMap) undo/redo print copy of model (without having to export it and import it back) Setting standards at model level:
  • 11.
    ● list ofrelationship types (has, is a, is part of, …), which can be set at the model level ● list of color related to the type of concept (e.g. blue: category in semantic wiki, green: property in semantic wiki) Merging of models: ● highlight the differences with a color codification system ● make it possible to grasp different levels of detail (while defining similar concept names during the merging process: one concept name could be set similar to more than one concept names of the other models > hierarchical relationship > e.g. temporal scale <> short term + medium term + long term) ● button merge is at the top of the webpage and no more visible at the end of the matching process between the concept names (position at the bottom of the webpage) B. Maps ConceptMe->Wiki Why ConceptMe: Conceptual aspects: (Christian)
  • 12.
    Technical aspects Results: New deepersemantic structure for the entire wiki the pages generated automatically based on a script that uses Property sheet/ConceptMe model
  • 13.
    C. Content ofthe wiki Finalise the semantic structure of the wiki based on the ConceptMe/property sheet model (Jussi) DSS ● Will have new DSS descriptions due to the migration of CR results; ● No advances on migrating DSS non-semantic-> semantic ● Need to migrate existing DSS semantic -> new semantic Country Reports/Problem types ● Input file will be ready this week ● Need to migrate directly to wiki data base (Jussi) Case studies ● Case study task force will be responsible for inputting date ● Need to migrate existing CS semantic -> new semantic Lessons learned ● Need to consolidate lessons-learned from the article into an excel sheet (Alexandra) ● Need migrate directly to wiki data base (Jussi) E. Queries F. Prepare article on Forsys Semantic wiki (Christian) G. Article ConceptMe->Wiki (Christian) List of co-authors: Comment of Lucas article structure Proposal for a new experiment (article 2)