Additions to scope of OWL1.1

Bijan,
 
Is the scope definition of OWL1.1 closed, or are proposals for additions
still possible?
 
In the world of ISO 15926 we are struggling with the problem that in RDF we
cannot model something like:
 
    :Joe isFatherOf :Mary
    :Mary isInvolvedWith :Pete
    :Joe approves [:Mary isInvolvedWith :Pete]
 
Often it is necessary to say something about a relationship between two
individuals (relations involving relations, like above example), with the
requirement to constrain that in an OWL schema.
 
ISO 15926 uses classes for (binary) relationships. These classes have two
properties, the ranges of which coincide with the domain and range of an
owl:ObjectProperty. For example:
 
    :Mary isInvolvedWith :Pete
 
maps to:
 
    <Involvement rdf:ID="ME329800">
        <involved1 rdf:resource="#Mary"/>
        <involved2 rdf:resource="#Pete"/>
    </Involvement>
 
where any subsequent approval of this relationship can be done like:
 
    <Approval rdf:ID="ME324199">
        <approved rdf:resource="#ME329800"/>
        <approver rdf:resource="#Joe"/>
    </Approval>
 
We could use an ObjectProperty AND a Relationship class, but then we have no
way to tell that a particular instance of the one is semantically equivalent
to a particular instance of the other. It would require a.k.a. cross-over
between equivalentClass and equivalentProperty.
 
This may be way out of line for the OWL1.1 exercise. In that case I
apologize for taking your time.
 
Regards,
Hans
____________________
OntoConsult
Hans Teijgeler
ISO 15926 specialist
Netherlands
+31-72-509 2005
HYPERLINK "http://www.infowebml.ws/"www.InfowebML.ws 
HYPERLINK "mailto:hans.teijgeler@quicknet.nl"hans.teijgeler@quicknet.nl
 
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.14.14/547 - Release Date: 22-Nov-06
17:41