Thx very much for your consideration. In NL were working on a national
modeling guide in which linking classes properties is an important
issue (typically difficult/different for many involved since it
differs from tradiotional modeling approaches).
In my *personal* opinion you may also
Also *personal* opinion :-)
The main characteristics of OO (i.e.polymorphism, encapsulation, information
hiding) are really not applicable to OWL as they are specifications about
behaviour, not data. OWL is data with no defined behaviour and so not really OO
IMPO. I guess you can think of OO
All aspects of object orientation (encapsulation, inheritance, and
polymorphism) apply equally to class members and methods. In OWL/RDF we
have class inheritance but we don't have the structure of a class such as
we do in programming languages. The triple of S-P-O is a very simple
structure,
Actually, it is the other way around. Restriction on a class applies to all of
its subclasses, domain or range declarations don't necessarily apply to all
subclasses.
This is according to the standard semantics. However, in practical use, people
typically only say that a property is in a
