Protege Server design

From Protege Wiki

Revision as of 11:24, September 13, 2013 by Tredmond (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Protege Server Design

Main concepts

The Protege OWL Server is loosely based on the ideas expressed in a paper that was a collaborative effort between Stanford University and the University of Manchester. The Protege OWL server presents a hierarchical arrangement of directories and evolving ontologies. Each evolving ontology in this hierarchical arrangement is represented as a sequence of revisions together with a collection of ontology changes that represent the change needed to take one revision to the next. Thus, for example, if a user wants to take an existing ontology and place it on the server, a client may perform the following steps

  • The client utilizes Protege OWL Server calls to navigate to the directory where she wants to place the original version of her ontology.
  • The client creates an ontology document in that directory. This ontology document will initially have only one revision and if the ontology at that revision is retrieved it will be empty; it will not even have a name.
  • The client commits all those changes to the ontology document to bring it from its empty document status to the ontology that the client wishes to put on the server. At this point the server will contain those

The core idea is that the server provides the abstraction of an evolving ontology through calls that provide the changes made to an ontology between any two revisions. Thus, for any ontology, the first revision of the ontology will be empty - it will not even have a name. Then in many cases the delta between the first and second contains all the changes needed to take the empty ontology to what the end user views as his initial version of the ontology.

Plugin Model


Protege Server Modules

Ontology Serialization

Personal tools