Subscribe to feed:
Or get posts via email:









Add to Technorati Favorites



« SF Geek Dinner | Main | The Berkeley Lower Extremity Exoskeleton (BLEEX) »

The Danger of Losing Context with XFN

As I re-posted Robert Scoble's geek dinner attendance list, I noticed that he included XFN notation in the links. When I re-posted the links, I made sure to edit all of the rel attributes to reflect my own relationships. But I could imagine that someone who uses a tool to copy links or simply is not yet aware of XFN might copy and paste them without realizing that s/he was specifying accidental semantic web relationships.

Those rel attributes convey one-way relationship information; from the owner of the containing page to the owner of the link. XFN tools must infer that the originator of the relationship is the owner of the page in which the link exists.

Since one half of the relationship is implied from the context of the containing document, there is a danger of misrepsenting relationship information by decontextualizing (re-posting) links that contain rel attributes. This problem would apply to any use of the XHTML rel attribute.

Maybe this won't happen much, but I wonder if we can come up with something to help keep the XFN network from being corrupted by such decontextualization.

TrackBack

Listed below are links to weblogs that reference The Danger of Losing Context with XFN:

» The Semantic Context of XFN from codestream
Michael Eakes raises the issue of XFN context. The problem he identifies is that someone might copy a set of XFN-enabled links from another blog and put them into their own, without realising that the links contained semantic information. It's... [Read More]

Comments (2)

I think you are right, it is very possible that it might happen and did, I did it!
XFN is still a new concept to a lot of folks and is not even supported by a lot of HTML creation programs. It wasn't till I saw a post about the danger of doing what you say that I started doing research on XFN, went back and started using XFN on my own posts. Oh yes, I fixed my prior posts!
Anyway I started using Nvu for creating blog posts as it supports XFN.
~Steve

What if rather than putting the XFN entries directly into the html page, a seprate html file is kept as your blogroll file and either linked to using the link rel=, or using a meta-tag in the header? Only problem I see is compatability with existing XFN apps. I think a meta-tag is the way to go.

Post a comment