OpenOntologyRepository Requirement

   (3656)

OpenOntologyRepository (OOR) Initiative - Requirement    (1841)

This page is for the documentation related to the requirements of the "open ontology repository" we are planning to implement through the OOR initiative.    (1842)

Basic Principles and Capabilities    (1HTK)

• The 2008 Ontology Summit provides a foundation for the implementation of the OOR    (1HTL)

Criteria for Adoption    (1HT2)

• Each requirement should clearly map to one of the subcategories identified in the candidate ideas or other references as listed on this page    (1HSI)

• Each requirement should contribute to the usability of the OOR    (1HT0)

• Each requirement should be designed to include any possible user, regardless of country of origin or potential use    (1HTA)

Adopted    (1843)

•    (1THN)
  • ref. http://ontolog.cim3.net/forum/oor-forum/2008-04/msg00012.html    (1GCZ)
  • Four Objectives    (1TI5)
    • 1. Make the Data Visible. This means that all the consumers of the data can discover the existence of that data.    (1TI6)
    • 2. Make the Data Accessible. This means that the consumers have appropriate authority to access the data.    (1TI7)
    • 3. Make the Data Understandable. This basically means — make it self-descriptive.    (1TI8)
    • 4. Support the Unanticipated User. This essentially means no limit on the number of the users, in a style similar to the World Wide Web.    (1TI9)

