Workshop

Community of Practice on Core Data ModelsRiga, 6 May 2015

1

WorkshopAgenda

Start Topic

08:30 Registration & Coffee

09:00 Introduction to the Community of Practice

09:15 Setting the scene

10:00 Lightning talks from the participants

11:30 Discussion and next steps

12:30 Lunch break

14:00 The Core Public Service Vocabulary Application Profile (CPSV-AP)

14:50 Conclusion

09:00 Introduction to the Community of Practice

2

Introduction to the Community of Practice

3

A network of representatives from (or workingfor) public administration organisations aiming to:

• Share knowledge, experiences and lessons-learnt on core data models and reference data

• Harmonise existing initiatives

• Develop together guidelines for core datamodels and reference data

Community of PracticeScope

4

• Share good practices and lessons-learned

• Increase the visibility of existing initiatives,and provide an entry point of expertise andknowledge

• Promote and support the implementation of coredata models

• Identify opportunities for alignment andstandardisation

• Define together areas of future collaboration inISA Action 1.1

Community of PracticeMission

5

21 participants from 13 countries i.e. Austria, Belgium, Denmark, Estonia,Finland, Germany, Japan, Latvia, Malta, Netherlands, Spain, Sweden, USA

Scope

• Promote the use of base registers and the “once only” principle

• Facilitate the exchange of information across organisations andborders

• Coordinate development efforts

Lessons learned

• The work requires specialised skills, employment of methodologiesand sharing look for advice

• The evolution from existing architectures is not always easy

• ROI is hard to demonstrate

Community of PracticeWorkshop, Nov 2014

6

10 participants from 8 countries i.e. Austria, Belgium, Japan, Latvia, Malta,Netherlands, Spain, Sweden

Scope

• Report on news and updates from the participating countries and the EC since the meeting of Nov 2015.

• Prepare the face-to-face workshop on Core Data Models

Key points

• The members of the Community of Practice as advisors to thework delivered under Action 1.1.

• Work together on the creation of a set of guidelines under theumbrella of an standardisation body

• Identify, document and share good practices

Community of PracticeWebinar, Mar 2015

7

Share experiences, lessons-learnt and challenges

• Core Vocabulary developments and pilots

• Core data model initiatives from the participating countries

Agree on common actions and develop a roadmap

• Documentation of good practices

• Drafting of common guidelines

• Next meeting(s)

Community of PracticeGoals of today’s workshop

The most important reports and studies produced by ISA Action 1.1 can be found on semic.eu“

“

8

WorkshopAgenda

Start Topic

08:30 Registration & Coffee

09:00 Introduction to the Community of Practice

09:15 Setting the scene

10:00 Lightning talks from the participants

11:30 Discussion and next steps

12:30 Lunch break

14:00 The Core Public Service Vocabulary Application Profile (CPSV-AP)

14:50 Conclusion

9

Setting the scene

10

Key building blocks in the Core Data Models landscape

Source:https://joinup.ec.europa.eu/site/eia/EIRA/EIRA_beta_dev

11

The EU Core VocabulariesDefinition

CORE

VOCABULARY

PUBLICSERVICE

[1] https://joinup.ec.europa.eu/asset/core_vocabularies/description

The Core Vocabularies are simplified, re-usable and extensible data models that capture the fundamental characteristics of a data entity in a context-neutral and syntax-neutral fashion [1]“ “

12

• NIEM 3.0

• Stelselcatalogus

• UN/CEFACT CCL 13B

• Core Vocabularies RDF Schemas

• Japanese Infrastructure for Multilayer Interoperability (IMI)

Download the mappings from http://mapping.semic.eu(under the section Downloadables)“

“

• OASIS UBL Common Library 2.1

• KoSIT - XOV

• Swedish Company data model

• eIDAS minimum dataset

• MUG- BII

• OSLO 2.0

Other core data model initiatives

13

Harmonising core data models with the Core VocabulariesCore Data Models Mapping Directory

Creation of mappings

•Concept mappings

•Spreadsheet based

Publishing of mappings

•Quality control

•Transform to RDF

Exploration of mappings

•browsing

•Visual

•Machine processeable

14

Core Data Models Mapping DirectoryDemo

15

Harmonising core data models with the Core VocabulariesCreation of mappings between Core Data Models

Conceptual schema level mappings

• Express relationships between entities

• The existence of a relationship is prerequisite for an implementation

Syntax level mappings

• Express relationships between entities and how one representation can be transformed into another one

• Requires:

o A physical representations of each Core Data Model (e.g. XML, DB, RDF)

o A transformation engine. (e.g. XSLT, R2ML)16

The EU Core VocabulariesPilot projects already completed

