3 3 Session Structure 1) Scope of the Ontology Summit 2008: Open Ontology Repository Architecture Session Discussion 2) Brief Recap of Online Discourse 3) Discussion Points Overview 4) Discussion Topic 5) Focused Discussion 6) Iteration of 4 and 5
4 4 Recap of Online Discourse 1)Assumptions 2)Archival Approach 3)Federated versus Centeralized Architecture Approach 4)Content Layering 5)Repository / Registry – PotAto / potAHto 6)Management of Repository 7)Metadata for OOR 8)Formatting of Ontologies 9)Required Services Integration
5 5 Discussion Points (morning) 1)Federation of Architecture 2)Content Components 3)Non-restrictive formatting of Ontology 4)Support of Support Applications
6 6 Federated Repository Architectural Framework Why a Federated structure - Open Resulting High-level Architectural Framework Requirements - SOA Point (1) : Federation of Architecture
7 7 Point (2): Content Components Content Components of Architecture Ontology stored / referenced within the repository Metadata structures for overlay on ontologies stored / referenced within the repository Metadata adhering to a structure, overlaid on an ontology stored / referenced within the repository
8 8 Point (3): Non-restrictive formatting of Ontology Methods to store / support ontologies Restriction to flat-file ontology representations within repository Access to other ontologies through registry and a common API Attachment and support of formatting data
9 9 Point (4) : Support of Support Applications Registry/Repository of support applications and hooks (API) Where the applications live Declaration of application capabilities (Ontology of applications) Open access to applications
11 Discussion Points (afternoon) 5)Defining and Storing Relationships 6)Mapping and Ontology Integration 7)Components of the Architecture 8)Content revisited
12 Point (6) : Mapping and Ontology Integration Mapping and Integration within and across Ontology Repositories Mappings required at what levels. Compatibility of content across ontologies Compatibility of the enumeration values for metadata tagging. Mappings maintenance.
13 Point (5) : Defining and Storing Relationships Architecture support for ties amongst the content of the repository Set of relationships stored vs set of relationships supported Which ties are to be stored and available to applications A level of formalization should be set for relationship declaration
Your consent to our cookies if you continue to use this website.