e-SENS kick-off meeting, Berlin, 10 April 2013

ISA Programme

Action 1.1 - Semantic Interoperability Stijn.Goedertier@pwc.be

How the ISA Programme can help build consensus on semantic interoperability

Agenda

0. About the ISA Programme 1. Document reusable building blocks with ADMS 2. Re-use the Core Vocabularies 3. Re-use ISA’s frameworks, tools, and services

ISA undertakes initiatives to foster interoperability of information exchanges by public administrations

What is interoperability? Ability of disparate organisations to interact towards mutually beneficial and agreed goals, involving the sharing of information and knowledge

• Aligned legislation Legal interoperability

• Coordinated processes Organisational Interoperability

• Precise meaning of information Semantic Interoperability

• Technical linking of systems Technical Interoperability

Political context

The EIF defines 4 interoperability layers

ISA Programme Action 1.1: semantic interoperability

Raise awareness: organise conferences, workshops, news items, events, ...

Encourage reuse: make collections of re-usable assets searchable on Joinup.

Exploit opportunities for semantic alignment: build consensus on core vocabularies.

Provide insight into frameworks and methodologies: conduct case studies and pilot implementations.

1

2

3

4

Collaboration between ISA Action 1.1 and e-SENS WP6.2

• Period: April 2013 – June 2013

• Possible areas of collaboration:

1. 1. Document reusable building blocks with ADMS.

2. 2. Re-use the Core Vocabularies.

3. 3. Re-use ISA’s frameworks, tools, and services.

Agenda

0. About the ISA Programme 1. Document reusable building blocks with ADMS 2. Re-use the Core Vocabularies 3. Re-use ISA’s frameworks, tools, and services

★ Applicability eGov interoperability, re-use, compatibility,...

★ Maturity Development status, quality, stability, ...

★ Openness Creation and change process, availability, ...

★ IPR Documented, FRAND or royalty free.

★ Market support Implementations, users, ...

★ Potential Impact, risks, maintenance, ...

What is needed to make an asset re-usable?

Creating optimal conditions for re-use.

Benefits of reuse Cost savings Coherent Architecture Interoperability

Common Assessment Method of Standards and Specifications (CAMSS)

Possible building blocks for the LSPs

• e-CODEX’ Data Model Governance

• ePSOS’ Master Value Set Catalogue

• PEPPOL’s/SPOCS’ Virtual Company Dossier

• SPOCS’ Omnifarious Container format

• STORK’s Technical Design

• STORK ‘s Integration Packages

• CIPA e-Delivery

• ETSI Rem

• OASIS BDX TC BusDoX Specifications

What can be re-used?

Asset Description Metadata Schema (ADMS)

• Re-usable building blocks = re-usable interoperability assets.

• Describe e-SENS building blocks only once with the ADMS vocabulary and publish them everywhere.

• Escape the data jail.

Describe your interoperability assets with ADMS

https://joinup.ec.europa.eu/asset/adms/description

Share your collection of re-usable interoperability assets with Joinup

The Joinup Team will help you identify the best way to describe your assets with ADMS.

Describe your assets using the ADMS and export them into an RDF file.

Propose a federated repository on Joinup, and upload the ADMS RDF file or configure a harvest URL.

1 Contact the Joinup team

2 Describe your assets using ADMS

3 Import your descriptions on Joinup

https://joinup.ec.europa.eu/community/cesar/description

Find reusable interoperability assets on Joinup

https://joinup.ec.europa.eu/catalogue/all

Refine the search results via the faceted search filters.

Enter a search keyword to find interoperability assets available on different websites.

The search results contain a relevant description of the assets and the link from where they can be downloaded.

2

1

3

1500 interoperability assets

20 partner organisations

EFIR: European Federated Interoperability Repository

• Extend ADMS towards other interoperability layers

• Participate in our Webinar on 24 April

https://joinup.ec.europa.eu/node/64526

Agenda

0. About the ISA Programme 1. Document reusable building blocks with ADMS 2. Re-use the Core Vocabularies 3. Re-use ISA’s frameworks, methodologies, tools, and services

• Recommendation 12. Public administrations, when working to establish European public services, should develop interfaces to authentic sources and align them at semantic and technical level.

European Interoperability Framework

Core vocabularies

Simplified, re-usable, and extensible data models that capture the fundamental characteristics of a data entity in a context-neutral fashion.

CORE

VOCABULARY

PUBLICSERVICE

Process and Methodology for Developing Core Vocabularies https://joinup.ec.europa.eu/node/43160

Process and Methodology for developing core vocabularies

• More than 60 WG members

• 21 EU Member States

• Many international experts

• Public review period

https://joinup.ec.europa.eu/node/43160

Consensus building

Core vocabularies

RDF schema

Re-uses existing Linked Data vocabularies

ISA Open Metadata Licence v1.1

Re-uses Core Components Technical Specification (CCTS).

XML schema

Concept model

Re-use existing concepts in CCL, INSPIRE, etc.

3 representation formats

Maintained by W3C (Government Linked Data Working Group)

