Terregov Interoperability platform and Open Source Tools

1
Terregov Interoperability platformand Open
Source Tools
BFC Emmanuel Orain
2
The TERREGOV project

• - European project IST FP6
• 15 partners (France, England, Spain, Italy,
  Greece, Poland, Belgium, and Israel)
• Industry
• Academics
• Administration
• 4 years from Jan.2004 to Dec. 2007
• Pilot domain social help
• started with 4 pilots in Europe France,
  England, Italy, Poland

3
TERREGOVs purpose
Provide territorial collectivities, such as
regions or smaller  départements  in Europe,
with a platform and tools enabling them to offer
proximity services to citizen, and to exchange
information between administrations. The purpose
of this platform is to - simplify the
management of complex procedures involving
territorial collectivities, distributed
state-level services, or non-governmental
organizations. - help users (civil servants) in
obtaining and share information about these
procedures
4
TERREGOV as a Platform

• Terregov a Regional Interoperability Centre,
  providing a complete infrastructure allowing
  local entities to participate

Regional Centre (city, inter-city, country, )
State services
Local entity
Local entity
Local entity
Local entity
5
TERREGOV A complete platform

• Terregov a Regional Interoperability Centre,
  providing a complete infrastructure allowing
  local entities to participate

TERREGOV Interoperability Centre Centralized
resources Semantic Registry, eProcedure engine,
document indexing and searching, reference
ontology Dowloadable tools tools and
libraries for local entities
TERREGOV Infra-structure
HTTP SOAP
Local entity
Local entity
Local entity
Local entity
TERREGOV tools and libraries for local entities
Interoperability layer
Terregov Web Service
 classic  Web Service
TERREGOV tools
Legacy system
TERREGOV technology
Legacy systems
Legend 
6
TERREGOV - Technical approach

• Interoperability rather than integration
• Respect of legacy systems
• Technical independence of local entities
• Security
• Data encryption and authentication
• Non-circulation of private citizen data
• eProcedure monitoring
• User support
• Document access, indexing and search engine
• Semantics

7
Providing services
Each local entity creates its own services, and
opens them for Terregov use
Web Service S1
Web Service S2
Local entity
Terregov interoperability layer
Web Service S3
Existing or internal Web Service
Internal system
8
Advertising a service
Each local entity registers its services within
the platform(s)
Regional Centre
Semantic Registry
Ontology

• S12 is a new service
• Input
• Output
• Category
• Location

Service Web S12
Local entity
Semantic binder
9
eProcedure and services
An eProcedure makes use of entity services
Regional Centre
eProcedures storage
Registry
eProcedure engine
Web Service
Web Service
Web Service
Web Service
Web Service
Local entity
Local entity
Local entity
10
Terregov various entity levels
Level 3 Online Services Centre Registries,
eProcedure engine, ontologies, CoP, Knowledge
support,Certificate Authority
Level 2 owns eProcedures eProcedure engine
(opt.)
Level 1 takes part in eProcedures Mainly
intra-agency modules
Level 0 pure Web access Nothing to install
11
Centralized control flow

• Distributed procedure vs. Centralized procedure
  separating task and control

Start
Entity A
Entity A
1
Start
1
2
3
Entity B
Entity B
eProcedure engine
4
2
5
Entity C
Entity C
6
Finish
Finish
12
TERREGOV is not
Data privacy

• Data cant travel through a third party
• Allow precise control about who accesses which
  data

Entity A
Entity A
1- PREPARE DATA !
1- GET DATA
3- GET DATA
Entity B
Entity B
2- USE DATA
2- GET AND USE DATA !
13
TERREGOV is not
Terregov is not a centralized data storage
platform Even though Terregov provide support
for exchanging information between entities, this
information remains the property of each
entity, and under its own responsibility
14
TERREGOV as a Tool Box

• In addition to a platform approach , some
  Terregov components are independently reusable
• Semantic Registry
• Community of Practice semantic document
  indexing and sear
• ... and most of these tools are available as part
  of the Terregov Open Source Initiative

15
Semantics in TERREGOV

• Documents
• Indexing and searching, with support of concepts
• Service (and eProcedure) description, using
  OWL-S
• Category
• Inputs/outputs
• any additional information

16
Semantics and eProcedures
Possibility to use a semantic description of a
service in an eProcedure
17
Semantics and eProcedures
Benefit from automatic semantic composition of
services
1) Req a service which takes i1 and returns o1
Semantic Registry
Ontology rules
OWL-S
2) Direct search, no result
4) Found i1-gtS10-gtx,y-gtS12-gto1
3) Try composition
Composer
18
TERREGOV and Open Source

• Open Source Web Site http//terregov-oss.eupm.ne
  t/
• Description of the project
• Availability of most software components
• Support for ontology life cycle
• Contact point to receive feedback

19
Some lessons

• The Open Source Initiative revealed a crucial
  issue through documentation
• more elements to document than for a closed
  source project,
• all documentation is gathered in one structured
  place, which make inconsistencies obvious
• documentation templates and guidelines are not
  enough
• any lack of sense of the project among
  partners is showing
• -gt Documentation requires a central authority