1 / 4

OOR Architecture and API – Take II

OOR Architecture and API – Take II. Ken Baclawski Michael Gruninger Co-Chairs. OOR Requirements. The repository architecture shall be scalable. The repository shall be distributed.

cara-jacobs
Download Presentation

OOR Architecture and API – Take II

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OOR Architecture and API – Take II Ken Baclawski Michael Gruninger Co-Chairs

  2. OOR Requirements • The repository architecture shall be scalable. • The repository shall be distributed. • The specification of the repository shall be sufficiently detailed and platform independent to allow multiple implementations. • The repository shall be capable of supporting ontologies in languages that have reasoners [supporting inferencing]. • The repository architecture shall support distributed repositories. • The repository architecture shall not require a hierarchical structure. http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_Requirement 2

  3. OOR Architecture • OOR requires an open and well documented architecture to • Allow multiple communities and organizations to participate in the OOR • Produce standard OOR functionalities and behaviors. • OOR Architectural Principles • Decoupling of responsibilities – To support multiple knowledge representations/languages repository will not be there tightly coupled with the content. • Implementation/Platform independence – To support acceptance, multiple instances, and evolution, no particular implementation or platform dependence can be allowed. • Ontologically driven – To allow for evolution of the OOR and reduce overall development costs, the use of an ontologically based development environment is sought. 3

  4. Panelists • Todd Schneider & Ken Baclawski • Gangemi & Adamou • Tuominen & Viljanen • D’Aquin • Chan

More Related