1. e-SENS WP6.2 face-to-face meeting, Poznan, 24 October 2013 ISA Programme Action 1.1 - Semantic Interoperability Suzanne.Wigard@ec.europa.eu Stijn.Goedertier@pwc.be e-Documents based on reusable core assets such as core vocabularies

2. Outline 0. ISA Programme Action 1.1 1. What are the Core Vocabularies? 2. Why using the Core Vocabularies? 3. How to use? 4. Where already used? 2

3. “Standards are like toothbrushes, a good idea but no one wants to use anyone else's” - Anita Golderba

4. Questions raised so far during this meeting… Which building block types: methodology, library, NDR, tools …? Reuse by restriction/extension? Syntax vs Semantics? Governance mechanism and sustainability? Metadata management? Reuse existing tools… exchange data elements between tools? Does it matter at all? (mediation) Do libraries cover everything? … And how about RDF?

5. 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 5

6. Political context European Interoperability Framework 6 Source: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdfhttp://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf

7. ISA Action 1.1 Semantic Interoperability New Work Package: Define a Method to build e-Documents based on Core Assets Methodology e-Documents Core Assets (Building Blocks)

8. Methods Examples: CCTS NIEM Naming and Design Rules (NDR) UBL ISA Core Vocabularies

9. e-Documents Definition? Machine-readable? PDF? XML? Messages?

10. Core Assets UN/CEFACT Core Component Library UBL 2.1 Library ISA Core Vocabularies

11. Definition: … Core Person Core Location Org, RegOrg Other initiatives Asset Description Metadata Schema (ADMS) DCAT application profile

12. Why we should collaborate What is e-SENS CC6.2 doing? "Develop Semantic Assets" What is a Semantic Assets?

13. D6.1 chapters Stock taking from predecessor LSP – Building Blocks Methodology SWOT analysis Maturity Semantic tools Requirements for semantic interactions EIA description of Building blocks Overview of semantic assets in Europe Priorities, Plans

14. Analysis of resources from the JoinUp portal (D6.1) eSens domainJoinUp asset theme Number of assets on JoinUp (July 2013) eBusinessBusiness and Competition5 eJusticeLaw and Justice19 eHealthHealth20 eEmploymentEmployment16 eEducationEducation13 eAgricultureAgricultura, Forestry and Fisheries22

15. Types of Semantic Assets (D6.1) Schemas (Messages, eDocs, …) Knowledge organization systems: o Codelists, Catalogues, (Controlled) Vocabularies o Taxonomies, Thesauri, Name authorities Ontologies Mappings/Translations, Mapping Services Other Services (Syndication, Service Catalogue, Directory of Registers) Process flows Containers

16. Future plans for CC 6.2 Create? Reuse? What is reusable? What is generic?

17. Thank you for your attention

18. Outline 0. ISA Programme Action 1.1 1. What are the Core Vocabularies? 2. Why using the Core Vocabularies? 3. How to use? 4. Where already used? 18

19. Building consensus on core vocabularies 2 WGs with each 60+ members 21+ EU Member States Following a formal process and methodology Public review periods Re-using existing standards 19 Source: https://joinup.ec.europa.eu/node/43160https://joinup.ec.europa.eu/node/43160

20. Core vocabularies Simplified, re-usable, and extensible data models that capture the fundamental characteristics of a data entity in a context-neutral fashion. 20 Source: https://joinup.ec.europa.eu/node/43160https://joinup.ec.europa.eu/node/43160

21. 4 core vocabularies 21 Fundamental characteristics of a person. Fundamental characteristics of a legal entity, such as legal identifier, name, company type, activities. Fundamental characteristics of a location, represented as an address, a geographic name, or a geometry. Fundamental characteristics of a public service.

22. 3 representation formats RDF schema Re-uses existing RDF vocabularies ISA Open Metadata Licence v1.1 IPR Re-uses Core Components Technical Specification (CCTS) and UBL NDR XML schema Conceptual model Re-use existing concepts in CCL, INSPIRE, etc. Maintained by W3C (Government Linked Data Working Group) 22

23. Core Vocabulary UML Model 23 A conceptual model of the Core Vocabularies To enable humans to understand the meaning of the data model Not (yet) used for model-driven design of schemas

24. Illustration: Core Person UML model 24

25. Core Vocabulary XML Schemas According to OASIS Universal Business Language (UBL) XML Naming and Design Rules (NDR) Garden of Eden design pattern (maximising reuse of global elements) Using Crane Software Genericode-to-UBL-NDR scriptGenericode-to-UBL-NDR Location XML Schema as subset of the INSPIRE Data Specifications (GML Application Profile)? 25 https://joinup.ec.europa.eu/node/43160

26. 26 UBL-CommonBasicComponents-2.1.xsd (namespace prefix: cbc) CoreVocabularyBasicComponents-v1.00.xsd (namespace prefix: cvb) CorePerson.xsd (namespace prefix: cperson) … … The global elements cbc:FamilyName and cvb:FullName can be reused in any schema Illustration: Person XML Schema

27. Core Vocabularies RDF Schemas Maximally reuse existing foundational RDF Vocabularies: Dublin Core Terms, FOAF, SKOS, … Created with a text editor Core Location as a foundational RDF Vocabulary for the INSPIRE Data Specifications? 27

