OntologySummit2008 Communique Draft Review - "Repository Architecture" Breakout Group    (1GHP)

Ref: OntologySummit2008_Communique/Draft    (1GHQ)

The Team:    (1GHR)

Notes:    (1GHU)

The Architecture of a repository for enabling wide-scale knowledge searching and sharing of ontologies, must be open and extensible. The Architecture design should be modular in nature and provide for ontology storing, sharing, searching, governance, and management of the repository infrastructure and content.    (1GIP)

6.1 Architecture Approach    (1GIQ)

The core approach for the Open Ontology Repository is a federated architecture with the flavor of service oriented architectures. This approach provides for distributed ontology storage, repository management and service support.    (1GIR)

The overall assessment of the community is to enable open, distributed, federated repositories, and to provide metadata for each ontology registered, as well as providing connections for logical services, inference engines etc.    (1GIS)

Those who engage in the federation may include both open and closed content. All metadata required for sharing must be open. This metadata must include the access constraints.    (1GIT)

6.2 Core Requirements    (1GIU)

1. The repository architecture shall be scalable.    (1GIW)

2. The architecture shall be optimized for sharing, collaboration and reuse.    (1GIX)

3. The repository shall be capable of supporting ontologies in multiple formats and levels of formalism.    (1GIY)

4. The repository architecture shall support distributed repositories.    (1GIZ)

5. The repository architecture shall support explicit machine usable/accessible formal semantics for the metamodel of the repository    (1GJ0)

6. The repository shall provide a mechanism to address intellectual property and related legal issues/problems    (1GJ1)

7. The repository architecture shall include a core set of services, such-as, support of adding ontologies, searching, and tie-in of data related to the stored ontologies.    (1GJ2)

8. The repository architecture shall support additional services both directly within the province of the repository and as external services.    (1GJ3)

9. The repository should support all phases of the ontology lifecycle.    (1GJ4)

6.3 Repository Management    (1GJ5)

1. The repository shall provide a mechanism to enforce access policies    (1GJ6)

2. The repository shall provide a mechanism to enforce submission policies    (1GJG)

3. The repository shall provide a mechanism to enforce governance policies    (1GJH)

4. The repository shall provide a mechanism to enforce ‘tracking’ policies    (1GJI)

5. The repository should provide a mechanism to create usage reports    (1GJJ)

6. The repository should provide syntax validation mechanisms    (1GJK)

7. The repository should provide a logical consistency checking mechanism    (1GJL)

8. The repository should provide a mechanism to automatically categorize a submission    (1GJM)

9. The repository shall provide a mechanism to maintain state change of repository items (i.e. versioning)    (1GJN)

10. The repository shall provide user and administrator access control mechanisms    (1GJO)

6.4 Service and Application Support    (1GLT)

The services and applications that should be supported include:    (1GLU)

6.5 Discovery Support    (1GM3)

1. The repository shall provide metadata capabilities to support    (1GM4)

a. search capabilities,    (1GM5)

b. governance process,    (1GM6)

c. management    (1GM7)

2. The repository should provide a content discovery mechanism that supports discovery by    (1GM8)

a. domain    (1GM9)

b. author/creator/source    (1GMA)

c. version    (1GMB)

d. usage    (1GMC)

e. language    (1GMD)

f. terminology    (1GME)

g. quality    (1GMF)