I thought I'd just mention a thought that flitted through my head several months ago. I'm not proposing this at this time as I'd like to try it in practice first.
Here's the proposal on my blog [1]. The example given is to link Ryan's trivial hcard on his blog to his more serious hcard on his website. (a) identify the url as being a place the identity could be found <address class="author vcard"> <a class="url fn x-identity.hcard" href="http://theryanking.com";>Ryan</a> </address> (b) on the identity page, link to the _real_ location of the hcard <link rel="identity.hcard" title="Ryan" href="http://theryanking.com/blog/contact/#vcard"; /> (c) profit! This provides a fairly straight forward path to link an arbitrary hCard somewhere in an enterprise to a standardized identity (probably somehow linked to an LDAP directory in practice). I'd also note that Chris's proposal of earlier this month for a "person profile" is becoming more and more relevant, at least in my mind. OpenID is off doing their own thing in a big way [2], for what it's worth. Regards, etc... David [1] http://blogmatrix.blogmatrix.com/:entry:blogmatrix-2006-09-12-0003/ [2] http://openid.net/specs/openid-attribute-properties-list-1_0-01.html On 9/26/06, Ryan King <[EMAIL PROTECTED]> wrote:
I completely agree that if we had a standard way to mark up employee numbers, companies (enterprises, even) could build nice, loosely coupled tools. However, that doesn't get around the point that microformats are build around existing practices. I was just asking you to build some existing practice of your own first.
_______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
