[rdfweb-dev] MeNowDocument proposed FOAF extension
ldodds at ingenta.com
Wed May 12 10:52:43 UTC 2004
Joel De Gan wrote:
> we put together the following FOAF extension:
> comments/critiques etc. welcome. please send to me as I am maintaining
> all pages on peoplesdns.
It'd be nice to see domain and ranges for all of these properties
as it'll help clarify the overlaps with other vocabularies.
The schema also declares these properties as "subPropertyOf"
foaf:Person. This is incorrect they should have a rdfs:domain
of foaf:Person, and then be a subPropertyOf other existing terms,
e.g. gameNick and ircNick should be a subPropertyOf foaf:nick
Also version indicators ("stable", "testing") as embedded in FOAF schema.
More specific comments:
* "listeningTo" -- I'd prefer to see more structure here rather than
a literal, e.g. MusicBrainz Track class.
There's a lot of activity relating to playlist description
(they're veering away from RDF sadly), would be nice to have them
tie up. i.e. not just what track I'm on, but what my playlist is.
* What's the difference between me:workingOn and foaf:currentProject?
Presumably it's related to time (i.e. I've got several current
projects on the go, but this is what I'm working on this second...)
* me:reading, c.f: http://purl.org/net/schemas/book
* me:liking: I don't understand that term
* me:workingOn: the example shows it being used as simple literal, but
also with structure (foaf:currentProject). This suffers from the same
problem as dc:creator, I'd prefer to see more rigid definitions e.g.
it's either definitely a literal or a resource.
* Lots of terms describe activities: eating, reading, watching,
chatting, writing, browsing, playing. Why not have an xx:Activity
class with subclasses for different types of activity. These can
then have their own properties, e.g. where am I eating or playing?
An xx:activity class could be used to relate a Person to one or more
I also wonder about the real utility of some of these properties.
Who is really going to have a keyboard to hand to mark up what they're
currently thinking, eating, talking to, standing near, etc.
Some of the properties are obviously self-contained so could be factored
out into smaller specs, e.g. all of the gaming data. I'm not a big
fan of lots of tiny namespaces, but there's seems several conceptual
groupings here: online presence, real-world presence, activities,
gaming. Taking these forward separately seems like a simpler goal as
it'll be easier to get buy in from particular communities.
More information about the foaf-dev