|
List Info
Thread: A (big) problem with XFN: identity of source and target not findable
|
|
| A (big) problem with XFN: identity of
source and target not findable |
  United States |
2008-03-18 07:31:10 |
Hi Folks,
Flickr uses XFN. Here is a sample Flickr page that uses
XFN:
http://www.flick
r.com/people/tantek/
At the browser menu select View >> Page Source. Then
search for rel=
Here's an example usage of XFN within that Flickr page:
<a href="/photos/24172116 N08/"
rel="contact">
<img
src="http://farm3.static.flickr.com/2146/buddyicons/24172116
a> N08.jpg?12
03935044#24172116 N08"
alt="Jolene_A" width="48"
height="48" /><br />
Jolene_A
</a>
Notice the use of XFN: >>> rel="contact"
<<<
Metafilter also uses XFN. Here is a sample page that uses
XFN:
http://www
.metafilter.com/usercontacts/292
Here's an example usage of XFN within that page:
<a href="/user/10411" rel="colleague"
target="_self">40 Watt</a>
Notice the use of XFN: >>>
rel="colleague" <<<
Now, suppose that I wanted to create a spider application
which crawls
all social networks that use XFN. Most likely, I would want
the spider
to collect:
1. Who is the source? That is, who is the individual using
XFN to
state a relationship?
2. What is the relationship? This is, of course, obtained
easily from
the value of the rel attribute on the link.
3. Who is the target? That is, who is the other individual
in the
relationship?
Examine the above snippets of code. Does 1. and 3. pop out
at you?
That is, do you know who are the individuals that are the
source and
target of the relationship?
That information "can" be found on the Flickr and
Metafilter sites, but
each site does it *differently*.
So, the problem with XFN can be stated as this: While XFN
does a great
job of providing a set of relationship values (friend,
contact,
co-worker, etc), it provides no means for the automated
discovery of
the individuals that are the source and target of the
relationship.
Without information about the source and target individuals,
the
relationship information is not very useful.
You might argue: "Well, the XFN *should* be embedded
within an hCard,
then you can discover who the source individual is. And the
target
page should contain an hCard, then you can discover who the
target
individual is." And I agree that is Best Practice.
Unfortunately,
this is not mandated and consequently many people don't do
it. For
example, Flickr and Metafilter don't do it. Nor do any of
the other
social networks do it.
Conversely, consider FOAF. Advogato is a social network
that uses
FOAF. Here an example FOAF on that network:
http
://www.advogato.org/person/connolly/foaf.rdf
At the browser menu select View >> Page Source to see
the actual FOAF
document. Notice that the individual who is the source of
the
relationship is clearly listed at the top of the document:
<foaf:name>Dan Connolly</foaf:name>
And the individual who is the target of the relationship is
clearly
identified:
<foaf:knows>
<foaf:Person
rdf:about="http://www.advogato.org/person/jtauber/foaf.rdf#me&q
uot;>
<foaf:nick>jtauber</foaf:nick>
<rdfs:seeAlso
rdf:resource="http://www.advogato.org/person/jtauber/foaf.rdf"/
>
</foaf:Person>
</foaf:knows>
The downside of FOAF is the only built-in relationship is
"knows", e.g.
"Dan Connolly knows James Tauber." That is, FOAF
doesn't possess the
richness of expression in terms of relationships. (I know,
there are
extensions of FOAF to express more than "knows,"
but as far as I can
tell, no social network is using those extensions)
The upside of FOAF is that all three pieces of information
are
available to a spider application:
1. The source individual (e.g. Dan Connolly)
2. The relationship ("knows")
3. The target individual (e.g. James Tauber)
I don't see any solution to the problem with XFN. As far as
I can see,
social networks using XFN cannot be processed by spiders.
Only social
networks that use FOAF can be processed by spiders. Bummer.
Hopefully, I am missing something. I really like the
simplicity of XFN
and its rich set of relationships.
/Roger
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
| Re: A (big) problem with XFN: identity
of source and target not findable |
  United States |
