COLLABORATIVE DEVELOPMENT OF LARGE - SCALE BIOMEDICAL ONTOLOGIES - Collaborative Computational Technologies for Biomedical Research - page 189

Figure 12.6 Metaproject ontology used to confi gure the Protégé server and the access
policies. The ICD project has several properties shown in the right-hand-side panel,
such as name, owner, location, access policies, and so on.
servers. The metaproject can be edited directly in the Protégé user interface
(Fig. 12.6) or can be edited while the server is running using the Server Admin
application.
The Protégé server supports three types of access policies: (1) project poli-
cies, (2) group policies, and (3) server policies, modeled as subclasses of the
PolicyControlledObject class in the metaproject. The project policies refer to
permissions set for a particular project. For example, for the ICD project, a
policy may say that only users from the group ICDGroup are allowed to write
to this project. The group policies apply to groups. For example, one policy
may state that only certain people are able to add users in this group. The
server policies apply to the Protégé server itself and pertain to more “admin-
istrative” types of permission. For example, one server policy might say that
only users from the Admin group are allowed to shut down the server.
The main classes in the metaproject ontology are shown in Figure 12.6. The
central class is the PolicyControlledObject that has as subclasses all types of
objects that can have policies attached to them (projects, groups, and servers).
The Operation class represents the different types of operations that can be
performed on the PolicyControlledObjects, such as Read and Write, Review,
Shutdown server, and so on. The User class represents the users of the Protégé
server, who are the performers of ontology operations. The screenshot in
Figure 12.6 shows an example of the ICD Project instance, which has several