sebastian sklarß ]init[ ag für digitale kommunikation semantic interoperability centre europe -...

Semantic Interoperability Centre Europe - ECOTerm Meeting - 2009-10-05 - Rome - Italy - Sebastian.Sklarss@init.de

Sebastian Sklarß

]init[ AG für digitale Kommunikation

SEMIC.EU – Semantic Interoperability Centre Europe

Reusing and Sharing of Semantic Interoperability Assets

1. Semantic challenges and solutions

2. 180 seconds – SEMIC.EU overview

3. SEMIC.EU Communities – first experiences

4. Next steps – Closer Collaboration

SEMIC.EU – what is it?

SEMIC.EU stands for Semantic Interoperability Center Europe

Open platform as a single point of contact and information for semantic interoperability in Europe

Collaborative tool permitting the sharing and reuse of semantic assets between European public administrations

Service Center for European administrations and eGovernment projects

Sustainable Service of the IDABC follow-up programme ISA scheduled for 2010 – 2015

Why should interoperability be examined?

Data exchange between different systems has to assure technical, syntactic and semantic interoperability

Information

Signals

Organisation A

Information

Signals

Organisation A

Information

Signals

Organisation B

Information

Signals

Information

Signals

Organisation B

Technical Interoperability

Syntactic Interoperability

Semantic Interoperability

Information

Signals

Organisation A

Information

Signals

Organisation A

Information

Signals

Information

Signals

Organisation B

Information

Signals

Information

Signals

Organisation B

Just an address . . .

Beethovenallee 66 a

1010 Vienna

GKZ 0345345

Beethovenallee 66PLZ: 1010

Beethovenallee 66Vienna

Beethovenallee

GKZ: 0345345

. . . but what really is the right one?

The exchange of address data . . .

Addresse Strasse Hausnummer Stiege Türnummer Postleitzahl Wohnort

Addresse County Street House number Village City

Addresse Strasse Hausnummer Hausnummerbuchstabe

Zusatzziffer Teilnummer der Hausnummer Stockwerkswohnungsnummer Adressierungszusätze Postleitzahl Wohnort Zusatzangaben

. . . what really is a House number?

1. Do you really get the information required?

Customers address ≠ Delivery address?

2. What about granularity of data?

Street and House number ≠ Street & No.

Delivery address

name Street City

Hilton International

Brussels

Address

name Address City

Boulevard Jamar 11

Further aspects . . .

Customers address

name Street City

Hilton International Brussels

Address

name Street No. City

Boulevard Jamar 11

4. Implicit knowledge has to become explicit

Brussels is a city of Belgium

Address

name Street City

Brussels

3. Data interchange has to solve questions of spelling

Brüssel ≠ Brussels

. . . how to integrate these information?

Address

name Street City

Brüssel

Address

name Street No. City

Brussels

Address

name Street City Contry

Brussels Belgium

6. Data exchange and Data typ conflicts

Postcode in incompatible formats

5. How to handle different nomenclatures and classification systems?

How do you migrate a three-thier to a five-tier classification system?

Further questions of information integration

Address

Hotel category

Hilton City Hotel A / B / C

Address

Hotel category

Hilton City Hotel

Address

name Street City Postcode

Brussels Char (5)

Address

name Street City Postcode

Brussels Integer

Typical problems of semantic interoperability

Typical syntactic problems Typical semantic problems

Identifier conflicts Scaling conflicts

Data typ conflicts Representation conflicts

Conflicts due to assymetrical or

missing information

Conflicts to different aggregation

levels

Conflicts of multilingualism Conflicts of incompatibility

Hands on examples of semantic conflicts

ISO Codelist issues

ISO 3166 Country CodesGermany needs historical values (GDR)

Important issues for eGovernment country code lists:

a) who is maintaining agency?

b) what is the update frequency?

c) how to deal with historical data?

d) what to do with plurality (ex. Kosovo) ?

e) What to do with redefined values?

ISO 639-3/2/1 Codelist issues

ISO Language Code List -> need for Venetian as language

Additional 639-3 Codes:

als ---> Tosk Albanian (the one you found already) frp ---> Franco-Provençal ksh ---> Kölsch lmo ---> Lombard nrm ---> Narom pih ---> Pitcairn-Norfolk pms ---> Piemontese rmy ---> Vlax Romani rup ---> Macedo Romanian vec ---> Venetian vls ---> Vlaams

ISO Codelists issues

ISO 4217 currency names

Albanian Lek encoded as „ALL“ poses

some “reserved keyword” problems on

some databases

Authority Tables / code lists / taxonomies

1. „semantic waste tourism“ -> old batteries turning into valuable source of energy due to re-declaration by import/export in MS

2. UK driver‘s licence register uses gender to constitute UID -> new person when changing gender

