W3C home > Mailing lists > Public > public-xg-webid@w3.org > January 2012

RE: hCard and WebID

From: Peter Williams <home_pw@msn.com>
Date: Wed, 11 Jan 2012 14:51:08 -0800
Message-ID: <SNT143-W1533894B7985E5CE8DAAA0929E0@phx.gbl>
To: <kidehen@openlinksw.com>, "public-xg-webid@w3.org" <public-xg-webid@w3.org>

im struggling to keep my hcards straight from my vcards;  lets stick with vcards

 

Google publishes my (vcard) profile.

 

http://yorkporc.blogspot.com/#resource(Blog1/1/1/2/1/1/5/1/1)

 

Its visible in triple form here http://morph.talis.com/?data-uri=http%3A%2F%2Fyorkporc.blogspot.com%2F%23resource%28Blog1%2F1%2F1%2F2%2F1%2F1%2F5%2F1%2F1%29&format=html

 

just trying to figure how to make those (vcard) triples show up in my linked data description, too (not just the talis screen scraping)

 

I care as they are "properly" integrated with the RSS feeds (an alternative rrepresentation of my site), and openid as a property over various alternative representations of web sites).


They may be there - and I just dont know how to navigate to see them.

 

I want to be clear that the openid is about blog sites (a particular embodiment of personal identity, expressed in blogging platforms), where webid is about something more abstract (and doesnt requires ANY web presence, to be useful). It can go on a national id card, for all it matters. that it ties in properly to the openid seems good, so ones "online" identity can be inferred from the webid assertion, by fiddling around with bloggin/openid auth protocols etc.

 

vcards are useful to us if tied to the webid, since a cert (bearing SAN with webid, not openid) published properly there imports into Outlook contact manager - and drives the S/MIME...encryption flow. AS it standard said contact manager is not foaf card aware, but can work with vcards. If the semweb can be handling vcards for some "practical importing stuff" (as well as foaf cards for formalised identity management purpose, to do with naming and identification), this "might be useful".

 

 

 

 

 

 

  		 	   		  
Received on Wednesday, 11 January 2012 22:51:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 11 January 2012 22:51:51 GMT