ldodds at ingenta.com
Wed Feb 4 10:40:42 UTC 2004
> Dan Brickley <danbri at w3.org> wrote:
> >class: foaf:PersonalProfileDocument (addition)
> Hmm, I guess the train has left the station on this, but I still don't
> see any compelling use cases...
1. Typing seeAlso links, so that one can traverse just those you're
interested in? This assumes that we might have other document classes
though. E.g image/book/music collection. (Not that having those classes
restricts the contents of the document in any way).
2. Adding PPD allows the location of a persons description to be part
of the RDF graph. At the moment it's not. We can then ask: where
is Morten's FOAF description. Presently we can just ask: which
documents mention Morten.
3. When loading a document into an editor (or viewer) we definitely
need at least primaryTopic to be able to explicitly identify the
main person being described. Neither foaf:topic nor foaf:maker, nor
the combination are really good enough.
We could probably get away with a heuristic for editors/viewers that
says: if the primaryTopic is a foaf:Person, then thats the one you're
editing. However as Dan pointed out if we have PPD then we can
also infer that the foaf:maker is the primaryTopic, as well as being
able to achieve the first two use cases outlined above.
>>property: foaf:primaryTopic (addition)
> >I intend to add a subpropertyOf foaf:topic called foaf:primaryTopic,
> >which is an InverseFunctionalProperty, ie. corresponds to the notion of
> >"the main topic" rather than "a topic".
> Please, pretty please, do not make this an IFP.
+1 on it being a Functional rather than InverseFunctionalProperty.
Can we say that PPD is a sub-class of foaf:Document, and that a
foaf:Document can have 1 primaryTopic?
More information about the foaf-dev