•    (1TIA)
  • Goals of the Open Ontology Repository    (1GD0)
    • Provide an architecture and an infrastructure that supports the    (1GD1)
      1. Storing,    (1GD2)
      2. Sharing,    (1GD3)
      3. Searching,    (1GD4)
      4. Governance,    (1GD5)
      5. Management of Ontologies.    (1GD6)
    • Requirements, High Level Assumptions    (1GD8)
      1. Not all capabilities will be implemented at any single version.    (1GD9)
      2. The architecture will evolve. There will be multiple versions each successor implanting additional capabilities and/or evolving the previous version.    (1GDA)
      3. Instance data, which are themselves not ontologies, will not be stored in the repository    (1GDB)
      4. The repository will meet the needs of operational or commercial systems.    (1GDC)
      5. Applicable standards will be used.    (1GDD)
    • General    (1GDE)
      1. The repository architecture shall be scalable    (1GDF)
      2. The repository shall be distributed.    (1GDG)
      3. The specification of the repository shall be sufficiently detailed and platform independent to allow multiple implementations.    (1GDH)
      4. The repository shall be capable of supporting ontologies in languages that have reasoners.    (1GDI)
      5. The repository architecture shall support distributed repositories.    (1GDJ)
      6. The repository architecture shall not require a hierarchical structure.    (1GDK)
    • Discovery    (1GDL)
      1. The repository shall provide metadata capabilities to support    (1GDM)
         1. search capabilities,    (1GDN)
         2. governance process,    (1GDO)
         3. management    (1GDP)
      2. The repository shall provide a content discovery mechanism that supports discovery by    (1GDQ)
         1. domain    (1GDR)
         2. author/creator/source    (1GDS)
         3. version    (1GDT)
         4. usage    (1GDU)
         5. language    (1GDV)
         6. terminology    (1GDW)
         7. quality    (1GDX)
    • Search    (1GDY)
      1. The repository shall provide a capability to    (1GDZ)
         1. search locally    (1GE0)
         2. search globally    (1GE1)
      2. The repository shall provide a capability to browse a repository    (1GE2)
         1. locally    (1GE3)
         2. globally (011)    (1GE4)
    • Subscription / Notification    (1GE5)
      1. The repository shall provide the ability for a user to subscribe to/for alerts associated with one or more repository items.    (1GE6)
      2. The repository shall provide the ability for a user to subscribe to/for automatic updates of one or more repository items.    (1GE7)
    • Management    (1GE8)
      • The repository shall provide a mechanism to enforce access policies    (1GE9)
      1. The repository shall provide a mechanism to enforce submission policies    (1GEA)
      2. The repository shall provide a mechanism to enforce governance policies    (1GEB)
      3. The repository shall provide a mechanism to enforce tracking policies    (1GEC)
      4. The repository shall provide a mechanism to create usage reports    (1GED)
      5. The repository shall provide syntax validation mechanisms    (1GEE)
      6. The repository shall provide a logical consistency checking mechanism    (1GEF)
      7. The repository shall provide a mechanism to automatically categorize a submission    (1GEG)
      8. The repository shall provide a mechanism to maintain state change of repository items (i.e. versioning)    (1HSD)
      9. The repository shall provide user and administrator access control mechanisms    (1GEI)
    • Governance    (1GEJ)
      1. The repository shall provide explicit machine usable/accessible repository semantics    (1GEK)
      2. The repository shall provide a mechanism to avoid intellectual property and related legal issues/problems    (1GEL)
  • Functional Requirements of an RDF/OWL Repository:    (186D)
    • Provide Capability to Submit an Ontology to the Repository.    (186F)
      • Extract administrative and descriptive data from the metadata fields of an OWL ontology.    (186G)
        • Metadata should follow existing metadata standards.    (186H)
        • Submitted items should be tracked with version numbers (after determining the levels of granularity needed for versioning).    (186I)
        • Generate a meta-card entry for the ontology.    (186J)
    • Provide Centralized Data Storage.    (186K)
      • Ontology metadata (ontology metadata includes the source, date, version number and other core metadata as defined by appropriate standards bodies).    (186L)
      • OWL ontology.    (186M)
      • RDF store.    (186N)
      • Linkage to XML and database data and documents.    (186O)
    • Metrics and Logging Requirements.    (186P)
      • Provide data access metrics.    (186Q)
      • Provide data storage metrics.    (186R)
      • Provide audit logs of repository activity.    (186S)
    • Provide User Services via a Web Interface to.    (186T)
      • Search metadata indices.    (186U)
      • Link from the metadata index to the specific OWL or RDF storage location.    (186V)
      • Browse repository contents.    (186W)
      • Provide visual representation of ontologies.    (186X)
      • Search RDF instance stores with ontology-assistance.    (186Y)
      • Specify agent-directed searches of instance store content.    (186Z)
    • Machine User Services.    (1870)
      • Query repository and triples store using a conceptual query language, such as SPARQL.    (1871)
      • Query the repository and triples store using REST.    (1872)
      • Query the repository and triples store using SOAP.    (1873)
      • Use an API to programmatically create, view, and modify repository contents.    (1874)
      • Define machine services in appropriate machine-interpretable format, such as OWL-S.    (1875)
    • Provide a Repository of Downloadable Web Tools.    (1876)
      • Define a process with criteria for determining what kinds of tools to make available.    (1877)
      • Provide an index to available tools.    (1878)
      • Provide search capability to available tools.    (1879)
    • Validation Requirements.    (187A)
      • Validate an OWL ontology to ensure that it is valid OWL.    (187B)
      • Confirm the RDF against its terminology defined in RDFS.    (187C)
    • OWL Services.    (187D)
      • Browsing Services.    (187E)
      • Query Services.    (187F)
      • Indexing Services.    (187G)
        • Provides services for external search engines and entity extractors to index and mine repository contents.    (187H)
      • Visualization Services.    (187I)
      • Edit Services.    (187J)
      • Validation Services.    (187K)
      • Annotation Services.    (187L)
      • Web-Page Markup.    (187M)
      • Semantic Search Services.    (187N)
      • Crawl and Index.    (187O)
        • OWL Semantic Search Services crawl and index OWL content on the Web. Users submit logical queries which are answered with exact data. It can broaden queries with simple inference, such as equivalence, inversion, generalization and specialization.    (187P)
    • Reasoning Services.    (187Q)
      • Provide services to check ontology consistency, build classification, verify concepts’ satisfiability and check entailment.    (187R)
      • Provide services to support rules and execute minimally automated deductive reasoning and proof.    (187S)
    • Import Services.    (187T)
      • Support importing of modular ontologies into larger ontologies; this is at least partially a function of the knowledge representation language itself.    (187U)
    • Semantic Mapping Services.    (187V)
      • Schema Translation.    (187W)
        • Automatically generate translation code between database schemas with an OWL mapping specification.    (187X)
      • Visually-aided Mapping.    (187Y)
        • A user would generate a mapping between an existing ontology and the ontology expected by the custom visualization tool. The data would then be translated according to the mappings. The resulting data can then be viewed by the custom visualization tool.    (187Z)
      • Disambiguation.    (1880)
        • A user would generate a mapping between multiple ontologies to identify where classes and properties are the same. The data from multiple sources could then be imported into a repository where a reasoning tool can determine what objects are the same. The results could then be viewed in a browser.    (1881)
    • Ontology and Instance Versioning Services.    (1882)
      • Provide services to support semantic versioning of ontologies and knowledge bases (instances).    (1883)
    • Terminology to Concept Mapping Services.    (1884)
      • Provide services to support mapping user terminology to the concepts that represent the meaning of that terminology, using thesauri, lexicons, and other terminological resources.    (1885)
  • Conceptual high-level Requirements of an RDF/OWL Repository:    (1THO)
    • Allows authors to create ontology content and store it in a "local" repository    (188A)
    • Allow communities to manage a shared "community" repository    (188B)
    • Provide a "root" repository that keeps tracks of community repositories and provides the most universal ontology content and metadata    (188C)
    • Supports a maven like distributed model where content from "local" repository may be "deployed" to the "community" repository or the "root" repository    (188D)
    • Allows standard and extensible metadata to be associated with Ontology elements    (188E)
    • Supports flexible search mechanism where domain and community specific parameterized queries may be defined for metadata based searches    (188F)
    • Supports flexible subscription and notification feature to keep interested parties notified of changes to artifacts    (188G)
    • Supports automatic cataloging of published artifacts    (188H)
    • Supports automatic rule-based validation of submitted artifacts    (188I)
    • Supports different life cycle states for ontological content and provides a process for transitioning from one state to the other in a controlled manner. Note that the notification feature would notify interested parties of such state changes.    (1899)
    • Maintains change history for all artifacts in repository    (188J)
    • Supports a set of minimal authentication mechanisms (e.g. Basic, HTTPS mutual, OpenId)    (188K)
    • Provide fine grained role-based access control and authorization over all actions    (188L)
    • Support seamless search over multiple repositorys (local + community, local + community + root, other...)    (188M)

