INTEROPERABILITY + SEMANTICS = CHECK! Smart and Cost Effective Data Modelling and Tools of the Future Miika Alonen, CSC – IT Center for Science Suvi Remes, CSC – IT Center for Science Patrik Maltusch, Aalto University Mikael af Hällström , Finnish Tax Administration 1
Summary • Interoperability challenges • Interoperability case: Student Transcript • Framework for Semantic Interoperability • Implementing the Framework: – Interoperability workbench 2
Present – Information chaos Organisation and application VIRTA Oili VTJ specific documentation Redefining data models Opintopolku Vipunen Y Point to point Integration No change management EMREX X over organisation borders Oodi
Interoperability CASE: Student Transcript 4 Your logo here
Making data sources semantic interoperable for a DW 80 h 4800 € ~1 milj. € ~80.000 € 20 Cost for the community 1000 h 60.000 €
Equation for Interoperability SEMANTIC IMPACT ICC ∗ ESB ∗ EIM ∗ DW = 𝑐𝑓𝑜𝑓𝑔𝑗𝑢𝑡 >1 𝑑𝑝𝑡𝑢 by Patrik Maltusch @aalto.fi ICC = Integration Competence Center ESB = Enterprise Service Bus EIM = Enterprise Information Management DW = DataWareHouse
Used methods for documenting APIs? Java Python Terminological dictionaries Programming Application interfaces Wikis Glossary XML Javascript Swagger SKOS WSDL Documents Classifications SOAP JSON Concept models Enumerations Data warehouses XML schema Wiki SQL Reference data ER RDB Data modelling RDF Codeservers UML Excel XML
Vision – Data model reuse and uniform documentation Domain vocabularies Shared Reusable core semantics Reusable classifications data models Application profiles X Y VIRTA EMREX Use of Uniform documentation for data shared semantics APIs and Applications Oili Opintopolku UNI Ö Application profiles
Application profiles An Application profile seeks to 2000 - Idea of Application Profiles address the interoperability evolved from DESIRE Registry requirements between systems by: project : “mixing and matching” metadata elements • retaining conformance with a base standard 2003 - Guidelines for creating application profiles (CEN/CWA • defining new requirements in an 14855) open and interoperable manner 2005 – Guidelines for machine- readable representation .. (CEN/CWA 15248) Examples of standard Application 2006 - Guidelines building profiles: application profiles in e-learning (CEN/CWA 15555) CEN/CWA 15903 : Metadata for Learning 2008 - Guidelines for Dublin Core Opportunities CEN/CWA 16132 : European Learner Application Profiles Mobility Achievement Information 2011 - 2016 – MLR Framework EMREX AP (2016): Report for the (ISO/IEC 19788-1) recognition of external studies
Need for common framework Shared concepts with the business and IT: 1. Well defined concepts 2. Unique identifiers 3. Machine readable format Service innovation and data modeling based on business needs: 1. Reuse terms and definitions 2. Create reusable components 3. Focus on the interfaces and integration Framework for semantic interoperability : • How to publish core vocabularies • and application profiles? • How to reuse standards? • How to reuse core vocabularies in the implementations? • How to document the metadata reuse? • How to document application interfaces?
Semantic interoperability framework Core Application Terminology vocabularies Profiles • Classes • Context • Concepts • Attributes • Constraints • Definitions • Associations • Extensions • Classifications Common metadata architecture for data modelling: • Machine readable terminology • Reusable core vocabularies and core components • Documented reuse of core components
Interoperability objectives • Shared metadata • Interoperability with models for education international and research standards • Modular and reusable • Promote standard metadata definitions reuse • Improve readability • Formal and semantic and understandability mappings to CEN and of data models ISO standards 12
Interoperability benefits • Collaborative tool for • Shared terminology metadata publishing – Less confusion – Benefit from external • Same terms for many expertice communications • Avoid redefinition of needs data models – Study administration – Lower integration – User interfaces costs 13
14
Domain specific vocabularies are administered by different agencies and published in the standard SKOS model in the Finnish Thesaurus and Ontology Service 15
Core vocabularies are published as Linked Data that defines re-usable classes and properties based on shared concepts and links to standards and best practices. 16
Domain specific data models and interfaces are documented as Application profiles that re-use the classes and properties from the Core Vocabularies 17
Data models are implemented with languages that best suit the given architecture by implementing the application profile. 18
Simplified process for describing Core vocabularies and Application profiles 19
Piloting Interoperability Framework VIRTA University EduCloud Information Oili Systems Opintopolku EMREX Enables Universities and Consortium Partners to start documenting local implementations using free & open source tools Documenting Documenting Open APIs Open APIs iow.csc.fi Core vocabularies Application profiles
Interoperability workbench • Collaborative online tool for creating Core Vocabularies and Application Profiles: 21
Interoperability workbnech • Tool for defining resolvable and machine readable data models • Document the use of data models, standards and best practices 22
Integration to controlled vocabularies • Link controlled vocabularies to created model • Create classes and properties based on existing concepts 23
Integration to classification schemes • Link to existing reference data from code service • Restrict allowed values by using existing reference data 24
Interoperability workbench • Import existing models from local models and external namespaces 25
Interoperability workbench • Include and search metadata from imported standards • Create new domain models as highly reusable metadata 26
Interoperability workbench • Map new classes and class usage to relevant standards 27
Interoperability workbench • Export schemas in multiple formats • Enforces Naming practices RDF JSON Schema XML Schema tbd … 28
Thanks! • Questions • Interoperability workbench • http://iow.csc.fi 29
Recommend
More recommend
