Re: enhancing Unambiguous to be domain-dependent

From: Ian Horrocks (
Date: 05/16/01


DAML+OIL can express this already. e.g., for UniqueProperty:

<daml:Class rdf:about="#Family">
    <daml:Restriction daml:maxCardinality="1">
      <daml:onProperty rdf:resource="#surName"/>

(i.e., every instance of Family has at most one name), and for

<daml:Class rdf:about="#Thing">
    <daml:Restriction daml:maxCardinalityQ="1">
        <daml:inverseOf rdf:resource="#surName"/>
      <daml:hasClassQ rdf:resource="#Family"/>

(i.e., every instance of Thing is the surName of at most 1 Family).

Please forgive any syntax errors (was going to try n3 but didn't have
time to check out the necessary details).

Note that I am not commenting on whether or not DAML+OIL needs to
provide this idiom directly.


On May 16, Dan Connolly writes:
> Just like we make a domain-dependent version
> of RDF's range, I'd like UniqueProperty
> and UnambiguousProperty to be domain-dependent;
> i.e. make them into properties that relate
> a property to a class.
> So I could say
> 	:surName ont:unambiguousOver :Family.
> This has come up before in my work; oh yeah...
> I specified it pretty carefully a while ago...
> [[[
> unambiugousOver is a class-specific form of daml:Unambiguous; in the
>      style of the DAML+OIL axiomatic semantics, the following is a
> specification for
>      it: 
>       (<=> (PropertyValue ?p unambiguousOver ?c) 
>                 (forall (?x ?y ?v) 
>                              (=> (and (Type ?x ?c) (Type ?y ?c)
>                                              (PropertyValue ?p ?x ?v) 
>                                       (PropertyValue ?p ?y ?v)) 
>                                  (= ?x ?y)))))
> ]]]
> --        Using XML Schema Datatypes in RDF and DAML+OIL
> Thu, 15 Feb 2001 22:23:12 GMT
> -- 
> Dan Connolly, W3C

This archive was generated by hypermail 2.1.4 : 04/02/02 EST