Also is a sample link to a publicly accessible profile in each network
that exhibits the use of XFN (or FOAF).
To see how XFN is being used, type in the link on your browser, in the
browser menu select View >> Page Source, and then search for: rel=
David, I was not able to find any pages on Vox that use XFN, can you
provide a sample link?
Everyone, if you know of other social networks using XFN please let me
know and I will add it to the list. Thanks!
SOCIAL NETWORKS THAT USE XFN
1. Flickr http://www.flickr.com/people/tracylee/
2. Last.fm http://www.last.fm/user/fbellintani/?scrobbling=t1
3. Ma.gnolia http://ma.gnolia.com/people/apartness
4. MetaFilter http://www.metafilter.com/usercontacts/292
5. Pownce http://pownce.com/ariel/
6. Twitter http://twitter.com/t
Below is a list of social networks that use FOAF.
To see how FOAF is being used, type in the link on your browser, in the
browser menu select View >> Page Source.
Everyone, if you know of other social networks using FOAF please let me
know and I will add it to the list. Thanks!
SOCIAL NETWORKS THAT USE FOAF
1. Advogato http://www.advogato.org/person/connolly/foaf.rdf
2. boards.ie http://www.boards.ie/vbulletin/foaf.php?u=4
3. Buzznet http://lomac.vox.com/profile/foaf.rdf
4. CrazyLife
http://www.crazylife.org/users/gothicxflower/data/foaf
5. DeadJournal http://tadydid.deadjournal.com/data/foaf
6. Ecademy
http://www.ecademy.com/module.php?mod=network&op=foafrdf&uid=2006
7. Elgg http://elgg.org/katarinam/foaf
8. FilmTrust
http://trust.mindswap.org/cgi-bin/FilmTrust/foaf.cgi?user=golbeck
9. GreatestJournal http://luckygmusic.greatestjournal.com/data/foaf
10. hi5 http://api.hi5.com/rest/profile/foaf/39290024
11. InsaneJournal http://ford.insanejournal.com/data/foaf
12. LiveJournal http://danbri.livejournal.com/data/foaf
13. My OpenLink
http://myopenlink.net/dataspace/person/kidehen/foaf.rdf
14. MyOpera http://my.opera.com/kjetilk/xml/foaf
15. Pownce http://pownce.com/adactio/foaf/
16. Vox http://lomac.vox.com/profile/foaf.rdf
/Roger
_______________________________________________
microformats-discuss mailing list
microforma...@microformats.org
http://microformats.org/mailman/listinfo/microformats-discuss
--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
http://www.onaswarm.com
http://www.onamine.com
> Hi Folks,
>
> Below is a list of social networks that use XFN (special thanks to
> David Janes). Following that is a list of social networks that use
> FOAF.
Why email these, why not just put them on the wiki?
-ryan
--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
http://www.onaswarm.com
http://www.onamine.com
Also is a sample link to a publicly accessible profile in each network
2. Last.fm http://www.last.fm/user/fbellintani/?scrobbling=t1
3. Ma.gnolia http://ma.gnolia.com/people/apartness
4. MetaFilter http://www.metafilter.com/usercontacts/292
5. Pownce http://pownce.com/ariel/
6. Twitter http://twitter.com/t
1. Advogato http://www.advogato.org/person/connolly/foaf.rdf
2. boards.ie http://www.boards.ie/vbulletin/foaf.php?u=4
3. Buzznet http://lomac.vox.com/profile/foaf.rdf
4. CrazyLife
http://www.crazylife.org/users/gothicxflower/data/foaf
5. DeadJournal http://tadydid.deadjournal.com/data/foaf
6. Ecademy
http://www.ecademy.com/module.php?mod=network&op=foafrdf&uid=2006
7. Elgg http://elgg.org/katarinam/foaf
8. FilmTrust
http://trust.mindswap.org/cgi-bin/FilmTrust/foaf.cgi?user=golbeck
9. GreatestJournal http://luckygmusic.greatestjournal.com/data/foaf
10. hi5 http://api.hi5.com/rest/profile/foaf/39290024
11. InsaneJournal http://ford.insanejournal.com/data/foaf
12. LiveJournal http://danbri.livejournal.com/data/foaf
14. MyOpera http://my.opera.com/kjetilk/xml/foaf
15. Pownce http://pownce.com/adactio/foaf/
16. Vox http://lomac.vox.com/profile/foaf.rdf
/Roger
_______________________________________________
I should be able to generate a more
complete list of sites that use XFN --- including the types of
relationships found on each --- some time tonight. ~D
me 65.46%
friend 31.82%
met 20.81%
colleague 19.56%
co-worker 14.46%
contact 11.15%
neighbor 5.00%
co-resident 4.45%
sweetheart 3.72%
sibling 3.03%
spouse 2.85%
muse 2.79%
parent 2.25%
crush 1.86%
kin 1.83%
date 1.12%
child 1.12%
acquaintance 0.14%
Out of a sample of ~15M pages with XFN, the following XFN rels are used,
in order of frequency. (That is, one page gets one vote for an XFN rel
used somewhere on the page.)
me 71.051%
friend 22.403%
colleague 13.929%
met 13.247%
co-worker 11.306%
contact 11.182%
neighbor 3.618%
co-resident 2.940%
parent 2.698%
sweetheart 2.094%
muse 1.707%
spouse 1.652%
sibling 1.398%
crush 1.073%
kin 0.942%
acquaintance 0.641%
date 0.612%
child 0.603%
So, while a large number of sites that use XFN do have "me" somewhere,
35% don't. Furthermore, while the statement by Chris Messina[1] is
corrent in asserting that "me" and "contact" are widely used, it is not
based on solid research.
The above data indicates that "contact" is not nearly as supreme as
"me," which is in a different league altogether. On the contrary,
"friend," "met," "colleague," and "co-worker" are at least as widely
used as "contact." The discrepancy appears to be bias towards the short
head of the usage curve.
Furthermore, I don't think anyone has really done a survey of
non-English usage. I certainly haven't. Many of the sites that I've
found that do use more than "me" are non-English, but certainly should
not be discounted.
Here is a random sampling of sites that do use XFN and the rels are used
by each in the last six months and are in the long tail.
ziki.com colleague friend me met muse spouse
topspeed.com contact friend
birdz.sk friend me neighbor
pushhit.com met
majoke.com co-worker friend met
bloguje.cz child co-resident co-worker colleague contact crush date
friend kin me met muse neighbor parent sibling spouse sweetheart
11870.com contact me
inter.co.yu co-resident colleague contact friend me met neighbor
finaltr.com friend muse
tractorfan.nl colleague kin me
botonturbo.com co-resident colleague contact friend me met
tecnosquad.com acquaintance co-resident colleague contact friend me met
giovani.it child date friend me met muse
wolkanca.com co-resident co-worker contact crush date friend me met
muse spouse sweetheart
~D
[1]
http://factoryjoe.com/blog/2008/03/11/portable-contact-lists-and-the-case-against-xfn/
Thanks!
/Roger
I learned that from now on, I should always include the value contact,
on top of all other values. XFN exists for more than just contact list
portability...
--
André Luís
If you use Google’s new Social Graph API
<http://code.google.com/apis/socialgraph/> and actually go looking
for XFN data (for example, on Twitter or Flickr or others
<http://microformats.org/wiki/xfn-implementations>), you’ll find
that, by and large, the majority of XFN links on the web are using
either |rel-contact| or |rel-me|.
If you’re lucky, you might find some |rel-friend|s in there, but
after rel-me and rel-contact, the use of the other 16 terms falls
off considerably. Compound that fact with the minor semantic
distinction between “contacts” and “friends” on different sites
(sites like Dopplr dispense altogether with these terms, opting for
“fellow travelers”) and you quickly begin to wonder if the “semantic
richness” of XFN is really just “semantic deadweight”.
And, in terms of evangelism and potential adoption, this is
critical. If 16 of the 18 XFN terms are just cruft, how can we
maintain our credibility [?] ...
So, with that, I’m no longer going to both with advocating for the
complete adoption of XFN. Instead, I’m going to advocate for
supporting /Contact List Portability/ by implementing rel-me and
rel-contact (a “subset” of XFN).
The above, taken from his post --- though his blog software appears to
be having issues right now --- says that
1.) He positively asserts that if YOU look at Twitter, Flickr, and a
handful of other sites, you will see that they do use rel-me and
rel-contact.
2.) He negatively asserts that you might find others XFN rels in the
wild but probably not because they aren't used.
3.) Therefore, XFN sans rel-me and rel-contact is cruft and should be
dropped in favor of just rel-me and rel-contact.
Statement #1 is flawed because the corpus is not representative; it's a
look at sites that were already known to use those formats. My numbers
(taken from a current, large web corpus) indicate that #2 is false
across the web-at-large. Therefore, I find it hard to support his
conclusion. ~D