Proposed for Adoption    (1845)

... (enter proposed items here)    (1HTM)

Ideas & Candidates    (1847)

... (enter ideas and candidates below)    (1848)

• Candidate01 - proposed by LeoObrst/2008.01.03    (1849)
  • slides #7~11 from the planning meeting slide deck:    (184A)
  • Functional Requirements of an RDF/OWL Repository:    (186D)
    • Provide Capability to Submit an Ontology to the Repository.    (186F)
      • Extract administrative and descriptive data from the metadata fields of an OWL ontology.    (186G)
        • Metadata should follow existing metadata standards.    (186H)
        • Submitted items should be tracked with version numbers (after determining the levels of granularity needed for versioning).    (186I)
        • Generate a meta-card entry for the ontology.    (186J)
    • Provide Centralized Data Storage.    (186K)
      • Ontology metadata (ontology metadata includes the source, date, version number and other core metadata as defined by appropriate standards bodies).    (186L)
      • OWL ontology.    (186M)
      • RDF store.    (186N)
      • Linkage to XML and database data and documents.    (186O)
    • Metrics and Logging Requirements.    (186P)
      • Provide data access metrics.    (186Q)
      • Provide data storage metrics.    (186R)
      • Provide audit logs of repository activity.    (186S)
    • Provide User Services via a Web Interface to.    (186T)
      • Search metadata indices.    (186U)
      • Link from the metadata index to the specific OWL or RDF storage location.    (186V)
      • Browse repository contents.    (186W)
      • Provide visual representation of ontologies.    (186X)
      • Search RDF instance stores with ontology-assistance.    (186Y)
      • Specify agent-directed searches of instance store content.    (186Z)
    • Machine User Services.    (1870)
      • Query repository and triples store using a conceptual query language, such as SPARQL.    (1871)
      • Query the repository and triples store using REST.    (1872)
      • Query the repository and triples store using SOAP.    (1873)
      • Use an API to programmatically create, view, and modify repository contents.    (1874)
      • Define machine services in appropriate machine-interpretable format, such as OWL-S.    (1875)
    • Provide a Repository of Downloadable Web Tools.    (1876)
      • Define a process with criteria for determining what kinds of tools to make available.    (1877)
      • Provide an index to available tools.    (1878)
      • Provide search capability to available tools.    (1879)
    • Validation Requirements.    (187A)
      • Validate an OWL ontology to ensure that it is valid OWL.    (187B)
      • Confirm the RDF against its terminology defined in RDFS.    (187C)
    • OWL Services.    (187D)
      • Browsing Services.    (187E)
      • Query Services.    (187F)
      • Indexing Services.    (187G)
        • Provides services for external search engines and entity extractors to index and mine repository contents.    (187H)
      • Visualization Services.    (187I)
      • Edit Services.    (187J)
      • Validation Services.    (187K)
      • Annotation Services.    (187L)
      • Web-Page Markup.    (187M)
      • Semantic Search Services.    (187N)
      • Crawl and Index.    (187O)
        • OWL Semantic Search Services crawl and index OWL content on the Web. Users submit logical queries which are answered with exact data. It can broaden queries with simple inference, such as equivalence, inversion, generalization and specialization.    (187P)
    • Reasoning Services.    (187Q)
      • Provide services to check ontology consistency, build classification, verify concepts’ satisfiability and check entailment.    (187R)
      • Provide services to support rules and execute minimally automated deductive reasoning and proof.    (187S)
    • Import Services.    (187T)
      • Support importing of modular ontologies into larger ontologies; this is at least partially a function of the knowledge representation language itself.    (187U)
    • Semantic Mapping Services.    (187V)
      • Schema Translation.    (187W)
        • Automatically generate translation code between database schemas with an OWL mapping specification.    (187X)
      • Visually-aided Mapping.    (187Y)
        • A user would generate a mapping between an existing ontology and the ontology expected by the custom visualization tool. The data would then be translated according to the mappings. The resulting data can then be viewed by the custom visualization tool.    (187Z)
      • Disambiguation.    (1880)
        • A user would generate a mapping between multiple ontologies to identify where classes and properties are the same. The data from multiple sources could then be imported into a repository where a reasoning tool can determine what objects are the same. The results could then be viewed in a browser.    (1881)
    • Ontology and Instance Versioning Services.    (1882)
      • Provide services to support semantic versioning of ontologies and knowledge bases (instances).    (1883)
    • Terminology to Concept Mapping Services.    (1884)
      • Provide services to support mapping user terminology to the concepts that represent the meaning of that terminology, using thesauri, lexicons, and other terminological resources.    (1885)

