Upload
semiceu
View
348
Download
2
Embed Size (px)
Citation preview
Workshop
The creation of an international core data model
Antwerp, 19 November 2015
A presentation by PwC EU Services
Agenda
Duration Topic
15’ Round table
15’ Setting the grounds for international core data models
30’ Implementations of the ISA Core Vocabularies across Europe
20’ The Community of Practice on data standards
10’ Q&A
2
Who is who?
Agenda
Duration Topic
15’ Round table
15’ Setting the grounds for international core data models
30’ Implementations of the ISA Core Vocabularies across Europe
20’ The Community of Practice on data standards
10’ Q&A
4
Setting the grounds for international core data models
Agreeing on common terminology & definitions
Source:https://joinup.ec.europa.eu/site/eia/EIRA/EIRA_beta_dev
6
The two main types of data standards are:
• data models
• reference data
Data standard
A data standard is a structural metadata specification that describes or defines other data [ISO111179]. Structural metadata indicates how compound objects are put together [NISO].“ “
“
“
European Interoperability Reference Architecture
Semantic View
Data models
The use of standardised data models as common building blocks fordeveloping information systems guarantees a minimum
of semantic consistency and facilitates information exchange.
A data model is a collection of entities, their properties and the relationships among them, which aims at formally representing a domain, a concept or a real-world thing.“ “
“
“
European Interoperability Reference Architecture
Semantic View
Reference data
Standardised reference data is key to data integration and interoperability, and facilitate the sharing and reporting of information.
Reference data is small, discrete sets of values that are not updated as part of business transactions, but are usually used to impose consistent classification. Reference data normally has a low update frequency. Reference data is relevant across more than one business systems belonging to different organisations and sectors.
“ “
“
“
Examples: lists of status codes, currency codes, country abbreviations, demographic fields, genders, file types.
European Interoperability Reference Architecture
Semantic View
• Describe basic information involved in an organisation, e.g. information about persons, companies, vehicles, buildings, locations, roads
• Used by multiple business processes and different public services
• Stored in base registries
Master data
Standardising master data formats and values are critical for successful system integration and information exchanges.
Master Data is the authoritative, most accurate data that is available about key business entities, used to establish the context for business transactions and transactional data.“ “
“
“
European Interoperability Reference Architecture
Semantic View
Agreeing on the representation of core data entities The ISA Core Vocabularies
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]“ “
11
• Core Evidence & Core Criterion
• Core Public Organisation
New Core Vocabularies Development starts in December 2015
[1] https://joinup.ec.europa.eu/asset/core_vocabularies/description
“ “
12
What are for you the most important core vocabularies?
Harmonising core data modelsCore 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
13
Discover more at: http://mapping.semic.eu
Harmonising core data modelsCreation 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)14
Overview of mappings to the ISA Core Vocabularies
Core data model Exact & close matches
Other matches No matches
NIEM 3.0 44% 35% 21%
KoSIT - XOV 41% 22% 37%
OSLO 38% 0% 62%
Stelselcatalogus 31% 12% 57%
IMI Vocabulary 29% 19% 52%
Swedish Company data model 27% 7% 66%
15
Agenda
Duration Topic
15’ Round table
15’ Setting the grounds for international core data models
30’ Implementations of the ISA Core Vocabularies across Europe
20’ The Community of Practice on data standards
10’ Q&A
16
Implementations of the ISA Core Vocabularies across Europe
The Core Vocabularies Handbook for design and alignment
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
Implementation in EU systems
Beneficiary: DG Competition and EU Member States
State aid transparencyDevelop a new vocabulary by extending Core Vocabularies
Disseminate transparency information related to state aid as machine-readable open data.
20
Build an RDF dissemination vocabulary reusing the RDF syntaxes of the Core Vocabularies
State aid transparency 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)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.
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
23
Implementation in the Member States
OSLO, an extension of the Core Vocabularies in a local context, is a simplified, reusable and extensible data model that captures the fundamental characteristics of information exchanged by Flemish public administration in
the domains: contact information, localisation and public services.
• Why starting from the Core Vocabularies – the benefits
• What were the vocabularies extended
• How were the Core Vocabularies extended
OSLO
• The adoption of the Core Public Service Vocabulary in Estonia forpublic service portfolio management
• The Italian application profile of the Core Public Service Vocabulary
• The planned extension of the Core Public Service Vocabulary forsupporting the Belgian Point of Single Contact.
Other cases from the Member States
Agenda
Duration Topic
15’ Round table
15’ Setting the grounds for international core data models
30’ Implementations of the ISA Core Vocabularies across Europe
20’ The Community of Practice on data standards
10’ Q&A
27
The Community of Practice on data standards
A network of representatives from (or working for) publicadministration organisations aiming to:
• Share knowledge, experiences and lessons-learnt on core datamodels and reference data
• Harmonise existing initiatives
• Develop together guidelines for core data models and referencedata
• Define together areas of future collaboration in ISA Action 1.1
Community of PracticeScope
Discover more at: https://joinup.ec.europa.eu/community/semic/og_page/cop-data-standards
Community of PracticeParticipants
Organisations Countries
• Ministry of Economy• Instytut Logistyki i Magazynowania
Poland
• Ministry of Environmental Protection and Regional Development• Regional State Development Agency
Latvia
• DHS Information Sharing Environment Office (NIEM) USA
• Directorate of Ministry of finances and public administrations Spain
• Bolagsverket - Swedish Companies Registration Office Sweden
• Ministry of Finance• ELY - Centre for Economic Development, Transport and the
EnvironmentFinland
11
3
5MemberStates
Thirdcountries
EC andUNU
30
Community of PracticeParticipants
Organisations Countries
• V-ICT-OR Belgium
• Ministry of the Interior Lithuania
• Logius Netherlands
• Data Exchange Agency Georgia
• Ministry of Finance Cyprus
• Bundeskanzleramt Austria
• Ministry of Economic Affairs and Communications Estonia
• IPA• Ministry of Economy, Trade and Industry• National Institute of Informatics
Japan
11
3
5MemberStates
Thirdcountries
EC andUNU
31
Common guidelines, good practices and lessons learned related to data
standards
• Share knowledge with the members of the Community of
Practice.
• Support new and on-going initiatives on data standards in
public administrations by providing common guidelines, good
practices and lessons learned concerning the management of data
standards.
• Identify alignment opportunities amongst the various
initiatives.
Objectives
A case study is considered within the scope of the current project ifit meets one or more of the following criteria:
• It relates directly to the management and governance ofdata standards.
• It is about data standards targeting the implementation of ITsystems having regional, national or cross-border coverage, orconcerns the exchange of information between systems withinor across borders.
• It relates to data standards covering one or more policy areas.
“
Scope
34
Case study template
35
• General information: Title, policy domains covered by thecase study, contact person, and references;
• Business model: Problem & challenges, Solution, Targetedaudience, Value proposition, Key metrics, Key activities,Strengths, Weaknesses, Cost structure, Revenue streams;
• Implementation experience: A practical implementation ofthe data standard described by the case study.
Agenda
Duration Topic
15’ Round table
15’ Setting the grounds for international core data models
30’ Implementations of the ISA Core Vocabularies across Europe
20’ The Community of Practice on data standards
10’ Q&A
36
Q&A
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
ISA Action 1.1 - http//semic.eu [email protected]