Search Mailing List Archives

Limit search to: Subject & Body Subject Author
Sort by: Reverse Sort
Limit to: All This Week Last Week This Month Last Month
Select Date Range     through    

[protege-discussion] Protege Frames - ideas on implementing missing features?

Jens Selbach Jens.Selbach at
Mon Feb 26 01:48:27 PST 2007


protege frames is an outstanding application, though it's primary scope
seems to support
editing of ontologies by few people. For maintaining ontologies by many
users with write
access, some features are missing often found in other applications:

- fine graded access control (role model for users)
- enforced input validation
- control of read-only attributes
- view change history
- info on who created instances, when was it created, when was it

Solutions for some of these requirements can be found on the net.
Starting a new project,
I would like to find out what is the best way to implement these
features now with protege 3.x
but also look at the upcoming version 4.

some access control can be achieved by client server mode in protege
3.x. Separates write users 
from read only users. 
I'd like to decide write access by protege class or even by protege
instances, e.g. if a
user (represented by a instance of class Person) is linked to that

change history, change control:
ChangeTab has all the information, but it's hard to read. I'd like to
see change history in
context of a single instance, e.g. a button "view history" within the
instance form.

To maintain a vaild ontology and allow many users editing, would it be a
good idea to 
allow users to make changes to a copy of the ontology and then apply
these changes to
a controlled ontology by a responsible change manager through PROMPT
plugin e.g. once per day? 
This could  prevent users from deleting large parts of the ontology.
Could be a workaround, 
if strict access control policies can no be enforced through the

The solution by Java Function Calls seems to be an interesting framework
extending features
of protege ( ) and might

Thank's for any comments.

More information about the protege-discussion mailing list