Main menu:


Subscribe with Bloglines

Subscribe via e-mail:

Twitter Status

My Twitter Feed
@hunterwalk lol they will now! ;)
3 days ago

Site search

Categories

March 2009
M T W T F S S
« Feb   May »
 1
2345678
9101112131415
16171819202122
23242526272829
3031  

Archive

Portable Contacts and vCardDAV (IETF 74)

Portable Contacts and vCardDAV
IETF 74
San Francisco, CA
March 25, 2009

Download PPT (81 KB) or PDF

You may remember the venerable IETF standards-body from such foundational internet RFCs as HTTP (aka the web), SMTP (aka e-mail), and vCard (aka contact info). So I’ll be honest that I was a bit intimidated when they invited me to their IETF-wide conference to speak about my work on Portable Contacts.

In addition to being chartered with updating vCard itself, the IETF has a working group building a read-write standard for sharing address book data called CardDAV. (It’s a set of extensions to WebDAV for contact info, hence the name.) Since Portable Contacts is also trying to create a standard for accessing contact into online (albeit with a less ambitious scope and feature set), I was eager to share the design decisions we had made and the promising early adoption we’ve already seen.

My optimistic hope was that perhaps some of our insights might end up influencing the direction of CardDAV–or perhaps even vCard itself. But I was also a bit nervous that such an august and rigorous standards body might have little interest in the pontifications of a “scrappy Open Stack hacker” like me. Or that even if they liked what I said, it might be impossible to have an impact this late in the game. But I figured if nothing else, here’s a group of people that are as passionate about the gory details of contact info as we are, so at least we should meet one another and see where it leads.

Boy was I impressed and inspired by their positive reception of my remarks! Far from being a hostile or dis-interested audience, everyone seemed genuinely excited by the work we’d done, especially since companies large and small are already shipping compliant implementations. The Q&A was passionate and detailed, and it spilled out into the hallway and continued long after the session officially ended.

Best of all, I then got to sit down with Simon Perreault, one of the primary authors of vCard 4.0 and vCardXML, and we went literally line-by-line through the entire Portable Contacts spec and wrote a list of all the ways if differs from the next proposed version of vCard. As you might imagine, there were some passionate arguments on both sides concerning the details, but actually there were really no “deal breakers” in there, and Simon sounded quite open (or even excited) about some of the “innovations” we’d made. It really does look like we might be able to get a common XML schema across PoCo and vCard / CardDAV, and some of the changes might well land in core vCard!

Of course, any official spec changes will happen through the normal IETF mailing lists and process. But as I’m sure you can tell, I think things went amazingly well today, and the future of standards for sharing contact info online has never looked brighter! Thanks again to Marc Blanchet, Cyrus Daboo, and the rest of the vCardDAV working group for their invitation and warm reception. Onward ho!

  • Nice post here. It does make senses, appreciate for sharing.
  • Nice to hear that it was such a nice experience! Exciting to see how different open stack components like poco and oauth is getting attention from the classic old standard bodies - seems like yet another step on getting the new social world to be a natural part of society.
  • It was good to see you there. This has been my first IETF as well, and for the most part, a very positive experience.
  • Yeah, great seeing you there, and congrats on the amazing progress you're making with drizzle!
  • Joseph, Any thoughts on how this approach compliements, extends, or provides an alternative to microformats such as hCard? Thanks...
  • Mike-they're complementary, and they play very well together. PoCo is an API with a contact info schema that's heavily based on vCard. And hCard is a way of embedding vCard data in web pages that don't otherwise have APIs. So for instance, if you have hCard for your contact info on your own blog, we can run that through technorati's hCard->vCard converter and then run that through our vCard->PoCo converter and voila--your home page is now effectively a Portable Contacts API for your own contact info (see for instance http://bit.ly/longpipe which does this with twitter).
blog comments powered by Disqus