[foaf-dev] Time to make the foaf classes relate to Dublin Core classes?

[Mikael Nilsson]

On ons, 2008-01-23 at 10:56 +0900, KANZAKI Masahide wrote:
> Hi Dan,
> 
> The dcterms:AgentClass is designed as domains of dcterms:audience,
> dcterms:mediator and dcterms:educationLevel. So it could be generic
> students, women, charities, lecturers etc (a class of Agents), but
> basically not a specific group (e.g. FOAF Project).
> 
> I guess foaf:Group is neither equivalentClass nor subClassOf dcterms:AgentClass.

I think this is right. I don't think the real difference is between
abstract vs concrete sets, though. There are a few other important
differences.

* Membership: An instance of dcterms:AgentClass uses (inverse) rdf:type
for membership, while foaf:Group uses foaf:member.

* foaf:Groups are not Classes

I think a dcterms:AgentClass can serve as the foaf:membershipClass of a
foaf:Group, though.

so, possibly, the range of foaf:membershipClass can be
dcterms:AgentClass??

/Mikael

> 
> 2008/1/23, Dan Brickley <danbrickley at gmail.com>:
> > I also wonder how well AgentClass maps to foaf:Group, ie.
> >
> > http://xmlns.com/foaf/spec/#term_Group
> > Group - A class of Agents.
> > "The foaf:Group class represents a collection of individual agents
> > (and may itself play the role of a foaf:Agent, ie. something that can
> > perform actions)."
> >
> > http://www.dublincore.org/documents/2008/01/14/dcmi-terms/#classes-AgentClass
> > "A group of agents."
> > "Examples of Agent Class include groups seen as classes, such as
> > students, women, charities, lecturers."
> >
> > Currently we don't say that Group is a subclass of class, which is how
> > AgentClass seems to work. But the basic idea is similar...
> 
-- 
<mikael at nilsson.name>

Plus ça change, plus c'est la même chose