28. 28 foaf:familyName rdfs:comment "..."@en ; rdfs:isDefinedBy ; rdfs:label "family name"@en ; dcterms:identifier "foaf:familyName"@en ; vann:usageNote "A family name is usually shared by members of a family. This attribute also carries prefixes or suffixes which are part of the Family Name, e.g.... "@ en. foaf:name rdfs:comment "..."@en ; rdfs:isDefinedBy ; rdfs:label "name"@en ; dcterms:identifier "foaf:name"@en ; vann:usageNote "The full name contains the complete name of a person as one string. In addition to the content of given name, family name and, in some systems, patronymic name... "@en. person:Person rdf:type rdfs:Class ; rdfs:comment "..."@en ; rdfs:isDefinedBy : ; rdfs:label "Person"@en ; rdfs:subClassOf schema:Person, foaf:Person ; dcterms:identifier "person:Person"@en. Illustration: Person RDF Schema The global properties foaf:familyName and foaf:name can be reused in any schema

29. Outline 0. ISA Programme Action 1.1 1. What are the Core Vocabularies? 2. Why using the Core Vocabularies? 3. How to use? 4. Where already used? 29

30. 3 generic use cases 1. Harmonised access to base registers (basic public service) 2. Interoperable cross-border public services (aggregate public service) 3. Interoperability of public data: making it easier to mash up public data 30

31. 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 31 Source: http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdfhttp://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf

32. Denmark: “Good basic data for everyone” http://www.digst.dk/ 32

33. Outline 1. What are the Core Vocabularies? 2. Why using the Core Vocabularies? 3. How to use? 4. Where already used? 33

34. How to use the e-Government Core Vocabularies? Reuse the core vocabularies as semantic building blocks for information exchange Reuse-by-restriction: use only a subset of the Core Vocabularies (e.g. only locn:Address) Reuse-by-extension: use the Core Vocabularies as a foundational data model that is extended with context-specific elements 34

35. Re-use by extension: 3 levels of abstraction e-Documents Linked Data, e-Documents (?) e-Documents domain models domain vocabularies domain schemas 35 Core level Message level Domain level RDFS /OWL XML Schema Core Vocabularies representation techniques … Levels of abstraction UML model

36. Illustration: patient healthcare domain 36 Patient as a subclass of Person… with a property blood type

37. Illustration: patient healthcare domain XML Schema 37 Patient.xsd (namespace prefix: cpatient) … …

38. Illustration: patient healthcare domain RDF Vocabulary 38 @prefix dct:.http://purl.org/dc/terms/ @prefix ex:.http://example.com/ @prefix foaf:.http://xmlns.com/foaf/0.1/ @prefix person:.http://www.w3.org/ns/person# @prefix rdf:.http://www.w3.org/1999/02/22-rdf-syntax-ns# @prefix rdfs:.http://www.w3.org/2000/01/rdf-schema# @prefix schema:.http://schema.org/Patient @prefix skos:.http://www.w3.org/2004/02/skos/core# @prefix ncicb:.http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl# ex:Patient a rdfs:Class ; rdfs:label "Patient"@en ; rdfs:comment "A patient in the cross-border healthcare domain."@en ; rdfs:subClassOf person:Person ; rdfs:subClassOf schema:Patient. ex:BloodType a rdf:Property ; rdfs:label "blood type"@en ; rdfs:comment "..."@en ; vann:usageNote "..."@en ; dct:identifier ex:bloodType ; rdfs:domain ex:Patient; rdfs:range ncicb:C61009.

39. Outline 0. ISA Programme Action 1.1 1. What are the Core Vocabularies? 2. Why using the Core Vocabularies? 3. How to use? 4. Where already used? 39

40. Known implementations e-CODEX large-scale pilot on eJustice Open Corporates The OSLO project 5 pilot implementations initiated by the ISA Programme: 25 public administrations 14 Member States 4 EU Institutions 40

41. 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 view SPARQL endpoint INSPIRE lookup, disambiguate, link 41 XML and RDF views on relational data served over a Web interface XML view Xquery, Xpath Core Location Pilot: https://joinup.ec.europa.eu/node/63242https://joinup.ec.europa.eu/node/63242

42. 42

43. GR- Company data of the Greek tax authorities 43 Master thesis project of Natasa Varitimou Using API of Greek tax administration 30K+ companies

44. GR- Ministry of administrative reform and electronic governance 44

45. Core public service vocabulary Describe public services “only once” using a standard vocabulary, make machine-readable descriptions available to others so that they become searchable on many governmental access portals. Core Public Service Vocabulary 45 https://joinup.ec.europa.eu/asset/core_public_service/description

46. Public services in Europe 46

47. Flemish Intergovernmental Product and service catalogue (IPDC) Exchange of service catalogue data between national, regional, and local governments. REST web service that returns XML. XSLT to convert into Core Public Service.XSLT Project manager: Katrien De Smet, CORVE (present at SEMIC 2013!) 47 http://www.corve.be/projecte n/lokaal/IPDC/

48. OSLO: Open Standards for Local Administrations 48 Putting the core vocabularies into a local context. Local administrations need locally enriched data models and data.

49. OpenCorporates: basic company data for everyone Machine- readable data: (URI, legal identifier, name, company type, activities) Links back to the base registers 49

50. Conclusions The core vocabularies are used in many different contexts. They can easily be extended and integrated with other vocabularies. They can be adapted to your needs and context. The can be used both in an XML and an RDF world. 50

51. Core Vocabularies: a semantic building block for e-SENS? 51 ?

52. Join SEMIC group on LinkedIn Follow @SEMICeu on Twitter Join SEMIC community on Joinup Project Officers: Vassilios.Peristeras@ec.europa.eu Suzanne.Wigard@ec.europa.eu Contractor: Stijn.Goedertier@pwc.be Get involved Visit our initiatives 52