1. WP3: Design of Semantic Web Service Architecture for National
and Pan-European e-Government services
WP5: Development of SWS Execution Environment for National
and Pan-European e-Government Services
WP6: Development of the SemanticGov Showcases
WP7: Integration, Testing and Operation
2nd Review Meeting, 9 April 2008
Brussels, Belgium
www.semantic-gov.org

2. Presentation Overview
Why this way of presenting the work packages?
WP3/5/6/7 overview
Structure of the presentation
2

3. Presentation Overview
Why combined presentation?
Scenario-based and citizen-centric development
It makes the presentation more comprehensible and interesting
It saves us time to demonstrate the great work that has been done in
developing prototypes and showcases
3

4. WP3 finished with
the final version of
the Architecture
WP4 finished with
the final version of
the Ontologies
WP5 finished with
the final version of
the tools
WP6 is in progress
without a
deliverable due yet
WP7 has officially started
in February but we started
the work earlier
4

5. Presentation Overview
Structure of the presentation
Scenario overview
Detailed scenarios presentation with tools discussion and demos
Conclusion – Next Steps
5

6. Scenario
The City of Turin is located in the Piedmont Region in the NW
part of Italy
The “Change of Residence” service is asked by a European
foreign citizen. The effect of this service is that the foreigner
will be registered in the population registries and will have
access to a number of services and can participate in local
elections
The foreign citizen presents his ID info and the additional
required information are retrieved/verified wrt. the registries of
the originating MS. The necessary semantic transpositions are
made when presenting this information to the civil servants of
the CoT registry office
In our showcase, we present a Belgian citizen who has moved
with his family to a new address in the City of Turin and wants
to register his new address
6

7. The SemanticGov Solution
But in order to run all this
story, we need previous
design work of service
engineers of the involved
1. discovery PAs … SemanticGOV offers
2. actual service to a toolkit
be executed
3. service
execution 3.x orchestration and
mediation of
component services
Italian MSA
portal and middleware
Belgian MSA
middleware
Belgian Registry
7

8. Scenario(s)
1. A service engineer in Turin has already working WSDL web
services. How is it possible to make them “Semantic”?
2. He wants to set up a new service for the change of residence of
a Belgian citizen who wants to move from Brussels to Turin
3. The Belgian citizen searches & discovers the service, and then
invokes it
8

9. WSMO Studio
First of all the service engineer has to define the domain
ontology which represents the formalization of concepts
belonging to the administrative domain
… today I’ve to develop the domain
ontology that I will use to implement
the PA service…
So, I have to define the concepts of
citizen, address, city … some important
relationships between these concepts and
some axioms
9

10. Defining a PA service
The second step consists of building the PA service
defining capabilities, pre/post conditions,
choreography…
Inside WSMO Studio the PA service Editor can
help me to define PA services following the
WSMO-PA specifications hiding the complexity of
the underlying conceptual model
10

11. SWSCE
We will show how existing PA services, can be
composed automatically, in order to quickly develop a
new one
…I have only to declare the capability and
the choreography of the desiderata
service. SWSCE will tell me if the
composition exist!
I can define the
ItalianChangeResidence service
11

12. WSMT – Ontology Mapping Tool
Consider now the case where different public
administrations export their services and the service
engineer has composed some of them. The mediation
problem may arise!
... mmm is it possible to orchestrate PA
services belonging to different public
administrations!?!?
I will solve this problem by defining
mediators using WSMT
As result of the composition, I’ve obtained the
structure of the orchestration definition.
Now I have to define mediators!!!
12

13. GoalTree
Now we will show how to create a GoalTree used by the
SemanticGov Portal in order to identify the exact service
that the citizen has to execute in order to get the desired
results
Now I want to make available the “change of
residence” service to European citizens. The
GoalTree editor will help me to define the right
questions to identify the PA Service suitable
for the citizens’ needs.
13

14. Registry-Repository
During evolution of the whole scenario the service
engineer wants to extend or modify the existing
configuration
Now I want to check which (composite)
semantic web services are using a given
WSDL web service
14

15. Portal
The citizen has to connect to the Portal and through
questions he is driven towards his goal
… I am searching for a service for the
change of residence …
15

16. Orchestration and Mediation
After discovering the right service, the citizen starts
interacting with it. In turn this service orchestrates the
underlying services, mediating the data when needed
… City of Turin is very efficient … only
one service instead of requiring me to
interact with many fragmented ones,
acting as humanware …
16

17. Presentation Overview
Structure of the presentation
Scenario overview
Detailed scenario presentation with tools discussion and demos
Conclusion – Next Steps
17

18. Global View of the SemanticGov Architecture
(1)
(2)
(3) (4) (5)
(6)
18

19. Development Methodology
Overview
WP1: Overall conceptual WP2: Requirement Analysis
analysis for NEGS & PEGS Conceptual Design Phase (requirements
analysis)
WP3: Design of National and European Semantic Conceptual/Technical Design Phase
Web Services Architecture
WP5: Development of SWS Execution
Environment For NEGS & PEGS Technical/Implementation Phase
19

20. Development Methodology
Dependencies (technology, existing know-how and concepts)
WP4: PA Domain Ontology
PA WSMO
Service Model Service Model
WSMO-PA
Architecture DERI ,Software AG, UniRoma
from WP2 (SEE (WSMX Ontotext technology
SemanticGov
Architecture WP3: SemanticGov
Architecture
20

21. Underlying Principles
Service Oriented Principle
Services: middleware services and PA services (business
services)
Semantic Principle
Semantic description of business services
Problem Solving Principle
Separation of user goal and the service
21

22. Used Technologies
Semantics-related (research) technology
WSMO4J and WSMO API
WSML2Reasoner, IRIS Reasoner
ORDI, SPARQL
Other technologies
Java SDK 1.6
Liferay portal, JSF
AXIS, JMX
CentraSite, JXTA 2.5 libraries
Eclipse3.3
22

23. SemanticGov Architecture and its
Components
Mapping
GTEditor Editor
Portal
PA Compos. Reg.Rep
Editor Editor Access
(1)
Discov.
(2)
(3) (4) (5)
Orchestr. Mediation
(6)
Distributed
Reg.Rep
23

24. Live
The SemanticGov Solution demos on
request
Compos.
GTEditor Editor
Portal PA Mapping
Discov. Editor Editor
1. discovery
2. actual service to
Reg.Rep
be executed Access
3. service execution
3.x orchestration and
Orchestr. mediation of
Mediation
component services
Italian MSA
portal and middleware
Belgian MSA
middleware
Reg.Rep Distributed
Access Reg.Rep
Run Design Belgian Registry
time time
24