oor architecture and api take ii n.
Download
Skip this Video
Download Presentation
OOR Architecture and API – Take II

Loading in 2 Seconds...

play fullscreen
1 / 4

OOR Architecture and API – Take II - PowerPoint PPT Presentation


  • 101 Views
  • Uploaded on

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.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'OOR Architecture and API – Take II' - cara-jacobs


Download Now 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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
oor architecture and api take ii

OOR Architecture and API – Take II

Ken Baclawski

Michael Gruninger

Co-Chairs

slide2

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

slide3

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

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