• Core Location – interconnect Belgian National and Regional Address Registers

• Organization Ontology – link public sector's organisational data

• Core Public Service – describe public services only once

• Maritime surveillance data – integrate disparate sources of maritime surveillance data

• Linked data on plant protection products – integrate data about applications and decisions for authorisation of plant protection products

• Metadata Management pilot for the Marine and Maritime environment – adapting tools to specific requirements of the Marine and Maritime domain

17

The EU Core VocabulariesWe developed a handbook

How to design new data models that extend the Core Vocabularies

How to map existing data models to the Core Vocabularies

Step 5: Syntax documentation and mapping

Step 4: Syntax binding

Step 3 : Business rules

Step 2: Information modelling

Step1: Context &

Requirements

1. Define the context and

requirements

2. Select and reuse Core Vocabulary

Concepts

3. Define business rules

4. Bind to an existing syntax or

create a new syntax

5. Document the syntax and create

conformance mapping

Core Vocabularies Handbook

18

Beneficiary: DG Competition and EU Member States

State aid transparency Pilot project

Develop a new vocabulary by extending Core Vocabularies

Disseminate transparency information related to state aid as machine-readable open data.

19

Build an RDF dissemination vocabulary reusing the RDF syntaxes of the Core Vocabularies

Step 5: Syntax documentation and mapping

Step 4: Syntax binding to RDF

Step 3 : Business rules

Step 2: Information modelling

Step1: Context &

Requirements

State aid award

Beneficiary

Location

Aid measure

“Beneficiary” exact match “Legal entity”

“Location” close match “Address”

E.g. a Beneficiary has one and only

one Location

Registered Organisation Vocabulary

Core Location Vocabulary

Core Public Service Vocabulary

Application Profile

Mint new terms for un-matched properties

Create a mapping worksheet with the full list of properties

identified for the state aid

transparency domain

State aid transparency Pilot project

Develop a new vocabulary by extending Core Vocabularies

20

State aid transparency Pilot project

Develop a new RDF vocabulary by extending Core Vocabularies

CORE

VOCABULARY

PUBLICSERVICE

Beneficiary national ID

Sector

Beneficiary name

Beneficiary Type

Granting authority

Entrusted entity

Financial intermediary

Location

Amount

Currency

rov:registration

rov:legalName

rov:orgType

rov:orgActivity

rov:legalName

rov:legalName

rov:legalName

locn:adminUnitL2

State aid transparency vocabulary

cpsv:value

cpsv:currency

21

Beneficiary: DG GROW, Member States

EU Business Registers Interconnection System (BRIS)Pilot project

Develop a new vocabulary by reusing Core Vocabularies

22

Implemented the BRIS data models (i.e. the BRIS entity and the BRIS messaging models) based on data standards to enable the

interoperable communication of company data between interconnected registers of the Member States.

The XML representation of the Legal Entity class of the Core Business Vocabulary was reused in the XML Schemata that

implemented the BRIS data models.

Step 5: Syntax documentation and mapping

Step 4: Syntax binding to XML

Step 3 : Business rules

Step 2: Information modelling

Step1: Context &

Requirements

Company

Reusing the Core Business Vocabulary

by aligning Core vocabularies’

concepts with BRIS elements:

“Company “ is a narrow match of the “Legal Entity” class

E.g. a Company has one and only one

identifier (ID number)

Core Business Vocabulary

Standard naming and design rules

(NDRs)

Mint new terms where needed (e.g.

Country)

Create specific schema (XML) and

XSD validation artefacts

Create a mapping worksheet with the full list of properties

identified for the BRIS Core Entity

Model

23

EU Business Registers Interconnection System (BRIS)Pilot project

Develop a new vocabulary by reusing Core Vocabularies

The BRIS data models reused elements of the “Legal Entity” conceptof the Core Business Vocabulary.

EU Business Registers Interconnection System (BRIS)Develop a new vocabulary by extending Core Vocabularies

Core

Vocabula

ries

LegalEntity

LegalEntityLegalName

LegalEntityLegalIdentifier

LegalEntityCompanyType

LegalEntityCompanyStatus BRIS

Company

CompanyName

RegistrationNumber

LegalForm

CompanyStatus

24

WorkshopAgenda

Start Topic

08:30 Registration & Coffee

09:00 Introduction to the Community of Practice

09:15 Setting the scene

10:00 Lightning talks from the participants

11:30 Discussion and next steps

12:30 Lunch break

14:00 The Core Public Service Vocabulary Application Profile (CPSV-AP)

14:50 Conclusion

25

Lightning talks from the participants

26

WorkshopAgenda

Start Topic

08:30 Registration & Coffee

09:00 Introduction to the Community of Practice

09:15 Setting the scene