Someone‘s Bee may be another‘s Reindeer

NACE-Code 01.49.1

EMTAK (Estonia):Bee keeping

SNI 2007 (Sweden):Reindeer husbandry

CZ-NACE (Czech Republic):Raising of small livestock

ATECO (Italy):Breeding rabbits

SK-NACE (Slovakia):Raising of farmed animals

NACE-Code 01.49:Raising of other animals

Unity conflicts

1991 - Mars-Klima-Orbiter of NASA was destroyed (125 Mio. US $) caused by unity conflicts (miles and kilometers)

Bridge in Denmark -> Nordic Zero (Baltic Sea or North Sea?)

Mapping of a persons language

German Ministry I

Person attribute: Language, Level of language

German Ministry II

Person attribute: Mothertongue, Foreign Language

French scaling conflict in “Nom Famille” of FR_Person

French family name: Ministry of Justice (30 chars) vs. Ministry of the Interior (60 chars) vs. INSEE (80 chars)

<<ASCC>>

A lias

<<ASCC>>

Filiation

<<ASCC>> Evenement

1 * FR_ Evenement<<ACC>>

FR_ Personne<<ACC>>

<<BCC>> Situation Familiale [0..1] : Code<<BCC>> Titre[* ] : Texte<<BCC>> Civilite [0..1] : Code<<BCC>> Sexe [0..1] : Code<<BCC>> Prenom Usuel [0..1] : Texte

<<BCC>> Prenom[* ] : Texte<<BCC>> Surnom[* ] : Texte<<BCC>> Pseudonyme[* ] : Texte<<BCC>> Nom Usage [0..1] : Texte<<BCC>> Nom Famille [0..1] : Texte<<BCC>> Identifiant[* ] : I dentifiant

Back to SEMIC.EU

SEMIC.EU – Scope

ServicesCoaching, consulting and support to develop Interoperability Assets

Collaboration Exchange with domain experts on relevant questions within pan-European data exchange

Online Platform Communication platform and repository for interoperability assets

SEMIC.EU competence network – partner projects

SEMIC.EU competence network – partner initiatives

SEMIC.EU platform

Visibility

Collaboration

Asset Repository

Network of eGovernment

Clearing Service

Clearing Process SEMIC.EU Repository

Registration

Maturity

Conformance

Semantic Assets

Why contribute to SEMIC.EU?Perspective of the e-Justice Community

Scope of eJustice Community eJustice is a growing network of judicial data interchange in

Europe

Issues of eJustice Community Judicial Registers (NJR) Insolvency registers Commercial register portal Land Registers

First Step – Network of Judicial Registers „one by one“

Total number of bilateral interfaces between 27 member states: 702

03/03: France and Germany 11/03: Spain 11/04: Belgium 03/06: Czech Republik 10/06: Luxembourg 06/07: Slovakia, United Kingdom 07/07 Poland, Slovenia, Italy 12/07: Portugal

Network of Judicial Registers (NJR):

For just one administrative procedure!

Never again!

The Idea – Using SEMIC.EU services

1. Coaching – Asset development

2. Clearing – Asset improvement

3. Reusing – Asset integrationAsset

SEMIC.EU Support Enable semantic interoperability

The process – Implementation of Interoperability

1. Coordination of the first movers

2. Methodical validation of the asset concept

3. Roll out in various Member StatesAsse

SEMIC.EU Coaching Services for Communities

The general Concept of Reuse

Searching the repository of www.semic.eu

Finding, evaluating, modifying

Asset Asset

Closer Collaborate

Visit www.semic.eu

Get registered in the SEMIC.EU competence network (User, Project)

Publish your assets

Give comments on assets and published eGovernment projects

Help to improve quality

Inform us about your activities

Sebastian Sklarß

]init[ AG für digitale Kommunikation

Thank you for your attention!

sebastian sklarß ]init[ ag für digitale kommunikation semantic interoperability centre europe -...

semantic challenges

rome italy

reuse of semantic assets

exchange of address

vlaams slide

missing information

europe collaborative

city boulevard jamar11

Documents

medier og kommunikation

tagungsbroschüre interne kommunikation

oracle startup parameters init initialization pfile init

strategisk kommunikation 2

ecoterm iv nbii/eionet demo of federated kos search

gas detector teta ecoterm / teta ecoh

fra tekstuel kommunikation til visuel kommunikation på...

primetime kommunikation

webmaker init()

booker finncap init

zusammenarbeit & kommunikation

interkulturel kommunikation

kernel init

compliance kommunikation 2014

init() day 4

init schemes 0706.2748v2

fh-wiesbaden / marketing prof. dr. klaus brüne...

ecoterm berlin, april 2005 gilw/fao margherita.sini@fao

early delta init

reading init param