in Identity Management

Johannes is on a roll: RSS-Foaf

More movement in the quest for a simpler FOAF: Johannes Ernst now proposes to enhance RSS to be a bearer for FOAFy data structures:

“When I tried to explain the RSFOAF idea to somebody last Friday, I got thinking: from an information structure perspective, how exactly is the set of members in my social network different from the set of gifts on an Amazon gift list? Well, it isn’t, at least not much. So … if RSS works for gift lists and other sets, why not for FOAF? Reminder to self: RSS is becoming the universal subscription format, so why not use it?”

This is an example of how that might look like if mixed with a style sheet – quite impressive.

However – it’s quite a bit closer to the original than the simple RSFOAF idea, and it mandates an XML format which RSFOAF did not. I actually liked that part best in the RSFOAF idea – people’s identity information today is in sooo many different formats: LinkedIn, Friendster, OpenBC, VCARD, Plaxo, what have you. I’d much rather have a web service understand all these different formats than me having to care about them, much less convert them into another format.

Now, let’s wait for Johannes to come up with a better idea next week, shall we? ;)

Leave a Reply

  1. I guess I don’t quite understand what you are saying. E.g. RSFOAF did mandate an XML format to express “Person” and “Group”. RSS-FOAF does the same thing, just using a slightly different syntax. The idea of referring to people’s VCard URLs and what have you is still the same, except that we can use existing RSS tags for that in RSS-FOAF and don’t need to invent new ones.

  2. I guess I don't quite understand what you are saying. E.g. RSFOAF did mandate an XML format to express "Person" and "Group". RSS-FOAF does the same thing, just using a slightly different syntax. The idea of referring to people's VCard URLs and what have you is still the same, except that we can use existing RSS tags for that in RSS-FOAF and don't need to invent new ones.

  3. The point is that hCard doesn’t invent any new “tags”, it simply reuses property names from vCard which makes it ideal for interoperating with existing contact info implementations, e.g. every modern address book on every platform and even most phones as well. It’s essentially another alternative to consider when looking at how to publish contact information in a visible/presentable form on the Web.

    Thanks,

    Tantek

  4. The point is that hCard doesn't invent any new "tags", it simply reuses property names from vCard which makes it ideal for interoperating with existing contact info implementations, e.g. every modern address book on every platform and even most phones as well. It's essentially another alternative to consider when looking at how to publish contact information in a visible/presentable form on the Web.

    Thanks,

    Tantek

Webmentions

  • DeveloperZen.com October 5, 2005

    [IMG] Constant Bearing, Decreasing Range [IMG] Doing My Little Part- Weblog of Mark Finnern [IMG] Software Alphabet Soup [IMG] The Village View [IMG] theotherthomasotter [IMG] Venture Chronicles [IMG] http://www.gadgetguy.de – The GadgetGuy [IMG] Yet Another Software Blog

  • DeveloperZen.com October 5, 2005

    [IMG] Constant Bearing, Decreasing Range [IMG] Doing My Little Part- Weblog of Mark Finnern [IMG] Software Alphabet Soup [IMG] The Village View [IMG] theotherthomasotter [IMG] Venture Chronicles [IMG] http://www.gadgetguy.de – The GadgetGuy [IMG] Yet Another Software Blog

  • Welcome to www.ekampf.com October 5, 2005

    [IMG] Constant Bearing, Decreasing Range [IMG] Doing My Little Part- Weblog of Mark Finnern [IMG] Software Alphabet Soup [IMG] The Village View [IMG] theotherthomasotter [IMG] Venture Chronicles [IMG] http://www.gadgetguy.de – The GadgetGuy [IMG] Yet Another Software Blog