• Candidate02 - proposed by FarrukhNajmi/2008.01.24    (1849)
  • ref. http://ontolog.cim3.net/forum/oor-forum/2008-01/msg00033.html    (1887)
  • Farrukh's quick brain dump / 2008.01.24    (1888)
    • Allows authors to create ontology content and store it in a "local" repository    (188A)
    • Allow communities to manage a shared "community" repository    (188B)
    • Provide a "root" repository that keeps tracks of community repositories and provides the most universal ontology content and metadata    (188C)
    • Supports a maven like distributed model where content from "local" repository may be "deployed" to the "community" repository or the "root" repository    (188D)
    • Allows standard and extensible metadata to be associated with Ontology elements    (188E)
    • Supports flexible search mechanism where domain and community specific parameterized queries may be defined for metadata based searches    (188F)
    • Supports flexible subscription and notification feature to keep interested parties notified of changes to artifacts    (188G)
    • Supports automatic cataloging of published artifacts    (188H)
    • Supports automatic rule-based validation of submitted artifacts    (188I)
    • Supports different life cycle states for ontological content and provides a process for transitioning from one state to the other in a controlled manner. Note that the notification feature would notify interested parties of such state changes.    (1899)
    • Maintains change history for all artifacts in repository    (188J)
    • Supports a set of minimal authentication mechanisms (e.g. Basic, HTTPS mutual, OpenId)    (188K)
    • Provide fine grained role-based access control and authorization over all actions    (188L)
    • Support seamless search over multiple repositorys (local + community, local + community + root, other...)    (188M)

• Candidate03 - proposed by EvanWallace/2008.04.17    (1GCM)
  • ref. http://ontolog.cim3.net/forum/oor-forum/2008-04/msg00011.html    (1GCN)
  • Bare minimum requirements:    (1GCP)
    1. Need to support ontologies in at least OWL and Common Logic (CL).    (1GCQ)
  • Need to provide means for users to Discover content via browsing and query of exposed elements of the content and metadata related to that content.    (1GCR)
  1. Need to serve content reliably in an appropriate standard exchange form and using protocols associated with each content type.    (1GCS)
  2. Need to provide persistent and available access to this content and associated metadata for multiple versions as the content evolves.    (1GCT)
  • I would characterize requirements 1 and 2 as requirements on a Registry functionality and 3 and 4 as requirements on a Repository functionality of an OOR.    (1GCW)

