------- Original message -------
From: Paul Hermans <[log in to unmask]>
Sent: 20/12, 12:04
> OK, If I understand well. The class "Agent" defines a group of resources
> that (are able to) act.
>
> As such, it is a group of agents, hence an instance of an AgentClass, in
> this case the group of all (potential) agents.
>
> My next question is: what is the added value of doing this?
Note that AgentClass and Agent are used as ranges for different properties.
(audience and creator, respectively). I think the modeling is sane here.
>
> Maybe I'm also a little bit confused, since in an OWL DL context the rule
is
> "that we cannot use classes as instances, i.e.
>
Experiences from OWL implementations are more than welcome. This aspect of
OWL is a limitation I have never understood how to deal with...
/Mikael
> x rdf:type owl:Class
> y rdf:type owl:Class
> x rdf:type y
>
> is not valid OWL DL.
>
> A general rule here is that if there is a node x in the graph with a
triple:
> x rdf:type owl:Class
> then x should not appear as the subject of any other triple involving
rdf:type."
>
> But maybe this is one of the subtle differences between RDFS and the
several
> flavours of OWL that I'm still not able to grasp completely.
>
> b) maybe another small issue encountered.
> dcterms:type doesn't seem to be defined as subPropertyOf dc:type in
dcterms.rdf
>
>
> My
> >
> >[1] http://dublincore.org/documents/2007/07/02/domain-range/
> >
> >--
> >Dr. Thomas Baker <[log in to unmask]>
> >Director, Specifications and Documentation
> >Dublin Core Metadata Initiative
>
|