A DSL for Corporate Wiki Initialization - Advanced Information Systems Engineering - page 245

- Content class. There is not a FreeMind counterpart for the Content class as
such. Rather all nodes in the map except for “Organigram” , “Presentation” ,
“Restriction” , “Event” and “Template” nodes (and descendants) stand for
Content Items . The node title behaves as an identifier, so that two FreeMind
nodes placed differently but with the same title, stand for the same Item .
This allows the Content graph to be flattened as a FreeMind tree.
- Item class. Items are typed as “category”, “article”, “template” and “event” .
Category Items are denoted as fork nodes (i.e., nodes with the “fork” style).
Article Items are captured as bubble nodes. Next, Template Items are
children of the “ Template ” node. These nodes can either hold the page text
content (i.e., text attribute) themselves as a child with the “ info ”icon or
point to external documents from where the content is obtained at compile
time (only txt and word as xml exported files in the current version) Finally,
Event Items are children of the “ Event ” node. As for the boolean properties,
discussion, rssFeed and indexPaneEntry , the affected Items (regardless of
their type) are decorated with the “ stop sign ”icon ,a“ flag ”icon and

“ look here ”icon , respectively.
- Link class. Links are classified as relatedWith , belongsTo , templatedBy and
scheduledFor . FreeMind offers two kinds of connectors: Edges, which are the
default arcs connecting a node with its child, and ArrowLinks ,whichare
arcs connecting two nodes anywhere in the map. Edges are interpreted as
belongsTo links when they connect an Item to a category Item (e.g., fig.
3, arc from “Database design” to “Deliverables” )andas scheduledFor when
they connect an Item to an event Item (e.g., fig. 3, edge from “ Requirement
analysis ”to“ 01/19/2011 ”). As for ArrowLinks , they sustain (1) RelatedWith
links when they relate an Item to another Item (e.g., fig. 3, arc from “ Software
design ”to“ Database design ”) and (3) TemplatedBy links when the ingoing
node stands for a template Item (e.g., fig. 3, arc from “ Purchase entry UC ”
to “ UseCaseTemplate ”).

5 Verification of WSL Maps

WSL maps are a subset of FreeMind maps, i.e., WSL metamodel imposes
additional constraints on top of the FreeMind metamodel. Such constraints
can be verified on user request or at deployment time. Fig. 5 provides a
snapshot of the “Tools” menu now extended to address WSL maps :“WSL
configuration” permits to configure parameters for the MediaWiki installation;
“WSL deployment” causes the generation of the wiki instance from the WSL
specification; “WSL Skeleton” provides a FreeMind mapwiththebasic WSL
nodes (e.g., Organigram , Restriction ,etc)sothatmisspellsareprevented;and
finally, “WSL Map Checking” triggers WSL map verification.
Fig. 5 depicts the verification outcome for our sample problem (see fig. 3).
Messages can be warnings and errors. For our sample, two warnings are noted.