10:00 Lightning talks from the participants

11:30 Discussion and next steps

12:30 Lunch break

14:00 The Core Public Service Vocabulary Application Profile (CPSV-AP)

14:50 Conclusion

27

Discussion and next steps

28

• Develop common guidelinesfor core data models andreference data

• Fix the date for the nextwebinar

• Fix the date for the nextface-to-face meeting

• Open call for ideas!

Topics

29

Define scope &

ToC

Define a template

for practices

Document practices

Criteria for measuring

the “success”

of a practice

Derive common

guidelines

Publish the study

Develop common guidelines for core data models and reference dataApproach & methodology

C:ISAR:CoP

C:ISAR:CoP

C:ISAC:CoP

C:ISAR:CoP

C:UNC:ISA

C: Create| R: Review

30

• Title of the common guideline

• Domain of the common guideline (e.g. supports the changemanagement process, deployment, etc.)

• Description of the common guideline

• Challenges addressed

• Origin (from which good practice(s) does it originate)

• Impact of the common guideline

• Beneficiaries

• Costs

• Benefits

Develop common guidelines for core data models and reference dataProposed ToC for the common guidelines

31

• Country of origin, policy domain,…

• Metadata governance

• Governance structure

• Enforcement policy

• Quality controls

• Metadata management

• Design, harmonisation, publication, and deployment processes

• Change management process

• Standards

• Tool support

• Costs – include a breakdown if possible

• Benefits achieved, for each of the facts described

Develop common guidelines for core data models and reference dataDefine a template for good practices

32

• Share documents and collect feedback via the Confluence wiki

• Establish an editorial team by assigning roles to people (e.g.editor, contributors, review group)

• The master version of the document will be created andmaintained by the editor

• Communication will be facilitated via the mailing list of the CoP

Develop common guidelines for core data models and reference dataWorking culture & environment

33

• Early July 2015

or

• Early September 2015

Next webinar

34

WorkshopAgenda

Start Topic

08:30 Registration & Coffee

09:00 Introduction to the Community of Practice

09:15 Setting the scene

10:00 Lightning talks from the participants

11:30 Discussion and next steps

12:30 Lunch break

14:00 The Core Public Service Vocabulary Application Profile (CPSV-AP)

14:50 Conclusion

35

The Core Public Service Vocabulary Application Profile (CPSV-AP)

36

WorkshopAgenda

Start Topic

08:30 Registration & Coffee

09:00 Introduction to the Community of Practice

09:15 Setting the scene

10:00 Lightning talks from the participants

11:30 Discussion and next steps

12:30 Lunch break

14:00 The Core Public Service Vocabulary Application Profile (CPSV-AP)

14:50 Conclusion

37

Conclusion

38

• New members of the CoP to be included in the mailing list.

• Members of the CoP to propose additional colleagues to be included in the list.

• All workshop material to be available on Joinup by 08 May.

• EIRA semantic view feedback/validation:

o Material of the semantic view of the EIRA to be uploaded for review on Joinup by Tuesday 12 May and a notification e-mail will be sent to the members of the CoP.

o The members of the CoP to provide their feedback by 30th May.

39

Conclusions & decisions taken

Members of the CoP to collaborate for the creation of a document for providing common guidelines for core data models.

Proposed activities

• A proposed scope (based on the EIRA semantic view);

• ideas on how to assess practices and lessons learnt shared by the members of the CoP;

• a template for documenting the efforts from the different MSs;

• timeplan and allocation of roles and responsibilities; and

• some first candidate cases.

ISA will investigate the opportunity to develop this document under the umbrella of the UN

This exercise is linked to the Methodology and tools for Metadata Governance and Management for EU Institutions and Member States 40

Conclusions & decisions taken

Mappings:

• Increase clarity of mapping types/classification.

• Japan to provide input regarding the mapping types to the Core Vocabularies by mid May.

• The semantic view of EIRA to be opened for review to the CoP by early June.

• All the members of the CoP to check the mapping tool and provide comments by 30th May.

• Validate existing mappings on a case by case basis.

• “Formal” mappings to be published by mid July.

• Add more mappings: propose national data models to be mapped.41

Conclusions & decisions taken

Webinar (end of June) to be organised as a check point for:

• EIRA validation

• Scope and approach for the good practices

• Status of the mappings

42

Conclusions & decisions taken

Join the SEMIC group on LinkedIn

Follow @SEMICeu on Twitter

Join the SEMIC community on Joinup

Get involvedVisit our initiatives

ADMS.

SW

CORE

VOCABULARY

PUBLICSERVICE

REGISTERED

VOCABULARY

ORGANIZATION

Community of Practice on

Core Data Models

contact@semic.eu

43