We suggest replacing the two mapping rules: NegativeDataPropertyAssertion( DPE a lt ) => _:x rdf:type owl:NegativePropertyAssertion . _:x owl:sourceIndividual T(a) . _:x owl:assertionProperty T(DPE) . _:x owl:targetValue T(lt) . And NegativeObjectPropertyAssertion( OPE a1 a2 ) => _:x rdf:type owl:NegativePropertyAssertion . _:x owl:sourceIndividual T(a1) . _:x owl:assertionProperty T(OPE) . _:x owl:targetIndividual T(a2) . We suggest the following alternative to the second one (the first is similar): NegativeObjectPropertyAssertion( OPE a1 a2 ) => T(a1) rdf:type _:c . _:c rdf:type owl:Class . _:c owl:complementOf _:r . _:r rdf:type owl:Restriction . _:r owl:onProperty T(OPE) . _:x owl:hasValue T(a2) . The merits are: a) reduces need for additional vocabulary b) makes it clear that this is an advanced feature that is unlikely to be interoperability supported Jeremy Carroll, AC Rep, TopQuadrant, Inc.Received on Tuesday, 12 May 2009 22:27:36 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:40:21 UTC