Revision as of 01:39, 1 November 2007 by Admin (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)



current status: open

This is a FoafVocab issue, documented as such by linking it from the IssueTracker page.

A property for listing the person's mailing list, usenet and RSS news subscriptions. A use case is using it to minimise the number of crossposts when mailing.

  * Danny Ayer's weblog entry
  * Assigned To: danbri at
  * rdfweb-issue-archive

Something in this vein is useful. Quite how we do it probably needs more discussion. Many folk want to represent groups, such as the membership of a mailing list or other online community. In some cases we want to do that indirectly, eg. by indicating the sha1sum of the mailboxes of the listmembers, to avoid giving away too much information. So there may be a general notion of a 'Group' that gets defined alongside such machinery for picking out the group members.

One thing to explicitly avoid is any assumption that all group members 'read' each item sent to the list/newsgroup/etc. People will be wary of this, example might be if a patent claim is sent to a mailing list, we shouldn't assume each listmember reads each mailing list posting.

Perhaps we could afford some specific markup for email and news groups, and have foaf:subscriber_mbox or foaf:subscriber_mbox_sha1sum be properties of such groups? ( Danbri, 2003-02-07 00:40])

I'd much rather see a way for a group itself to express it's membership first and use that. Better to have a way for the concept of a 'group' to be defined and to express it's members. Then have a user's foaf state it's membership in said group as a bidirectional linking factor. This way the group's definition of being a mailing list might then infer than contacting members found across multiple groups might be wasteful. Especially if the groups can expose their own contacting mechanisms. (wkearney99 at 2003-02-28 21:05)