Simon Spero
Fri, 19 Jun 2009 09:06:21 -0700
On Thu, Jun 18, 2009 at 4:10 PM, Jon Phipps <jphi...@madcreek.com> wrote:
> Folks, > > I'm looking for some community advice on how to best model this situation: > > The RDA spec says that the rda:extent property applies to both > frbr:manifestation and frbr:item. Without getting into a discussion of > whether that's correct, I'm interested in the best way to model that. It > looks like there are at least a couple of options... > In ACE <http://attempto.ifi.uzh.ch/site/tools/> notation Everything that v:extent something is something that is an item or that is a manifestation . This can be represented as a domain constraint (using the OWL2 functional notation). ObjectPropertyDomain(extent ObjectUnionOf(manifestation item)) APE <http://attempto.ifi.uzh.ch/ape/> suggests a class axiom ( SubClassOf(ObjectIntersectionOf(ObjectSomeValuesFrom(extent owl:Thing) owl:Thing) ObjectIntersectionOf(ObjectUnionOf(manifestation item) owl:Thing)) i.e. SubClassOf(ObjectSomeValuesFrom(extent owl:Thing) ObjectUnionOf(manifestation item)) Pellet and Fact++ can both infer the domain constraint from the class axiom,but only if there is some existing item-or-manifestation class. Fact++ can also infer ranges, something pellet refuses. In general I'd go with the ObjectPropertyDomain Simon