W3C home > Mailing lists > Public > public-owl-dev@w3.org > July to September 2007

On classes and property permissions

From: Emanuele D'Arrigo <manu3d@gmail.com>
Date: Thu, 27 Sep 2007 10:38:23 +0100
Message-ID: <915dc91d0709270238h4554f6admba7c4510e5f84c5@mail.gmail.com>
To: "OWL developers public list" <public-owl-dev@w3.org>

Hi everybody,

another request for info and pointers to info pages.

Assuming I'm trying to build an OWL-based system
that allows users to edit not only the data but also
the ontologies themselves, are there estabilished
strategies to add metadata to the classes, properties
and their instances so that users are allowed or
disallowed to add/edit/delete stuff?

Think about this case for example:

- the ontology has a class "file"
- the class file has a property "size"
- the property "size" -should not- be user-editable
  bacause it's directly dependent on the actual
  size of the file stored elsewhere
- the class file has also a property "name"
- the property "name" -should- be editable because
  it is reasonable that a user might want to rename
  the actual file.
- however, only some users AND groups of users
  should be allowed to edit the value of this property
- additionally, nobody should be allowed to
  remove the class "file" nor the properties "size"
  and "name" from the ontology

Should all these axioms be stored in the ontology
so that whatever application manipulates the instances
can make use of them directly? Or should they be
instances themselves, of a separate "permission"
ontology somehow applied to the ontology "files"?
Or are there other options?

Thanks for your help!!!

Received on Thursday, 27 September 2007 09:38:32 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:58:15 UTC