[seek-kr-sms] property restrictions in growl

[Rich Williams]

>
>
> In a graphical editor such as GrOWL, I don't think as a user, I would
> want to necessarily have to follow OWL to construct a model. If I draw a
> line between two classes, name it, and give the property restrictions,
> then that should both create the property and the restriction ... or
> maybe I am missing something. Also, some "restrictions" are defined at
> the property-level and some per class -- but as a user, you shouldn't
> have to worry about these two "modes".
>

Shawn is raising a very important user interface issue.  Right now, the user
interface of GrOWL, like the Protege OWL plugin, is very close to OWL.
Typically, one operation creates one OWL entity, so you create a property as
one operation, and a restriction on the property as another operation.
Shawn gives an example in which a series of operations that create multiple
objects in the graph model could usefully be combined into a single user
action.  One future step in developing GrOWL should be to identify sequences
like this and represent them as primitive operations in the user interface.
I think of the current user interface as analogous to programming in
assembly language.  It is useful and a necessary step on the way to a
higher-level user interface, rather than the final word on OWL browsing or
editing.

Rich