I'm just tossing an idea out for discussion (and to get it out of my head).

I've been looking recently at XFN as it's used "in the wild" as a
method of social network portability, or as Chris has probably more
correctly relabeled it, "portable contact lists" [1]. In several
cases, for example here [2]. Obviously this is a requirement to make
this _human usable_ but unfortunately without further assistance an
XFN parser is only going to get a fraction of the contact list. Not
good.

HTML has rel= elements for paging through data: rel, next, index,
start and contents [3].

My thoughts:
- has something already been done and I'm missing it (if so: end here
;-) otherwise
- let's gather examples from the web, and start seeing how we can sort this out

I don't think this is an overly difficult project, maybe, hopefully. I
may just be a matter of defining how those link types work within the
context of a page or particular microformats. In particular, there's
probably an hAtom hfeed/fentry connection here too, and probably also
for contact lists. Maybe there's a need to define an (optional)
enclosing element, maybe there's not.

Regards, etc...

[1] 
http://factoryjoe.com/blog/2008/03/11/portable-contact-lists-and-the-case-against-xfn/
[2] http://twitter.com/statuses/friends/scobleizer.xml
[3] http://www.w3.org/TR/html401/types.html#type-links

-- 
David Janes
Founder, BlogMatrix
http://www.blogmatrix.com
http://www.onaswarm.com
http://www.onamine.com
_______________________________________________
microformats-new mailing list
[email protected]
http://microformats.org/mailman/listinfo/microformats-new

Reply via email to