• Candidate04 - proposed by ToddSchneider/2008.04.17    (1GCY)
  • ref. http://ontolog.cim3.net/forum/oor-forum/2008-04/msg00012.html    (1GCZ)
  • Goals of the Open Ontology Repository    (1GD0)
    • Provide an architecture and an infrastructure that supports the    (1GD1)
      1. Storing,    (1GD2)
      2. Sharing,    (1GD3)
      3. Searching,    (1GD4)
      4. Governance,    (1GD5)
      5. Management of Ontologies.    (1GD6)
    • Requirements, High Level Assumptions    (1GD8)
      1. Not all capabilities will be implemented at any single version.    (1GD9)
      2. The architecture will evolve. There will be multiple versions each successor implanting additional capabilities and/or evolving the previous version.    (1GDA)
      3. Instance data, which are themselves not ontologies, will not be stored in the repository    (1GDB)
      4. The repository will meet the needs of operational or commercial systems.    (1GDC)
      5. Applicable standards will be used.    (1GDD)
    • General    (1GDE)
      1. The repository architecture shall be scalable    (1GDF)
      2. The repository shall be distributed.    (1GDG)
      3. The specification of the repository shall be sufficiently detailed and platform independent to allow multiple implementations.    (1GDH)
      4. The repository shall be capable of supporting ontologies in languages that have reasoners.    (1GDI)
      5. The repository architecture shall support distributed repositories.    (1GDJ)
      6. The repository architecture shall not require a hierarchical structure.    (1GDK)
    • Discovery    (1GDL)
      1. The repository shall provide metadata capabilities to support    (1GDM)
         1. search capabilities,    (1GDN)
         2. governance process,    (1GDO)
         3. management    (1GDP)
      2. The repository shall provide a content discovery mechanism that supports discovery by    (1GDQ)
         1. domain    (1GDR)
         2. author/creator/source    (1GDS)
         3. version    (1GDT)
         4. usage    (1GDU)
         5. language    (1GDV)
         6. terminology    (1GDW)
         7. quality    (1GDX)
    • Search    (1GDY)
      1. The repository shall provide a capability to    (1GDZ)
         1. search locally    (1GE0)
         2. search globally    (1GE1)
      2. The repository shall provide a capability to browse a repository    (1GE2)
         1. locally    (1GE3)
         2. globally (011)    (1GE4)
    • Subscription / Notification    (1GE5)
      1. The repository shall provide the ability for a user to subscribe to/for alerts associated with one or more repository items.    (1GE6)
      2. The repository shall provide the ability for a user to subscribe to/for automatic updates of one or more repository items.    (1GE7)
    • Management    (1GE8)
      • The repository shall provide a mechanism to enforce access policies    (1GE9)
      1. The repository shall provide a mechanism to enforce submission policies    (1GEA)
      2. The repository shall provide a mechanism to enforce governance policies    (1GEB)
      3. The repository shall provide a mechanism to enforce tracking policies    (1GEC)
      4. The repository shall provide a mechanism to create usage reports    (1GED)
      5. The repository shall provide syntax validation mechanisms    (1GEE)
      6. The repository shall provide a logical consistency checking mechanism    (1GEF)
      7. The repository shall provide a mechanism to automatically categorize a submission    (1GEG)
      8. The repository shall provide a mechanism to maintain state change of repository items (i.e. versioning)    (1HSD)
      9. The repository shall provide user and administrator access control mechanisms    (1GEI)
    • Governance    (1GEJ)
      1. The repository shall provide explicit machine usable/accessible repository semantics    (1GEK)
      2. The repository shall provide a mechanism to avoid intellectual property and related legal issues/problems    (1GEL)

• see: Proceedings from the Joint OpenOntologyRepository-OntologySummit2008 "Requirements Panel" sessions:    (1HSE)
  • 2008_03_27 - Thursday: Joint OOR-OntologySummit2008 Panel Discussion: "An Open Ontology Repository: Rationale, Expectations & Requirements - Session-1" - Chair: LeoObrst & FabianNeuhaus; Panelists: WilliamBug, EvanWallace, JohnLMcCarthy, KenBaclawski, PeterBenson & RexBrooks - ConferenceCall_2008_03_27 T    (1HSF)
  • 2008_04_03 - Thursday: Joint OOR-OntologySummit2008 Panel Discussion: "An Open Ontology Repository: Rationale, Expectations & Requirements - Session-2" - Chair: LeoObrst & FabianNeuhaus; Panelists: DougLenat, DekeSmith, MarciaZeng, DeniseBedford, PatHayes, MalaMehrotra & RobRaskin - ConferenceCall_2008_04_03 T    (1HSG)

• see the OOR Presentation by this team on 29-Apr-2008 at the OntologySummit2008 F2F workshop.    (1HSK)
  • note, in particular, slides #8 to #43    (1HSL)

• see: the OntologySummit2008_Communique    (1HSC)

• see: OpenOntologyRepository_UseCases    (189F)