Core Person Vocabulary

• Basic properties for a person.

• Re-used by e-CODEX.

Core Person Vocabulary

https://joinup.ec.europa.eu/asset/core_person/description

Registered Organisation Vocabulary

• Renamed by W3C GLD into “Registered Organisation” (specialises the ORG ontology).

• Good basic company data for everyone (URI, legal identifier, name, company type, activities).

• Informs DG Markt – interconnecting business registers (Directive 2012/17/EU).

Core Business Vocabulary

https://joinup.ec.europa.eu/asset/core_business/description

Core public service vocabulary

Bridge the gap between the supply and demand of electronic public services.

Describe public services “only once” using a standard vocabulary and make them searchable on many governmental Access Portals.

Participate in our pilot (as simple as filling in a spreadsheet).

Core Public Service Vocabulary

https://joinup.ec.europa.eu/asset/core_public_service/description

Core Location Vocabulary

• Subset of the INSPIRE address specification.

• A linked data service can be implemented on top of an INSPIRE representation.

• Address notation.

• Taken on board by the W3C location and address community.

Core Location Vocabulary

Today address data is fragmented across

various registers

Core Location Vocabulary

Core Location Pilot: https://joinup.ec.europa.eu/node/63242

Data fragmentation

Heterogeneous data formats

Lack of common identifiers

Unlinked Low quality

Non-interoperable

UrBIS - Brussels

Capital Region

CRAB - Flanders PICC - Wallonia Civil register NGI – National

Geographic Institute

DATA CONSUMER

?

The pilot demonstrates

interconnection of base address

registers

Core Location Vocabulary

Core Location Pilot: https://joinup.ec.europa.eu/node/63242

LOGD INFRASTRUCTURE

UrBIS - Brussels

Capital Region

CRAB - Flanders PICC - Wallonia Civil register NGI – National

Geographic Institute

DATA CONSUMER

sample address data in native format

Linked address data

Common Data models

RDF

Repository

SPARQL endpoint

Address

Identifier

Address

Notation

Link

Look up

Disambiguate

DATA CONSUMER ORIENTED

USE CASES

INS

PIR

E

lookup, disambiguate, link

Agenda

0. About the ISA Programme 1. Document reusable building blocks with ADMS 2. Re-use the Core Vocabularies 3. Re-use ISA’s frameworks, tools, and services

• The Joinup Licensing Framework establishes a system for:

• 1. the co-creation of assets on the Joinup platform, the ISA Contributor Agreement v1.1, and

• 2. a licensing model, the ISA Open Metadata Licence v1.1.

Joinup Licensing Framework

What can be re-used?

http://joinup.ec.europa.eu/node/45058

Process and Methodology for reaching semantic agreements

What can be re-used?

Process

Methodology

Agree on the selected Use Cases

Identify data entities and

sources

Compare existing

description models

Develop a Shared Data

Model (at least 2 iterations)

Implement Shared Data

Model

Assign roles and responsibilities

Establish a subgroup

Create and review drafts

(at least 2 iterations)

Reach agreement on a Shared Data

Model

Endorsement of the Shared Data Model

https://joinup.ec.europa.eu/node/61062

http://education.data.gov.uk/doc/schools/123456.csv

e.g. http://education.data.gov.uk/doc/school?id=123456

e.g. http://education.data.gov.uk/doc/school/v01/123456

e.g. http://education.data.gov.uk/ministryofeducation/id/school/123456

Follow the pattern

Re-use existing identifiers

Link multiple representations

Implement 303 redirects for

real-world objects

Use a dedicated service

Avoid stating ownership

Avoid version numbers

Avoid using auto-increment

Avoid query strings

10 rulesfor persistent

Avoid file extensions

e.g. http://{domain}/{type}/{concept}/{reference}

e.g. http://education.data.gov.uk/id/school/123456

e.g. http://data.example.org/doc/foo/bar.html

e.g. http://data.example.org/doc/foo/bar.rdf

i.e. independent of the data originator

e.g. data.gov.uk and publications.europa.eu are decoupled from

specific government department and could readily be transferred and run by someone else if necessary.

e.g. http://education.data.gov.uk/id/school1/123456

e.g. http://education.data.gov.uk/id/school1/123457

URIs

Common Web identifiers for basic data

https://joinup.ec.europa.eu/node/53858

Use Joinup as a collaborative work environment

Joinup provides wikis, news items, events, mailman mailing lists, subversion, WebDav, signing of contributor agreements,etc.

What can be re-used?

https://joinup.ec.europa.eu/page/our_services

Join SEMIC group on LinkedIn

Follow @SEMICeu on Twitter

Join SEMIC community on Joinup

Project Officers: Vassilios.Peristeras@ec.europa.eu

Szabolcs.Szekacs@ec.europa.eu

Contractors: Joao.Frade@pwc.be, Stijn.Goedertier@pwc.be

Get involved Visit our initiatives

SOFTWARE

FORGESCOMMUNITY

ADMS.

SW

CORE

VOCABULARY

PUBLICSERVICE