2008-03-18 08:40:19 |
Costello, Roger L. wrote:
> I don't see any solution to the problem with XFN. As
far as I can see,
> social networks using XFN cannot be processed by
spiders. Only social
> networks that use FOAF can be processed by spiders.
Bummer.
>
> Hopefully, I am missing something. I really like the
simplicity of XFN
> and its rich set of relationships.
You're not missing much. XFN *can* be useful for robots, but
it takes a
lot of work.
Let's take a look at the RDF model. Now RDF/XML as a syntax
is not too
friendly for authors, but I'm not going to concentrate on
the minutiae of
the syntax here: just the underlying model. RDF encodes
three things:
<subject> <predicate> <object>
e.g.
X foaf:name "Toby Inkster"
X foaf:maker Y
Y dc:identifier "http://tobyinkster.co.
uk"
Y dc:title "TobyInkster.co.uk"
and so on. Although these triples seem simple, virtually any
information
is capable of being represented in this manner. (Although it
may not be
the easiest or most natural representation of the data.)
If we look at where XFN fits into the model, it basically
adds a bunch of
predicates (which we can imagine to be implicitly in the
"xfn:" namespace
even if the namespace isn't explicitly declared) like
xfn:contact, xfn:me
and xfn:sibling.
It seems initially that the subject and object of these
predicates is
undefined, but really when we have:
http://bob.example.com xfn
:sibling http://dave.example.com
what is meant is:
X xfn:sibling Y
http://bob.example.com foa
f:primaryTopic X
http://dave.example.com f
oaf:primaryTopic Y
In other words, the two web pages are not siblings -- the
primary topics
(i.e. people described by the pages) are siblings.
XFN right now doesn't define a way of determining the
primary topic of a
page, and probably never will. But if you need to be able to
do determine
this, then there are ways and means. FOAF is one
possibility; and there is
work being done as part of the hCard project to determine
the "definitive
hCard" for a given URL; failing either of those
solutions, heuristics can
be used (e.g. spidering out rel="me" links until
you find the information
you need). Right now it's all a bit undefined and of limited
use in
automatic cataloguing of human relationships.
Also see my second reply (11 Mar 2008, 20:26 UTC) in the
"XFN getting
smoked by FOAF" thread.
--
Toby A Inkster BSc (Hons) ARCS
[Geek of HTML/SQL/Perl/PHP/Python/Apache/Linux]
[OS: Linux 2.6.17.14-mm-desktop-9mdvsmp, up 15:04.]
The Semantic Web
http://t
obyinkster.co.uk/blog/2008/03/09/sw/
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
| Re: A (big) problem with XFN: identity
of source and target not findable |

|
2008-03-18 09:11:52 |
I've been working on a social network browser recently and I
was
preparing to write a blog post called "XFriendN or FOAF
(or API)" on
what I learned, so I have a few relevant comments. Don't
expect I
narrative flow to this e-mail, it's a bit of a brain dump
On Tue, Mar 18, 2008 at 8:31 AM, Costello, Roger L.
<costello mitre.org> wrote:
> Hi Folks,
>
> Flickr uses XFN. Here is a sample Flickr page that
uses XFN:
> http://www.flick
r.com/people/tantek/
>
> At the browser menu select View >> Page Source.
Then search for rel=
>
> Here's an example usage of XFN within that Flickr
page:
>
> <a href="/photos/24172116 N08/" rel="contact">
> <img
> src="http://farm3.static.flickr.com/2146/buddyicons/24172116
a> N08.jpg?12
> 03935044#24172116 N08"
> alt="Jolene_A" width="48"
height="48" /><br />
> Jolene_A
> </a>
>
> Notice the use of XFN: >>>
rel="contact" <<<
Please see Chris Messina's post from last week [1].
Interestingly, he
came to the same conclusion I had just the day before --
there's
basically only "me" and "contacts" and
the reset is gravy. In my
browser application, I normal all the relationship into one
of these
two types (I keep the original relationships, of course).
There's a deeper problem with the Flickr XFN results -- it's
_paged_,
which is totally a nuisance. In this particular case it was
easier for
me go to the Flickr API to get the contacts than use the XFN
data. It
would be nice if they offered a pared down page with only
XFN results.
As an aside, it occurs to me now that we can indicate paged
results by
add rel="me next" and rel="me prev" to
the page navigation links.
[1] http://factoryjoe.com/blog
/2008/03/11/portable-contact-lists-and-the-case-against-xfn/
>
> Metafilter also uses XFN. Here is a sample page that
uses XFN:
> http://www
.metafilter.com/usercontacts/292
>
> Here's an example usage of XFN within that page:
>
> <a href="/user/10411"
rel="colleague" target="_self">40
Watt</a>
>
> Notice the use of XFN: >>>
rel="colleague" <<<
>
> Now, suppose that I wanted to create a spider
application which crawls
> all social networks that use XFN. Most likely, I
would want the spider
> to collect:
>
> 1. Who is the source? That is, who is the individual
using XFN to
> state a relationship?
Trivially, the page "http
://www.metafilter.com/usercontacts/292" is
"me". However, I realize how unsatisfactory an
answer this is! Let me
make three comments here:
1. As a _recommendation_ -- and microformats really need to
make a lot
more recommendations IMHO -- I would suggest that the page
should
should have a link <a href="http://www.m
etafilter.com/user/292"
rel="me">...</a> at a minimum.
Note then that if you navigate then to that home page,
there's a whole
bunch of natural candidates for rel="me" links:
all the other links
2. Extending that thought, they really should have a full
hcard
wrapped around the "me" link: this would be the
profile of "jessamyn".
You've now got the profile and the contacts on the same page
and are
in FOAF-functionality territory.
3. In practice, it's nice to know all sorts of me links even
though
the user hasn't explicitly done this with "me"
links. Google has
created a concept of "canonicalization" [2] that
can convert a sorta
arbitrary URI into a standard representation -- and then
convert that
back into home, profile, contacts, rss, atom links.
Interestingly
enough, metafilter is not in their code, though Flickr is.
Plugging
tantek's flickr page into my browser gives tons of results,
but
Canonically we figure out that this is "me" for
tantek on Flickr.
http://www.flick
r.com/people/tantek/
http://www.flick
r.com/photos/tantek/
http://www.flic
kr.com/people/39039882 N00/
http://
www.flickr.com/people/tantek/contacts/
I've re-implemented this in Python, though probably not
quite to the
standard of Google's JS code.
[2] http://code.google.com/apis/socialgraph/docs/canonica
l.html
4. I hate the fact that we've never solved the canonical
hCard problem
(search the archives). I can't afford to visit tens of links
just in
case there's something interesting on the other side! I
think that as
I produce XFN information in the future (e.g. [3]) I'm going
to add
rel="me X" to links, where X is one of
"profile", "atom", "rss",
"contacts" ... i.e. the terminology that Google
uses for describing
important pages ... and see if this goes anywhere.
[3] http://dpjanes.onaswarm.c
om
>
> 2. What is the relationship? This is, of course,
obtained easily from
> the value of the rel attribute on the link.
>
> 3. Who is the target? That is, who is the other
individual in the
> relationship?
See previous
> You might argue: "Well, the XFN *should* be
embedded within an hCard,
> then you can discover who the source individual is.
And the target
> page should contain an hCard, then you can discover
who the target
> individual is." And I agree that is Best
Practice. Unfortunately,
> this is not mandated and consequently many people
don't do it. For
> example, Flickr and Metafilter don't do it. Nor do
any of the other
> social networks do it.
On the same page here as you. However, these guys do use XFN
+ hCard.
http://davidcrow.jaiku.co
m/
http://www.la
st.fm/user/jevonm/friends/
h
ttp://ma.gnolia.com/people/aarongustafson/contacts
Digg, weirdly enough, uses hCard but not XFN :-(
>
> Conversely, consider FOAF. Advogato is a social
network that uses
> FOAF. Here an example FOAF on that network:
>
> http
://www.advogato.org/person/connolly/foaf.rdf
>
FOAF is, quite frankly, an ugly mess. This, based on my
experience of
trying to code to extract useful information out of it
rather than
just an opinion I pulled out of the air. I spent way to many
hours
coding trying to pull info out of FOAF because, well, things
seem to
be doable in lots of different ways.
People don't want a format does _anything_; people want a
format that
does _something_.
FOAF needs recommendations more than XFN does. Here's the
sample set
of FOAF files I worked with:
http:/
/api.hi5.com/rest/profile/foaf/208329359
http://lomac.vo
x.com/profile/foaf.rdf
http://brad.liv
ejournal.com/data/foaf
http://johngus
hue.typepad.com/foaf.rdf
http://dpjan
es.buzznet.com/user/foaf.xml
I've uploaded N3 serializations of two of these to here:
http://www.davidjanes.com/images/blogmatrix/vox-foaf.n3
a>
http://www.davidjanes.com/images/blogmatrix/hi5-foaf.n3
a>
Note the different way things such as "weblog" are
wrapped -- there's
some sort of intermediate node being placed on the Hi5
links. Why? I
dunno, but it doesn't make pulling out 'img', 'weblog' etc.
links with
SPARQL particularly easy. Maybe there's some magic way to do
this, but
there's only so much digging I'm willing to do.
And someone can ask the people at livejournal what
'foaf:image' is, or
everyone else what 'foaf:img' does.
>
> Hopefully, I am missing something. I really like the
simplicity of XFN
> and its rich set of relationships.
>
> /Roger
I had a great time coding the XFN stuff -- I wrote one piece
of code
that extracts all the A.rel links, another that pulls out
all the
hCards, and another that matches them up and I was done.
Can probably show you guys a demo by the end of the week if
you're
interested Here's
[4] a screen shot.
[4] http://www.davidjanes.com/images/blogmatrix/2
008-03-18%20Tantek.png
Regards, etc...
David
--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
a>
http://www.onaswarm.com
http://www.onamine.com
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
| Re: A (big) problem with XFN: identity
of source and target not findable |
  United States |
2008-03-18 10:29:37 |
David Janes wrote:
> FOAF is, quite frankly, an ugly mess. This, based on my
experience of
> trying to code to extract useful information out of it
rather than just
> an opinion I pulled out of the air. I spent way to many
hours coding
> trying to pull info out of FOAF because, well, things
seem to be doable
> in lots of different ways.
Don't try to parse it yourself -- use an RDF parser. I
recommend Redland
(a.k.a. librdf) -- it's stable, has bindings for a bunch of
different
language, and feature-wise seems to beat the competition
hands down.
As far as relationships go, once the FOAF is parsed, it's
just a matter of
looking for any subjects that have an rdf:type of
foaf:Person and one or
more foaf:knows predicates. Each foaf:knows predicate will
be a resource
(i.e. URI) representing a person that the subject knows. In
terms of the
actual XML representing this kind of information, it's a
nightmare to
parse, but once the RDF parser has reduced it to
subject-predicate-object
triples, it's much easier to consume.
Recently I've been doing quite a bit of work on
rationalising data
discovered from RDF and Microformats and integrating them
into a single
model.
Example:
http://exampl
es.tobyinkster.co.uk/hcard (click "cognify")
FOAF and microformats *can* work nicely together.
--
Toby A Inkster BSc (Hons) ARCS
[Geek of HTML/SQL/Perl/PHP/Python/Apache/Linux]
[OS: Linux 2.6.17.14-mm-desktop-9mdvsmp, up 16:54.]
The Semantic Web
http://t
obyinkster.co.uk/blog/2008/03/09/sw/
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
| Re: Re: A (big) problem with XFN:
identity of source and target not
findable |

|
2008-03-18 11:08:55 |
On Tue, Mar 18, 2008 at 10:29 AM, Toby A Inkster
<mail tobyinkster.co.uk> wrote:
> David Janes wrote:
>
> > FOAF is, quite frankly, an ugly mess. This, based
on my experience of
> > trying to code to extract useful information out
of it rather than just
> > an opinion I pulled out of the air. I spent way
to many hours coding
> > trying to pull info out of FOAF because, well,
things seem to be doable
> > in lots of different ways.
>
> Don't try to parse it yourself -- use an RDF parser. I
recommend Redland
> (a.k.a. librdf) -- it's stable, has bindings for a
bunch of different
> language, and feature-wise seems to beat the
competition hands down.
>
Thanks -- I've got XFN and FOAF working nicely together too.
I'm using
SPARQL and rdflib. My issue is not that it's not doable,
it's just a
lot more difficult than you would think because more or less
anything
shows up in the data -- not some specific thing.
With a typical XML API and Python's ElementTree, I can
manipulating
data within seconds because everything will fall into a
well-defined
slot. Same with JSON APIs and simplejson -- that's even
better, to
tell you the truth, since there's a clearer distinction from
dumping
the data what's representing a list and what's representing
rows.
With XFN, I've already done the hard work: normalizing the
HTML (using
TIDY), hCard parsers, etc. so it's really only regexs.
That's ugly in
one sense, but there's definite benefits for the
publishers.
Regards, etc...
--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
a>
http://www.onaswarm.com
http://www.onamine.com
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
| RE: A (big) problem with XFN: identity
of source andtarget not findable |
  United States |
2008-03-18 11:33:56 |
Thanks David and Toby.
David Janes wrote:
> I had a great time coding the XFN stuff -- I wrote one
piece of code
> that extracts all the A.rel links, another that pulls
out all the
> hCards, and another that matches them up and I was
done.
How do you know that the hCard matches to the XFN,
particularly if the
XFN is not embedded within the hCard?
> Can probably show you guys a demo by the end of the
week
> if you're interested
Yes please!
/Roger
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
| Re: A (big) problem with XFN: identity
of source andtarget not findable |

|
2008-03-18 11:48:55 |
On Tue, Mar 18, 2008 at 11:33 AM, Costello, Roger L.
<costello mitre.org> wrote:
> > I had a great time coding the XFN stuff -- I
wrote one piece of code
> > that extracts all the A.rel links, another that
pulls out all the
> > hCards, and another that matches them up and I
was done.
>
> How do you know that the hCard matches to the XFN,
particularly if the
> XFN is not embedded within the hCard?
I take your chances Good
point though.
--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
a>
http://www.onaswarm.com
http://www.onamine.com
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
| Re: A (big) problem with XFN: identity
of source andtarget not findable |
  United States |
2008-03-18 12:26:20 |
Costello, Roger L. wrote:
> How do you know that the hCard matches to the XFN,
particularly if the
> XFN is not embedded within the hCard?
Effectively, this:
<span class="vcard">
<a class="fn url" href="http://bob.exampl
e.com">Bob Jones</a>
</span>
says "Bob Jones" has the URL "http://bob.example.com&
quot;. And this:
<a rel="friend" href="http://
bob.example.com">Bob</a>
says that "http://bob.example.com&q
uot; is the URL for a friend. So it can be
inferred that Bob Jones is a friend.
Of course, Bob Jone's hCard might link to, say, his
workplace's website --
indeed several hCards could link to the same workplace
website. So then it
becomes more difficult to understand what
rel="friend" means when it links
to that same website. Are they *all* friends?
A better solution would be to the hCard's "uid"
property to indicate that
one particular URL acts as an identifier for one particular
hCard. Then an
XFN link to that same URL could unambiguously describe a
relationship to
that person.
I don't know how widespread the use of "uid" is in
practise though. My own
parser (Cognition) will make up its own UID in the case
where none exists,
as its internal data model requires a unique identifier
(which must
conform to IRI syntax) for every object being described.
--
Toby A Inkster BSc (Hons) ARCS
[Geek of HTML/SQL/Perl/PHP/Python/Apache/Linux]
[OS: Linux 2.6.17.14-mm-desktop-9mdvsmp, up 18:52.]
The Semantic Web
http://t
obyinkster.co.uk/blog/2008/03/09/sw/
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
| Re: A (big) problem with XFN: identity
of source and target not findable |
  United States |
2008-03-19 19:11:58 |
This is not a big problem, its mostly solved with [1]
-ryan
1. htt
p://microformats.org/wiki/representative-hcard
On Mar 18, 2008, at 5:31 AM, Costello, Roger L. wrote:
> Hi Folks,
>
> Flickr uses XFN. Here is a sample Flickr page that
uses XFN:
> http://www.flick
r.com/people/tantek/
>
> At the browser menu select View >> Page Source.
Then search for rel=
>
> Here's an example usage of XFN within that Flickr
page:
>
> <a href="/photos/24172116 N08/"
rel="contact">
> <img
> src="http://farm3.static.flickr.com/2146/buddyicons/24172116
a> N08.jpg?
> 12
> 03935044#24172116 N08"
> alt="Jolene_A" width="48"
height="48" /><br />
> Jolene_A
> </a>
>
> Notice the use of XFN: >>>
rel="contact" <<<
>
> Metafilter also uses XFN. Here is a sample page that
uses XFN:
> http://www
.metafilter.com/usercontacts/292
>
> Here's an example usage of XFN within that page:
>
> <a href="/user/10411"
rel="colleague" target="_self">40
Watt</a>
>
> Notice the use of XFN: >>>
rel="colleague" <<<
>
> Now, suppose that I wanted to create a spider
application which crawls
> all social networks that use XFN. Most likely, I would
want the
> spider
> to collect:
>
> 1. Who is the source? That is, who is the individual
using XFN to
> state a relationship?
>
> 2. What is the relationship? This is, of course,
obtained easily from
> the value of the rel attribute on the link.
>
> 3. Who is the target? That is, who is the other
individual in the
> relationship?
>
> Examine the above snippets of code. Does 1. and 3. pop
out at you?
> That is, do you know who are the individuals that are
the source and
> target of the relationship?
>
> That information "can" be found on the Flickr
and Metafilter sites,
> but
> each site does it *differently*.
>
> So, the problem with XFN can be stated as this: While
XFN does a great
> job of providing a set of relationship values (friend,
contact,
> co-worker, etc), it provides no means for the automated
discovery of
> the individuals that are the source and target of the
relationship.
> Without information about the source and target
individuals, the
> relationship information is not very useful.
>
> You might argue: "Well, the XFN *should* be
embedded within an hCard,
> then you can discover who the source individual is.
And the target
> page should contain an hCard, then you can discover who
the target
> individual is." And I agree that is Best
Practice. Unfortunately,
> this is not mandated and consequently many people don't
do it. For
> example, Flickr and Metafilter don't do it. Nor do any
of the other
> social networks do it.
>
> Conversely, consider FOAF. Advogato is a social
network that uses
> FOAF. Here an example FOAF on that network:
>
> http
://www.advogato.org/person/connolly/foaf.rdf
>
> At the browser menu select View >> Page Source to
see the actual FOAF
> document. Notice that the individual who is the source
of the
> relationship is clearly listed at the top of the
document:
>
> <foaf:name>Dan Connolly</foaf:name>
>
> And the individual who is the target of the
relationship is clearly
> identified:
>
> <foaf:knows>
> <foaf:Person
> rdf:about="http://www.advogato.org/person/jtauber/foaf.rdf#me&q
uot;>
> <foaf:nick>jtauber</foaf:nick>
> <rdfs:seeAlso
> rdf:resource="http://www.advogato.org/person/jtauber/foaf.rdf"/
>
> </foaf:Person>
> </foaf:knows>
>
> The downside of FOAF is the only built-in relationship
is "knows",
> e.g.
> "Dan Connolly knows James Tauber." That is,
FOAF doesn't possess the
> richness of expression in terms of relationships. (I
know, there are
> extensions of FOAF to express more than
"knows," but as far as I can
> tell, no social network is using those extensions)
>
> The upside of FOAF is that all three pieces of
information are
> available to a spider application:
>
> 1. The source individual (e.g. Dan Connolly)
>
> 2. The relationship ("knows")
>
> 3. The target individual (e.g. James Tauber)
>
> I don't see any solution to the problem with XFN. As
far as I can
> see,
> social networks using XFN cannot be processed by
spiders. Only social
> networks that use FOAF can be processed by spiders.
Bummer.
>
> Hopefully, I am missing something. I really like the
simplicity of
> XFN
> and its rich set of relationships.
>
> /Roger
>
>
>
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss microformats.org
> http://microformats.org/mailman/listinfo/microforma
ts-discuss
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
| Re: A (big) problem with XFN: identity
of source and target not findable |

|
2008-03-19 20:36:30 |
Wow. A spec just like Aphrodite, born fully an adult.
On Wed, Mar 19, 2008 at 8:11 PM, Ryan King <ryan theryanking.com> wrote:
> This is not a big problem, its mostly solved with [1]
>
> -ryan
>
> 1. htt
p://microformats.org/wiki/representative-hcard
>
>
>
> On Mar 18, 2008, at 5:31 AM, Costello, Roger L.
wrote:
>
> > Hi Folks,
> >
> > Flickr uses XFN. Here is a sample Flickr page
that uses XFN:
> > http://www.flick
r.com/people/tantek/
> >
> > At the browser menu select View >> Page
Source. Then search for rel=
> >
> > Here's an example usage of XFN within that Flickr
page:
> >
> > <a href="/photos/24172116 N08/" rel="contact">
> > <img
> > src="http://farm3.static.flickr.com/2146/buddyicons/24172116
a> N08.jpg?
> > 12
> > 03935044#24172116 N08"
> > alt="Jolene_A"
width="48" height="48" /><br
/>
> > Jolene_A
> > </a>
> >
> > Notice the use of XFN: >>>
rel="contact" <<<
> >
> > Metafilter also uses XFN. Here is a sample page
that uses XFN:
> > http://www
.metafilter.com/usercontacts/292
> >
> > Here's an example usage of XFN within that page:
> >
> > <a href="/user/10411"
rel="colleague" target="_self">40
Watt</a>
> >
> > Notice the use of XFN: >>>
rel="colleague" <<<
> >
> > Now, suppose that I wanted to create a spider
application which crawls
> > all social networks that use XFN. Most likely, I
would want the
> > spider
> > to collect:
> >
> > 1. Who is the source? That is, who is the
individual using XFN to
> > state a relationship?
> >
> > 2. What is the relationship? This is, of course,
obtained easily from
> > the value of the rel attribute on the link.
> >
> > 3. Who is the target? That is, who is the other
individual in the
> > relationship?
> >
> > Examine the above snippets of code. Does 1. and
3. pop out at you?
> > That is, do you know who are the individuals that
are the source and
> > target of the relationship?
> >
> > That information "can" be found on the
Flickr and Metafilter sites,
> > but
> > each site does it *differently*.
> >
> > So, the problem with XFN can be stated as this:
While XFN does a great
> > job of providing a set of relationship values
(friend, contact,
> > co-worker, etc), it provides no means for the
automated discovery of
> > the individuals that are the source and target of
the relationship.
> > Without information about the source and target
individuals, the
> > relationship information is not very useful.
> >
> > You might argue: "Well, the XFN *should* be
embedded within an hCard,
> > then you can discover who the source individual
is. And the target
> > page should contain an hCard, then you can
discover who the target
> > individual is." And I agree that is Best
Practice. Unfortunately,
> > this is not mandated and consequently many people
don't do it. For
> > example, Flickr and Metafilter don't do it. Nor
do any of the other
> > social networks do it.
> >
> > Conversely, consider FOAF. Advogato is a social
network that uses
> > FOAF. Here an example FOAF on that network:
> >
> > http
://www.advogato.org/person/connolly/foaf.rdf
> >
> > At the browser menu select View >> Page
Source to see the actual FOAF
> > document. Notice that the individual who is the
source of the
> > relationship is clearly listed at the top of the
document:
> >
> > <foaf:name>Dan Connolly</foaf:name>
> >
> > And the individual who is the target of the
relationship is clearly
> > identified:
> >
> > <foaf:knows>
> > <foaf:Person
> > rdf:about="http://www.advogato.org/person/jtauber/foaf.rdf#me&q
uot;>
> >
<foaf:nick>jtauber</foaf:nick>
> > <rdfs:seeAlso
> > rdf:resource="http://www.advogato.org/person/jtauber/foaf.rdf"/
>
> > </foaf:Person>
> > </foaf:knows>
> >
> > The downside of FOAF is the only built-in
relationship is "knows",
> > e.g.
> > "Dan Connolly knows James Tauber." That
is, FOAF doesn't possess the
> > richness of expression in terms of relationships.
(I know, there are
> > extensions of FOAF to express more than
"knows," but as far as I can
> > tell, no social network is using those
extensions)
> >
> > The upside of FOAF is that all three pieces of
information are
> > available to a spider application:
> >
> > 1. The source individual (e.g. Dan Connolly)
> >
> > 2. The relationship ("knows")
> >
> > 3. The target individual (e.g. James Tauber)
> >
> > I don't see any solution to the problem with XFN.
As far as I can
> > see,
> > social networks using XFN cannot be processed by
spiders. Only social
> > networks that use FOAF can be processed by
spiders. Bummer.
> >
> > Hopefully, I am missing something. I really like
the simplicity of
> > XFN
> > and its rich set of relationships.
> >
> > /Roger
> >
> >
> >
> > _______________________________________________
> > microformats-discuss mailing list
> > microformats-discuss microformats.org
> > http://microformats.org/mailman/listinfo/microforma
ts-discuss
>
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss microformats.org
> http://microformats.org/mailman/listinfo/microforma
ts-discuss
>
--
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
a>
http://www.onaswarm.com
http://www.onamine.com
_______________________________________________
microformats-discuss mailing list
microformats-discuss microformats.org
http://microformats.org/mailman/listinfo/microforma
ts-discuss
|
|
|
|