Are there parts of the FOAF vocabulary we should declare ‘core’, and stable (or stabilise)?
Would anyone be interested to help translate such a subset? initially the class/property labels and definitions, perhaps later, the accompanying per-term definitions? (a friend helped make a start on translating some terms into Persian, and there’s a neglected German translation lost in my 2004 mailbox somewhere too).
Are there terms which are more clutter than useful? Terms that could be relegated to an appendix? Or even (I’m wary of this) fully removed?
Are there Open Issues you’d particularly like to see addressed?
Also some practicalities: the mailing list hosting I use at the moment is hosed. There are a cluster of FOAF-related lists, of which email@example.com is the most important. I’m looking for alternate hosting, that has in particular got spam-control. I’ve been experimenting with Dreamhost’s mailman installation, but it doesn’t look up to the job.
Open ended question time: which bits of the FOAF vocab would you like to see get some more attention, improvement etc., first? In particular, what should we do about the naming parts? eg. defer to an improved vcard-in-rdf spec’d
elsewhere? How about the topic stuff and relationship to SKOS?
FOAF’s been having a little rest for a year or so, but it’s time to dust things down and see where a little time could most usefully be spent…
Thanks for any thoughts :)