OOR Architecture and OOR Architecture and API – Take IIAPI – Take II

Ken BaclawskiKen Baclawski

Michael GruningerMichael Gruninger

Co-ChairsCo-Chairs

OOR RequirementsOOR Requirements The repository architecture shall be scalable.The repository architecture shall be scalable. The repository shall be distributed.The repository shall be distributed. The specification of the repository shall be The specification of the repository shall be

sufficiently detailed and platform independent to sufficiently detailed and platform independent to allow multiple implementations.allow multiple implementations.

The repository shall be capable of supporting The repository shall be capable of supporting ontologies in languages that have reasoners ontologies in languages that have reasoners [supporting inferencing].[supporting inferencing].

The repository architecture shall support distributed The repository architecture shall support distributed repositories.repositories.

The repository architecture shall not require a The repository architecture shall not require a hierarchical structure. hierarchical structure.

http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_RequirementRequirement 2

OOR ArchitectureOOR Architecture OOR requires an open and well documented OOR requires an open and well documented

architecture to architecture to Allow multiple communities and organizations to Allow multiple communities and organizations to

participate in the OOR participate in the OOR Produce standard OOR functionalities and behaviors. Produce standard OOR functionalities and behaviors.

OOR Architectural PrinciplesOOR Architectural Principles Decoupling of responsibilitiesDecoupling of responsibilities – To support multiple – To support multiple

knowledge representations/languages repository will not knowledge representations/languages repository will not be there tightly coupled with the content.be there tightly coupled with the content.

Implementation/Platform independenceImplementation/Platform independence – To support – To support acceptance, multiple instances, and evolution, no acceptance, multiple instances, and evolution, no particular implementation or platform dependence can be particular implementation or platform dependence can be allowed.allowed.

Ontologically drivenOntologically driven – To allow for evolution of the OOR – To allow for evolution of the OOR and reduce overall development costs, the use of an and reduce overall development costs, the use of an ontologically based development environment is sought.ontologically based development environment is sought.

3

PanelistsPanelists

Todd Schneider & Ken BaclawskiTodd Schneider & Ken Baclawski Gangemi & AdamouGangemi & Adamou Tuominen & ViljanenTuominen & Viljanen D’AquinD’Aquin ChanChan