D2.3 - Upper Level Cultural Heritage Data Structure & Ontology
•Download as PPT, PDF•
0 likes•1,616 views
CrossCult H2020 Project Deliverable Brief Overview
Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
D2.3 - Upper Level Cultural Heritage Data Structure & Ontology
- 1. Brief Overview D2.3 - UPPER-LEVEL CULTURAL HERITAGE DATA STRUCTURE & ONTOLOGY
- 2. Metadata models integration: Overview This task will integrate the metadata used in the four pilots Review and analyse vocabularies/ontologies used in the pilots Define upper-level ontology for cultural heritage Create links between individual data models and upper-level ontology
- 3. Review of Ontology Requirements Single Generic Upper-Level Ontology A Semantic “glue” of common Concepts and Relationships Scalable and Extensible Cater for Pilot Specialisations
- 6. Review of Ontology Requirements Facilitate Interoperability and Linking to External Resources Maximum Reuse of Existing Standards when possible Support the Knowledge Base needs of CC Semantics : Entities / Concepts Reasoner and Useful Relationships and Linking
- 7. Pathway to Ontology Definition Review Pilot Datasets D2.1 Review Pilot Datasets D2.1 Partner DiscussionsPartner Discussions Identify Common Concepts Identify Common Concepts Grouping & Abstraction Grouping & Abstraction Propose MappingsPropose Mappings
- 8. Dataset Review & Discussions The partners identified the following entities of interest: Physical Items Landmark Places Dates MM Content Users Venues User Profiles Venue Profiles Reflection Topics Routes User Tracking Points of Interest (POI)
- 9. Grouping and Abstraction Physical Item Digital MM Content Reflection Topic Place Date Person Organisation
- 10. Core Upper Level Ontology CC.Reflection Topic Project Specific Entity Extends E89.Propositional Object (immaterial Item, topic of discourse) P670.reflects | P670i is reflected by Project Specific Entity Extends P67i.is referred to by | P67.refers to
- 11. Core Upper Level Ontology Extensions Provide Flexibility to introduce semantics closer to CC definition of reflection topic A shortcut for connecting CC.Reflection Topic with E18.Physical Thing
- 13. Core Upper Level Ontology
- 14. Apply Ontology to Pilot Examples Example from Pilot 4 Max plays a treasure hunt game in Luxemburg. He got interested in the statue of Tall Banker. He found its location on the map of Kirchberg together with a group of objects, all related to the thread of cross-border worker
- 15. Apply Ontology to Pilot Examples
- 18. Next Steps Further Refinement and Improvement Emerging Semantic Interoperability Requirement Scope and Structure of the Reflective Topic semantics Integrate CC Knowledge Base User Ontology Venue Ontology Populate ontology with data from the 4 pilots’ datasets
Editor's Notes
- Overview on the requirements of theT2.2 task, highlighting the the focus on integration of diverse resources under an overarching layer of semantics. The CrossCult Upper-level ontology fosters the semantic harmonization of disparate cultural heritage datasets.
- The main requirements of the Upper-level ontology can be summarized into the following points; Single Generic Upper-Level Ontology – an overarching scheme, used as a Semantic “glue” of common Concepts and Relationships, the should be Scalable and Extensible to accommodate new pilot cases and reflection scenarios, but which at the same time is flexible to address Specialisations needs of each pilot.
- The Upper-level ontology as the semantic glue layer between the CC Knowledge Base structures and the Semantic Web.
- In addition the review process reveled another set of requirements relating to the semantic enrichment of data. The Upper-ontology structure is required to enable linking to semantic web definitions and to take full advantage of reusing existing standard ontological definitions.
- The pathway to ontology definition, passes from an initial review of datasets and partner discussions, in the light of identifying the shared semantic between pilot dataset and scenarios. Then the revealed semantics are grouped into conceptual abstractions, which propose standard definitions and mapping to CIDOC-CRM, SKOS, FOAF
- A set of concepts as emerged by the first round of reviewing the datasets and discussing with the pilots.
- More formal abstractions of the common - across the pilots- concepts.
- The specialization of the project specific entity Reflection Topic is based is required for enabling the semantics a Physical Thing to reflect one or more reflective topic propositions.
- The Reflective Topic as a central node between the core entities of an ontological scheme
- Formal expression in CIDOC-CRM of the relationship between Reflective Topic and Physical Thing and core entities of the Upper-level ontology.
- A scenario description from Pilot 4
- The scenario expressed in formal semantics
- A view of the Upper-level ontology in Protégé
- Demonstration of the volume of relationships of the ontology individual POI Tall Banker in the Upper-level structure.
- The final version of the ontology will be delivered in M25, the work is ongoing and further refinements are expected to take place. The CC knowledge base will integrate the user and venue ontologies.