=Paper=
{{Paper
|id=Vol-1593/article-03
|storemode=property
|title=None
|pdfUrl=https://ceur-ws.org/Vol-1593/article-03.pdf
|volume=Vol-1593
|dblpUrl=https://dblp.org/rec/conf/www/WellerM16a
}}
==None==
https://ceur-ws.org/Vol-1593/article-03.pdf
Towards a Collaborative Process Platform
Publishing Processes according to the Linked Data Principles
Tobias Weller Maria Maleshkova
AIFB Institute, KIT AIFB Institute, KIT
Englerstr. 11 Englerstr. 11
76131 Karlsruhe, Germany 76131 Karlsruhe, Germany
tobias.weller@kit.edu maria.maleshkova@kit.edu
ABSTRACT transform inputs into an intended output. Modeling pro-
Research in the area of process modeling and analysis has a cesses is done in multiple domains in order to define an ideal
long-established tradition. Process modeling is among oth- workflow, hence a framework is given for executing the pro-
ers used in the medical domain to define an ideal workflow in cess. Among others is process modeling used in the clinical
order to ensure an efficient treatment of patients. These pro- environment to define clinical guidelines in order to ensure
cesses are often defined and maintained by multiple persons. an efficient treatment of patients.
Furthermore, multiple persons are interested in these defined These clinical guidelines support physicians by recommend-
processes to compare them with own defined processes for ing the sequence and timing of actions that is necessary to
improvements purposes. Current solutions provide tools to achieve an efficient treatment of patients [14, 9]. These
model processes locally and export them in standard formats guidelines are also called clinical pathways and are based
in order to exchange them. Besides, there are some collabo- on evidence from insights of former treatments of patients.
ration tools available to model processes collaboratively and Each clinic has their own pathways based on their evi-
see changes dynamically. However, these solutions do not dences and experiences. Therefore, there are multiple path-
publish the data according to the Linked Data principles. ways available that target different problems and care needs [22,
Enriching processes with semantic information is useful in 12, 7]. These clinical pathways become more complex due
order to perform enhanced analysis. However, different users to the increasing volumes of data and developments in the
can only provide particular meta-information on same pro- medical domain. At the same time, clinics are interested in
cess steps. To address these problems we 1) developed an in- clinical pathways of other clinics in order to improve their
tuitive, open-source extension for Semantic MediaWiki that own pathways and adapt them to latest trends and insights.
supports the graphical modeling of processes and stores the Besides the structure of processes, there are also many
information in a structured way; 2) enable to enrich the pro- semantic information about processes available. There are
cesses with semantics from ontologies and knowledge graphs many ontologies and semantic information in different data
with references to external data sources 3) provide adapted sources like e.g. DBpedia1 available that can be used for an-
views on meta-information in order to not overwhelm users alyzing purposes. In addition, there are further semantic in-
with unnecessary information. formation about processes available that cannot be captured
with current standard formats for storing process models.
Another important aspect that occurs nowadays is that
CCS Concepts processes become more complex and that they are usually
•Information systems → Wikis; Process control systems; maintained by multiple persons. These persons do not nec-
•Applied computing → Health care information systems; essarily share the same location but are located in different
countries. This is often the case in international projects.
Keywords Therefore, a collaborative tool that allows to capture, anno-
tate and share information about processes collaboratively
Business Process Model and Notation, Semantic MediaWiki, is preferable in order to allow a simplified acquisition and
Linked Data principles, Collaborative Platform, User Roles exchange of processes and respective meta-information.
Linked Data is a method to publish data in a structured
1. INTRODUCTION way2 . Publishing data according to these principles facili-
According to the process definition from ISO 9000:2015 [1] tates the exploration and interlinks between different docu-
are processes defined as a set of interrelated activities that ments. Thus information can be looked up by a HTTP URI
and are provided in a structured way. Additional links to
other URIs offer the possibility to explore even more infor-
mation and enrich further knowledge.
Applying the Linked Data principles on processes would
allow to 1) model processes and its set of activities with
unique HTTP URIs; 2) provide useful information about
1
http://wiki.dbpedia.org, visited 24 January 2016
2
Copyright is held by the author/owner(s). http://www.w3.org/DesignIssues/LinkedData.html, vis-
WWW2016 Workshop: Linked Data on the Web (LDOW2016) ited 24 January 2016
processes in a standard format like the Resource Descrip- who are not performing the processes but working in the
tion Framework3 (RDF); and 3) interlink processes with in- same domain. Hence, clinics are for example interested in
formation from other data sources. clinical pathways from other clinics to get insights from their
During the acquisition of semantic information from users, processes and treatments of patients. This exchange of in-
one has to consider different views on processes and its el- formation allows to improve own processes by the insights
ements. Thereby, different users can provide and are in- of other clinics.
terested in different meta-information for same process ele- However, processes do not store semantic information.
ments. Considering this aspect, in order to not overwhelm Current formats like e.g. BPMN 2.0 XML4 , proposed by the
users with meta-information that is not relevant for him, OMG as standard format for storing Business Process Model
is an important aspect while acquiring corresponding meta- and Notation (BPMN) diagrams, do not allow to capture se-
information about processes. mantic information like e.g. references to medical guidelines,
In order to address these problems, we present a collabora- responsible persons and conditions. Therefore, useful meta-
tive platform that allows to acquire processes, applying the information that can be used for analyzing processes gets
Linked Data principles on them, capture meta-information lost. However, these information can be used to improve
and enable different views on these meta-information. healthcare services in planning resources and improving the
We demonstrate the applicability of our solution by mod- outcome of clinical pathways.
eling a concrete perioperative process and enable users with Therefore, we would like to provide a possibility to capture
different roles to see different views on provided forms, which processes, semantics in processes and the accruing meta-
they can use to annotate the elements. The used methods information in a collaborative platform. Thus, multiple per-
and an overview of the system are described in section 2. son can access the platform, add, edit and view processes,
Overall, we address the following research questions: semantics in processes and meta-information collaboratively.
This collaborative manner supports among others also the
1. How can we model processes and publish them accord- exchange of processes. Thus people from the same domain
ing to the Linked Data principles? has access to these information at any time. Following this,
the entered information are available for querying and per-
2. How can we implement the infrastructure necessary for forming process analysis. The vision of the collaborative
storing, accessing, and processing processes and the platform is given in figure 1.
corresponding meta-information?
3. How can we introduce different views for entering meta-
information?
We show that our approach is easy to use and extensible
to capture multiple processes and semantic information, as
well as applicable to other domains (Section 2). The used
materials and methods are shown in section 3. The concrete
implementation of our approach is shown in section 4. Fur-
thermore, we show that our approach is sufficient to capture
processes and meta-information, and allow different views on
the entered information. For this purpose we will model a
perioperative process and enrich it with meta-information
from users that use different views (section 5). The evalu-
ation of the system includes showing the application of the
Linked Data principles on the modeled processes, demon- Figure 1: Vision of the collaborative platform. The
strating the functionality of the system and enable differ- collaborative platform consists of multiple stages,
ent views on the meta-information. A short discussion and which are interlinked by the knowledge base that
lessons learned is given in section 7. contains all available information. 1) Capture pro-
cesses: Processes are captured by using a process
2. MOTIVATION modeling tool, converted into a machine-readable
format and stored in the knowledge base. 2) Acquire
A major shortcoming of current process modeling lan- meta-information with different views: Provide pos-
guages is that they cannot capture semantic information. sibility to enter meta-information about processes
They concentrate on representing the structure of processes and its elements. Different views are provided to
but do not include specification of a formal semantic. This users, which are adapted to their specific fields of
is e.g. the case for the Business Process Model and Notation expertise. 3) Process Analysis: The entered pro-
(BPMN) [19]. cesses and meta-information are available according
Capturing processes and semantics is nowadays usually to the Linked Data principles. These information
done by multiple persons. Projects and workflows are cur- can be used in order to perform analysis like e.g
rently by no means proceeded in one place and by one per- similarity between processes.
son. The workflows of processes are usually defined collabo-
ratively, as well as the analysis of processes. Moreover, not We especially want to use the Linked Data principles5 to
only analysts are interested in process models but also peo-
4
ple who actually performing the processes as well as people http://www.omg.org/spec/BPMN/2.0/, visited 24 Jan-
uary 2016
3 5
https://www.w3.org/RDF/, visited 24 January 2016 http://www.w3.org/DesignIssues/LinkedData.html, vis-
publish process data. These principles are particular useful dition, we want to provide different views on same elements
for linking, exchanging and exploring information . so users are not overwhelmed with unnecessary information
Thereby, the platform will publish the entered informa- (section 3.3).
tion according to the Linked Data principles. Thus, unique
HTTP URIs will represent process elements. In addition,
the information provided by the platform will be available in
a standard, machine-readable format. This allows to query
the entered information for analyzing purposes. Entered in- 3.1 Infrastructure
formation includes meta-information as well as useful refer- The infrastructure to model and annotate processes, pro-
ences to external data sources like e.g. DBpedia6 , PubMed7 viding different views on entering data and publishing the
or Medscape8 . This allows to lookup further facts and in- entered data according to the Linked Data principles, con-
formation about entities and concepts, discover more things sists of multiple components. Figure 2 shows a high level
and connect the data from the collaborative platform with overview of the planned infrastructure.
other data to avoid of having an unbounded web.
Information about the hierarchy of flow objects and con-
necting objects can be modeled with the collaborative plat-
form. Meta-information like a responsible person for a spe-
cific task in a process, runtime, descriptions or references to
external data sources, can be added to an element. These
additional information, published according to the Linked
Data principles, can be queried and used for enhanced anal-
ysis and can i.e. allow improved comparisons between pro-
cesses [4].
The semantic information can be used to enhance analysis
and providing additional information to users. However, an
extensive provision of attributes that are shown to the users
may overrun them and is therefore not feasible, because it
prevents users more from entering meta-information instead
of supporting them. In addition, not every user can pro-
vide all meta-information or rather is interested in them.
Hence, we would like to introduce views on process meta-
information that is relevant and useful for the user. Thus,
the platform provides those meta-information to the user Figure 2: High level architecture of the system. It
that is relevant to him without overwhelming him. consists of three layers. Entry Layer: Users can en-
The information, provided by the platform, as well as the ter processes, as well as meta-information. Differ-
information from the referenced external data sources, al- ent views for users with specific field of expertise
lows performing analysis such as runtime analysis and simi- are provided in order to not overwhelming them
larity analysis of processes. By the variety of semantics and with unnecessary information. In addition, users
meta-information, provided by the platform and referenced can query the available information. Business layer:
from external data sources, are enhanced process analysis The platform takes care of entering processes and
feasible that were not possible before. meta-information, providing useful views to users,
query the data and publish them according to the
3. MATERIAL AND METHODS Linked Data principles. Data layer: The knowledge
base consists out of all available information like e.g.
Our approach is based on several components that are
references to external data sources, as well as the
part of a common collaborative platform that stores the data
entered processes and meta-information.
in a knowledge base. Section 3.1 describes the idea of the
collaborative platform that publishes information using the
The needed infrastructure has to ensure an efficient data
Linked Data principles in more detail.
input and exchange that follows the Linked Data princi-
The collaborative platform should provide a possibility to
ples. However, the data entry has to abstract from the pro-
model processes and reuse existing standards (section 3.2).
vision of standard formats like RDF. We have to consider
Thereby, we have to consider that modeling processes should
already available standard formats for process models like
be as simple as possible due to the fact that domain experts
e.g. BPMN 2.0 XML. Therefore, we need an infrastructure
will use the system and they may have no experience in using
that allows to model and enter data in different ways and
modeling tools.
formats and provide the entered information automatically
Besides modeling processes, we are interested in captur-
in a standard format like e.g. RDF.
ing meta-information. Therefore, we need an approach to
Users can enter processes and meta-information into the
capture these information from the domain experts. In ad-
collaborative platform. For entering meta-information, the
ited 24 January 2016 system provides different views according to roles that are
6
http://wiki.dbpedia.org, visited 24 January 2016 assigned to the user (see section 3.3). The entered data
7 should be available according to the Linked Data principles
http://www.ncbi.nlm.nih.gov/pubmed/, visited 24 Jan-
uary 2016 so accessing the unique identifiers returns information in a
8
http://www.medscape.com, visited 24 January 2016 standard format and it is possible to query the data.
The entered data will be stored in a knowledge base. The can enter all information they have and view all available
knowledge base consists of entered data, as well as linked information in the system, may deter them in using the sys-
data from external sources. Thus the knowledge stores mod- tem. Different views on the task for entering semantic in-
eled processes, meta-information about the modeled pro- formation allows to not overwhelm users with information
cesses and information from other data sources like e.g. DB- which they cannot know and do not need. Figure 3 illus-
pedia9 and PubMed10 that is referenced. trates the idea of providing different views.
3.2 Modeling Processes
There are multiple modeling languages available in order
to model processes. We would like to provide the possibility
in our platform to capture processes in multiple modeling
languages. Modeling languages are visual representations of
workflows and architectures. They define a structure how
different elements are linked. However, they do not store
semantic information.
Usually, domain experts are not familiar with semantic
technologies and with modeling processes. Therefore, we
have to provide a tool that allows domain expert to enter
processes in a very simple way. Most of the modeling lan-
guages are a graphical representation, therefore a graphical
user interface that allows to enter processes in a very simple
way is preferable.
There are already formats available in order to store pro- Figure 3: The system checks the assigned roles and
cesses like e.g. BPMN 2.0 XML11 proposed by OMG12 as displays only those information which are allowed by
standard format for BPMN or EPML that defines a XML the role. Only the attributes with a tick are shown
schema to store event-driven process chains [13]. The pro- to the user.
cess modeler should reuse such standards.
Reusing standards allows to import and export processes We would like to introduce roles into the system and as-
so that these processes do not have to be modeled from sign them to users. Each role contains information which
scratch. Therefore, the reuse of standards allows the flexi- attributes are interested by the user group and should be
ble exchange of modeled processes. Besides the import and displayed to the them. Hence, the system checks which roles
export functionality of processes, the modeler should also al- are assigned to the user and shows only these attributes to
low to add new processes into the platform and edit existing him.
processes. The relationship between users and roles follow a m : n
Processes can be described by using different process mod- relationship. So multiple roles can be assigned to one user
eling languages. Currently there are among others Busi- and different users may have same roles. According to the
ness Process Model and Notation (BPMN), Petri Nets and assigned roles, the user will only see specific information.
Event-driven process chain available to model processes. Each The different views can be used to offer the possibility to
process modeling language tackles a specific depiction of a secure information from unauthorized access. However, we
process. This circumstance of describing one workflow by will not focus on the security aspect but more on providing
using multiple process modeling languages should be sup- useful views for users.
ported by the collaborative platform. Hence, users can enter
processes using different modeling languages. 4. IMPLEMENTATION
We implemented our approach by using a use-case sce-
3.3 Annotating Processes with different Views nario from the medical domain. The medical domain is
Annotating processes with semantic information allows to very suitable for our approach, because in this domain are
use these information among others for analyzing purposes. many experts that can provide different information about
This can improve e.g. the comparison between processes same clinical pathways. Furthermore, clinics are interested
and allows to find biomarkers in processes that have not in clinical pathways from other clinics in order to improve
been known before. Biomarkers in processes are indicators their own clinical processes. Providing processes and meta-
that have significant influence on the output of a clinical information as Linked Data allows to exchange clinical path-
pathways. ways across clinics and link them to already existing infor-
However, different users have different perspectives on mation to discover more things. The implementation of the
same tasks. Therefore, they can only provide particular in- infrastructure for the collaborative platform is described in
formation and will probably only use specific information. section 4.1.
Forms allow a structured and easy input of semantic infor- The realization of how processes are modeled in the col-
mation for users. Providing one giant form, in which users laborative platform is shown in section 4.2. We focused on
9
http://wiki.dbpedia.org, visited 24 January 2016 BPMN as modeling language, however the approach can be
10
http://www.ncbi.nlm.nih.gov/pubmed/, visited 24 Jan- adapted in order to capture processes in other modeling lan-
uary 2016 guages like e.g. Event-driven process chain and Petri net.
11 We also allow to capture meta-information about the pro-
http://www.omg.org/spec/BPMN/2.0/, visited 24 Jan-
uary 2016 cess elements by providing forms. Users with different as-
12
http://www.omg.org, visited 24 January 2016 signed roles get different views on same forms, so they are
not overwhelm with redundant information (section 4.3). 4.1 Infrastructure
In order to allow users to create, edit and view processes
and process meta-information according to the Linked Data
principles collaboratively, we need a collaborative platform
that supports this feature. For this purpose we use Seman-
tic MediaWiki13 (SMW) as platform for modeling processes,
capturing meta-information and publishing these informa-
tion according to the Linked Data principles.
Semantic MediaWiki is a powerful collaborative knowl-
edge management system to store and query data. Data
resources, concepts and properties can be annotated inter-
nally, as well as linked to external data sources like e.g. DB-
pedia14 ). The possibility of linking concepts and proper-
ties enables the integration of well-known ontologies such
as Dublin Core15 and SNOMED16 . Each wiki page has its
own HTTP URI, provides its data in RDF and, if entered,
provides useful links to other data sources.
Hence, the information, stored in SMW, is available as
Linked Data on the web. We used existing tools and ex-
tended them in order to capture processes within SMW (sec-
tion 4.2) and capture meta-information by providing differ-
ent views (section 4.3).
Figure 4 illustrates the infrastructure for capturing pro-
cesses, annotating them by users that use different views on
same processes and query all available information in SMW
by using the RDF export functionality of SMW.
Figure 4: The infrastructure is a classical three tier
architecture. Presentation tier: User can enter and
view processes and meta-information with respect
to their assigned roles. In addition, an export func-
tionality is given by Semantic MediaWiki that allows
to export the information in RDF. Logic tier: The
process modeler allows to capture BPMN processes.
Each BPMN element is represented by a wiki page.
Semantic Forms allows to enter meta-information
using forms. Assigned roles to users allow to dis-
play different views on same forms. The SMW ex-
port functionality publishes the data according to
the Linked Data principles. Data tier: Stores all
entered information. In addition, references to ex-
ternal data sources allows to include additional in-
formation and ontologies.
13
https://www.semantic-mediawiki.org/wiki/Semantic
MediaWiki, visited 24 January 2016
14
http://wiki.dbpedia.org, visited 24 January 2016
15
http://dublincore.org, visited 24 January 2016
16
http://www.ihtsdo.org/snomed-ct, visited 24 January 2016
The Semantic MediaWiki offers an infrastructure that al- 4.3 Process Annotation
lows to capture information and link it to other data sources Once processes are captured, we would like to enrich them
in a very easy way. Flexible inputs and modifications of the with meta-information. For this purpose, we use Semantic
entered data is possible. Furthermore, SMW takes care of Forms21 , which is an extension to SMW that provides forms
publishing the data in RDF and according to the Linked for adding and editing data.
Data principles. Thus the entered processes and meta-information We use Semantic Forms to provide useful forms that help
is available in a structured way that can be used for analyz- users to annotate process elements. Multiple forms can be
ing purposes. created and used to annotate BPMN elements. The forms
can include information like Responsible Person, Goal, Con-
4.2 Process Modeler dition and links to Guidelines. These meta-information can
Currently SMW does not support graphical inputs of pro- be used to analyze processes and its elements. In addition
cess modeling languages. However, due to the fact that do- users can use these information to get a closer look on the
main experts will enter process models, we want to facilitate process and its tasks.
the input as much as possible by providing a graphical user We imported the FOAF Ontology22 and Dublin Core Schema23
interface for modeling processes. As modeling language we to model and describe the used properties. These properties
chose BPMN 2.0. are used in the forms to annotate the processes.
17
For modeling BPMN diagrams, we used bpmn-io as Forms can be arranged in a hierarchical model. So a
graphical user interface. bpmn-io is a graphical web mod- form can inherit attributes from a superclass. However,
eler, based on JavaScript that allows to view, create and the relationship between the superclass and its subclasses
edit BPMN 2.0 diagrams. It is part of the business process is 1 : n. Hence, a subclass does not inherit from multiple su-
management platform Camunda18 . perclasses, but a superclass can be used as a generalization
We extended bpmn-io with further functionality in order for multiple subclasses [18].
to embed it as process modeler in SMW. Each BPMN ele- We extended the functionality of Semantic Forms in or-
ment (nodes and edges) is represented by an own wiki page. der to provide different views on same forms. Therefore,
The wiki page contains all information about the BPMN ele- admins can assign attributes to roles in the local settings
ment like e.g. the type of the element, labels, comments and file of Semantic MediaWiki. Each role stores attributes that
entered semantic information by the user (see section 4.3). are allowed to be viewed by the user that has the assigned
bpmn-io allows to import processes in the standard for- role. Besides defining the roles, are the roles assigned to
mat BPMN 2.0 XML19 proposed by OMG20 . Thus existing users. As the default setting, each attribute in a created
processes that are available in BPMN 2.0 XML can directly form is allowed to be viewed for every user, independent
be imported via drag&drop into SMW using the process from assigned roles. However, if adding the attribute role
modeler. In addition, bpmn-io allows to export modeled with the value true into the div element of the form, are the
processes in BPMN 2.0 XML and as an image in Scalable assigned roles for the user checked.
Vector Graphics (SVG) format. Thereby, we support stan- This check is done by a JavaScript file. Users are only
dards and allow to reuse modeled processes. allowed to view attributes that are defined in the assigned
Besides the provided functionality from bpmn-io, we al- roles. Other attributes in the form are hidden. For this
low to reload already depicted BPMN diagrams from SMW purpose we use the hide functionality from jQuery24 . The
and allow to modify them. The following list describes the corresponding HTML form is then presented to the user with
mapping between the process modeler and SMW. hidden elements that he is not allowed to see.
The user uses these forms to enter additional information
• Create BPMN element: Creates a new wiki pages
about the process element into the Semantic MediaWiki.
that represents the BPMN element and allows to store
The entered information are stored on the corresponding
corresponding information of the element on this wiki
wiki page that represents the BPMN 2.0 element and is
page.
available according to the Linked Data principles.
• Edit BPMN element: The modification of a BPMN
element leads to modifications of information on the 5. EVALUATION
wiki page. Modification comprises among others shift-
ing the position of an element, reconnecting flow ele- We evaluated the system according to its functionality and
ments and defining labels and comments for a BPMN show the proof of concept. Therefore, we used an existing
element. process in the medical domain. We imported an existing
perioperative process that was modeled in BPMN 2.0 and
• Delete BPMN element: The deletion of a BPMN enriched it with meta-information. The meta-information
element leads to a deletion of the corresponding wiki are entered by two users that use the same form, however
page. with different views due to different assigned roles.
We successfully imported the perioperative process into
the Semantic MediaWiki. Figure 5 shows the graphical rep-
resentation of the process in the web modeler. Each element
in the BPMN 2.0 process is represented by a wiki page that
17 21
http://bpmn.io, visited 24 January 2016 https://www.mediawiki.org/wiki/Extension:Semantic
18 Forms
https://camunda.org, visited 24 January 2016
19 22
http://www.omg.org/spec/BPMN/2.0/, visited 24 Jan- http://www.foaf-project.org, visited 24 January 2016
23
uary 2016 http://dublincore.org, visited 24 January 2016
20 24
http://www.omg.org, visited 24 January 2016 https://jquery.com, visited 24 January 2016
stores the information about this element. for each user group a particular form but assigning roles to
them that hides specific parts of the forms.
With this approach we can create one giant form, instead
of multiple forms that may only differ slightly. However, by
using the roles, each user has a different view and perceive
the same forms in a different way.
All the entered information into the SMW, which includes
the perioperative process and the entered meta-information
is available in RDF. The information can be accessed and
queried by using the RDF export from SMW and is available
according to the Linked Data principles.
6. RELATED WORK
Figure 5: Imported perioperative process. Each el- Process modeling tools like Visio25 allow to model pro-
ement is represented by a wiki page that stores the cesses on a local machine. However,a collaborative creation
corresponding information. and maintenance of processes is not possible.
Collaborative modeling tools like Blueworks Live26 , BPMN
We use Semantic Forms to annotate the BPMN 2.0 ele- Modeler27 , jBPM28 and gluu29 provide a web-based solution
ments and allow users to enrich them with meta-information. in order to allow modeling processes collaboratively. In ad-
A role system allows to hide information from users that is dition these tools allow to import and export diagrams in
not relevant for them. To demonstrate the functionality, various formats. Although these tools support a collabo-
we assigned two different roles to two different users and rative modeling of tools, the captured information are not
called up the form to annotate the task for radiography in published according to the Linked Data principles.
the perioperative process. We called the roles physician and Flowchart30 is an extension for SMW that allows to model
radiologist. Figure 6 shows the different views for the same diagrams by using flowchart elements. Each flowchart ele-
form. ment is represented by a wiki page. Flowchart allows to
model e.g. event-driven process chains. However, a graph
can be displayed that shows the interlinks, it does not pro-
vide an interactive modeler. Modifications in the process
must be done directly on the wiki pages, using the wiki syn-
tax.
The modeling and capturing of information in a formal
representationm using a Semantic MediaWiki, were done be-
fore in other projects [6]. Thereby, Data Science data are
captured and provided in a structured way in order to use
them collaboratively. Complex projects in the architecture
often require a collaborative creation and exchange of build-
ing data. Therefore, theoretical framework exists to support
Figure 6: Different views on data with the same multi-disciplinary scenarios [15].
form. On the left is a view for a user that has the SPUD is an environment to catalog, explore and process
role physician assigned. He will e.g. not see with urban information based on semantic technologies and pub-
which device the CT were captured, because he may lish the data according to the Linked Data principles [11].
not be interested in it and he also may not know. It uses existing vocabularies for modeling the data. Static,
On the right is the same form shown for a user with as well as stream data is used to perform traffic diagnosis.
the role radiologist assigned. He can upload the CT Roles to restrict users from accessing specific data had
image, sees the attended physicians and used device been developed long time ago [2, 16, 8]. And since they are
for capturing the CT image. However, he does not used in various systems to provide specific views on data, as
see the habits of the patient. well as restrict users from unauthorized access.
Annotations are used in different scenarios like e.g. an-
notating television and radio news with semantic informa-
Although, users have different views on form, it is the tion [3]. The annotations are used to produce a higher qual-
same form. In some parts they can view the same informa- ity of descriptions of the news. The semantic information
tion like label and comment, but some attributes can only is used to improve conceptual search and browsing. Besides
be viewed by the radiologist like e.g. the used device to cap- annotating television and radio news, there is also a seman-
ture the X-ray image, which the doctor in charge might not tic approach to annotate raw mobility data with semantic
know and is also not relevant for him.
However, the attributes are only hidden in the form. The 25
http://visio.microsoft.com, visited 24 January 2016
information is still in the HTML code available but not pre- 26
https://www.blueworkslive.com, visited 24 January 2016
sented to the user. Our approach hides the attributes on the 27
http://www.trisotech.com/bpmn-modeler, visited 24 Jan-
client side and is therefore not suitable to prevent users from uary 2016
28
unauthorized access. For this case, a server side processing http://www.jbpm.org, visited 24 January 2016
29
of the information is more suitable. However, we focused http://www.gluu.biz, visited 24 January 2016
30
more on providing aligned forms for users without creating http://www.flowchartwiki.org, visited 24 January 2016
information [21]. Therefore, an annotation platform was cre- 8. REFERENCES
ated that supports the enrichment of the raw mobility data [1] Quality management systems - fundamentals and
with meta-information.
vocabulary (iso 9000:2015). European Committee for
Besides annotating data, there are also approaches avail- Standardization, September 2015.
able to annotate web services [10, 20]. SAWSDL31 is a
[2] C. W. Bachman and M. Daya. The role concept in
W3C recommendation to define how semantic annotations
data models. In Proceedings of the Third International
are added to WSDL documents. Annotating web services
Conference on Very Large Data Bases - Volume 3,
adds machine-readable descriptions on web services and thus
VLDB ’77, pages 464–476. VLDB Endowment, 1977.
allow a machine-to-machine interaction. Besides SAWSDL
there is also OWL-S available [5] to add semantic annota- [3] M. Dowman, V. Tablan, H. Cunningham, and
tions to web services. Ontologies were published to support B. Popov. Web-assisted annotation, semantic indexing
the standardization of web service descriptions [17]. and search of television and radio news. In Proceedings
of the 14th International Conference on World Wide
Web, WWW ’05, pages 225–234, New York, NY, USA,
7. CONCLUSIONS 2005. ACM.
We showed an approach to capture processes and anno- [4] M. Ehrig, A. Koschmider, and A. Oberweis. Measuring
tate them with meta-information by using a collaborative similarity between semantic business process models.
platform and providing different views for entering meta- In Proceedings of the Fourth Asia-Pacific Conference
information in order to not overwhelm users. The published on Comceptual Modelling - Volume 67, APCCM ’07,
information follows the Linked Data principles. pages 71–80, Darlinghurst, Australia, Australia, 2007.
SMW provides the basis for storing the data and publish- Australian Computer Society, Inc.
ing them according to the Linked Data principles. There- [5] T. A. Farrag, A. I. Saleh, and H. A. Ali. Toward swss
fore, the captured and annotated processes are available in a discovery: Mapping from wsdl to owl-s based on
machine-readable format that can be queried for analyzing ontology search and standardization engine. IEEE
purposes. Trans. on Knowl. and Data Eng., 25(5):1135–1147,
We used an existing modeler to model BPMN 2.0 dia- May 2013.
grams, extended it with further functionality and embedded [6] Y. Gil, F. Michel, V. Ratnakar, J. Read, M. Hauder,
it in SMW. Each element in the BPMN 2.0 diagrams is rep- C. Duffy, P. Hanson, and H. Dugan. Supporting open
resented by an own wiki page that stores the corresponding collaboration in science through explicit and linked
information. A modeler for modeling other diagrams like semantic description of processes. In F. Gandon,
e.g. event-driven process chain can be implemented with M. Sabou, H. Sack, C. d’Amato, P. Cudré-Mauroux,
the same approach as presented. and A. Zimmermann, editors, The Semantic Web.
Role based forms support the annotation of BPMN ele- Latest Advances and New Domains, volume 9088 of
ments so that redundant information is not shown to users Lecture Notes in Computer Science, pages 591–605.
that are not assigned to specific roles. The assigned roles fo- Springer International Publishing, 2015.
cus on not overwhelming users with unnecessary information
[7] D. Hindle and A. Yazbeck. Clinical pathways in 17
rather than on security purposes.
european union countries: a purposive survey.
We evaluated the system according to its working func-
Australian Health Review, 29(1):94–104, 2005.
tionality. We could import existing BPMN 2.0 XML dia-
grams, edit BPMN diagrams and enrich them with meta- [8] G. Kappel, P. Lang, S. Rausch-schott, and
W. Retschitzegger. Workflow management based on
information. The entered information is available in RDF
and follows the Linked Data principles. Different views on objects, rules, and roles. IEEE Bulletin of the
forms allow specific entry of data by users. Technical Committee on Data Engineering, 18:11–18,
Future work comprises among others the input of multi- 1995.
ple processes and corresponding meta-information in order [9] L. Kinsman, T. Rotter, E. James, P. Snow, and
to use these data for performing process similarity and anal- J. Willis. What is a clinical pathway? development of
ysis. The entered meta-information helps especially in using a definition to inform the debate. BMC Medicine,
them for comparing the processes on a semantic level. The 8(31), 2010.
consequent benefits helps to get new insights into processes [10] J. Kopecký, T. Vitvar, C. Bournez, and J. Farrell.
like e.g. clinical pathways in order to improve them. Sawsdl: Semantic annotations for wsdl and xml
In conclusion, we have taken a first step towards captur- schema. IEEE Internet Computing, 11(6):60–67, Nov.
ing, annotating and processing processes according to the 2007.
Linked Data principles that can be shared and used in order [11] S. Kotoulas, V. Lopez, R. Lloyd, M. L. Sbodio,
to analyze and refine processes collaboratively. Role based F. Lecue, M. Stephenson, E. Daly, V. Bicer,
forms allows specific views on the data that are particularly A. Gkoulalas-Divanis, G. D. Lorenzo, A. Schumann,
interesting for users with the assigned roles. and P. M. Aonghusa. Spud – semantic processing of
urban data. Web Semantics: Science, Services and
Agents on the World Wide Web, 24:11 – 17, 2014. The
Semantic Web Challenge 2012.
[12] K. Kris Vanhaecht, M. Bollmann, K. Bower,
C. Gallagher, A. Gardini, J. Guezo, U. Jansen,
R. Massoud, K. Moody, W. Sermeus, R. Zelm,
C. Whittle, A. M. Yazbeck, K. Zander, and
31
http://www.w3.org/TR/sawsdl, visited 24 January 2016 M. Panella. Prevalence and use of clinical pathways in
23 countries – an international survey by the european
pathway association. International Journal of Care
Coordination, 10(1):28–34, 2006.
[13] J. Mendling and M. Nüttgens. Epc markup language
(epml): An xml-based interchange format for
event-driven process chains (epc). Information Systems
and e-Business Management, 4(3):245–263, 2005.
[14] M. Panella, S. Marchisio, and F. Di Stanislao.
Reducing clinical variations with clinical pathways: do
pathways work? International Journal for Quality in
Health Care, 15(6):509–521, 2003.
[15] V. Singh, N. Gu, and X. Wang. A theoretical
framework of a bim-based multi-disciplinary
collaboration platform. Automation in Construction,
20(2):134 – 144, 2011. Building Information Modeling
and Changing Construction Practices.
[16] F. Steimann. The role data model revisited. Appl.
Ontol., 2(2):89–103, Apr. 2007.
[17] H. H. Wang, N. Gibbins, T. R. Payne, and
D. Redavid. A formal model of the semantic web
service ontology (wsmo). Information Systems,
37(1):33 – 60, 2012.
[18] T. Weller and M. Maleshkova. Towards a process
meta-model. In Proceedings of the second Karlsruhe
Service Summit Workshop - Advances in Service
Research, Karlsruhe, Germany, 2016. KIT Scientific
Publishing.
[19] P. Wong and J. Gibbons. A process semantics for
bpmn. In S. Liu, T. Maibaum, and K. Araki, editors,
Formal Methods and Software Engineering, volume
5256 of Lecture Notes in Computer Science, pages
355–374. Springer Berlin Heidelberg, 2008.
[20] H. N. Yadav and R. V. Patel. Dbpedia based sawsdl
for semantic web services. In Computing for
Sustainable Global Development (INDIACom), pages
35–39. IEEE, 2015.
[21] Z. Yan, D. Chakraborty, C. Parent, S. Spaccapietra,
and K. Aberer. Semantic trajectories: Mobility data
computation and annotation. ACM Trans. Intell. Syst.
Technol., 4(3):49:1–49:38, July 2013.
[22] K. Zander. Integrated care pathways: eleven
international trends. International Journal of Care
Coordination, 6(3):101–107, 2002.