openid-brainstorming - Revision history

Tantek: /* OpenID whitelist authentication for private hCard */ note superceded by indieauth and h-card

2014-08-13T21:21:35Z

OpenID whitelist authentication for private hCard: note superceded by indieauth and h-card

← Older revision		Revision as of 21:21, 13 August 2014
Line 24:		Line 24:

	== OpenID whitelist authentication for private hCard ==		== OpenID whitelist authentication for private hCard ==

			<div style="padding:1em;background:#ffe">This brainstorm has been superseded by [http://indiewebcamp.com/sign-in-use-cases#show_personal_info sign-in with IndieAuth to show more personal info]</div>

	A blog can use the URLs in its [[XFN]] Friendly blogroll as an OpenID whitelist to provide more information to those that login to the blog with one of those URLs. This technique can be used to provide more detailed private [[hCard]] contact information to only a subset of people (or services). You could also build the whitelist of OpenIDs by parsing data out of a social network API or an aggregated list of XFN friends of friends (following the ideas on [[social-network-portability]]).		A blog can use the URLs in its [[XFN]] Friendly blogroll as an OpenID whitelist to provide more information to those that login to the blog with one of those URLs. This technique can be used to provide more detailed private [[hCard]] contact information to only a subset of people (or services). You could also build the whitelist of OpenIDs by parsing data out of a social network API or an aggregated list of XFN friends of friends (following the ideas on [[social-network-portability]]).

Brian: Reverted edits by GetroLbasm (Talk) to last version by Tantek

2008-12-20T22:33:34Z

Reverted edits by GetroLbasm (Talk) to last version by Tantek

← Older revision		Revision as of 22:33, 20 December 2008
Line 1:		Line 1:
	~~licaoueld~~
	<h1> OpenID + microformats Brainstorming </h1>		<h1> OpenID + microformats Brainstorming </h1>
	{{TOC-right}}		{{TOC-right}}
Line 17:		Line 16:
	=== Replace SREG attributes with hCard ===		=== Replace SREG attributes with hCard ===
	* [http://factoryjoe.com/blog/2007/11/01/hcard-for-openid-simple-registration-and-attribute-exchange/ hCard for OpenID Simple Registration and Attribute Exchange] by [[Chris Messina]]		* [http://factoryjoe.com/blog/2007/11/01/hcard-for-openid-simple-registration-and-attribute-exchange/ hCard for OpenID Simple Registration and Attribute Exchange] by [[Chris Messina]]
	* [http://tantek.com/log/2007/11.html#d02t2318 Replacing OpenID SREG with hCard part 1: Modest proposals] by [[Tantek ~~Ãelik~~]].		* [http://tantek.com/log/2007/11.html#d02t2318 Replacing OpenID SREG with hCard part 1: Modest proposals] by [[Tantek Çelik]].

	=== Replace Attribute Exchange attributes with hCard ===		=== Replace Attribute Exchange attributes with hCard ===
Line 29:		Line 28:
	[[User:TomMorris\|Tom Morris]] has implemented this on [http://tommorris.org/blog his blog], and on a "family extranet".		[[User:TomMorris\|Tom Morris]] has implemented this on [http://tommorris.org/blog his blog], and on a "family extranet".

	In his blog post [http://adactio.com/journal/1348/ MicroformatID], Jeremy Keith explained how Tom's blog works: <blockquote><p>Tom has an hCard on his blog. By default the information provided is fairly basic: an email address, a URL and a vague physical address. Right by the hCard, ~~thereâs~~ a simple form that allows you to log on using OpenID. If you log on and ~~youâre~~ on a white list of ~~Tomâs~~ friends, the hCard is updated to reveal more information: telephone numbers and a complete physical address.</p><p>~~Thatâs~~ pretty clever. And when you consider that OpenID is a URL-based authentication system and XFN is also based around URLs, it would be pretty easy to have the white list correspond to an XFN list on the same page as the hCard.</p><p>hCard \| OpenID \| ~~XFNâ¦ itâs~~ like Unix pipes for the Web: small pieces, loosely joined.</p></blockquote>		In his blog post [http://adactio.com/journal/1348/ MicroformatID], Jeremy Keith explained how Tom's blog works: <blockquote><p>Tom has an hCard on his blog. By default the information provided is fairly basic: an email address, a URL and a vague physical address. Right by the hCard, there’s a simple form that allows you to log on using OpenID. If you log on and you’re on a white list of Tom’s friends, the hCard is updated to reveal more information: telephone numbers and a complete physical address.</p><p>That’s pretty clever. And when you consider that OpenID is a URL-based authentication system and XFN is also based around URLs, it would be pretty easy to have the white list correspond to an XFN list on the same page as the hCard.</p><p>hCard \| OpenID \| XFN… it’s like Unix pipes for the Web: small pieces, loosely joined.</p></blockquote>

	Tom recently explained this a bit more in his blog post [http://tommorris.org/blog/2007/11/05#pid2533635 Are you on the list? / Once again, in English]:		Tom recently explained this a bit more in his blog post [http://tommorris.org/blog/2007/11/05#pid2533635 Are you on the list? / Once again, in English]:

GetroLbasm: acellidar

2008-12-20T06:08:50Z

acellidar

← Older revision		Revision as of 06:08, 20 December 2008
Line 1:		Line 1:
			licaoueld
	<h1> OpenID + microformats Brainstorming </h1>		<h1> OpenID + microformats Brainstorming </h1>
	{{TOC-right}}		{{TOC-right}}
Line 16:		Line 17:
	=== Replace SREG attributes with hCard ===		=== Replace SREG attributes with hCard ===
	* [http://factoryjoe.com/blog/2007/11/01/hcard-for-openid-simple-registration-and-attribute-exchange/ hCard for OpenID Simple Registration and Attribute Exchange] by [[Chris Messina]]		* [http://factoryjoe.com/blog/2007/11/01/hcard-for-openid-simple-registration-and-attribute-exchange/ hCard for OpenID Simple Registration and Attribute Exchange] by [[Chris Messina]]
	* [http://tantek.com/log/2007/11.html#d02t2318 Replacing OpenID SREG with hCard part 1: Modest proposals] by [[Tantek ~~Çelik~~]].		* [http://tantek.com/log/2007/11.html#d02t2318 Replacing OpenID SREG with hCard part 1: Modest proposals] by [[Tantek Ãelik]].

	=== Replace Attribute Exchange attributes with hCard ===		=== Replace Attribute Exchange attributes with hCard ===
Line 28:		Line 29:
	[[User:TomMorris\|Tom Morris]] has implemented this on [http://tommorris.org/blog his blog], and on a "family extranet".		[[User:TomMorris\|Tom Morris]] has implemented this on [http://tommorris.org/blog his blog], and on a "family extranet".

	In his blog post [http://adactio.com/journal/1348/ MicroformatID], Jeremy Keith explained how Tom's blog works: <blockquote><p>Tom has an hCard on his blog. By default the information provided is fairly basic: an email address, a URL and a vague physical address. Right by the hCard, ~~there’s~~ a simple form that allows you to log on using OpenID. If you log on and ~~you’re~~ on a white list of ~~Tom’s~~ friends, the hCard is updated to reveal more information: telephone numbers and a complete physical address.</p><p>~~That’s~~ pretty clever. And when you consider that OpenID is a URL-based authentication system and XFN is also based around URLs, it would be pretty easy to have the white list correspond to an XFN list on the same page as the hCard.</p><p>hCard \| OpenID \| ~~XFN… it’s~~ like Unix pipes for the Web: small pieces, loosely joined.</p></blockquote>		In his blog post [http://adactio.com/journal/1348/ MicroformatID], Jeremy Keith explained how Tom's blog works: <blockquote><p>Tom has an hCard on his blog. By default the information provided is fairly basic: an email address, a URL and a vague physical address. Right by the hCard, thereâs a simple form that allows you to log on using OpenID. If you log on and youâre on a white list of Tomâs friends, the hCard is updated to reveal more information: telephone numbers and a complete physical address.</p><p>Thatâs pretty clever. And when you consider that OpenID is a URL-based authentication system and XFN is also based around URLs, it would be pretty easy to have the white list correspond to an XFN list on the same page as the hCard.</p><p>hCard \| OpenID \| XFNâ¦ itâs like Unix pipes for the Web: small pieces, loosely joined.</p></blockquote>

	Tom recently explained this a bit more in his blog post [http://tommorris.org/blog/2007/11/05#pid2533635 Are you on the list? / Once again, in English]:		Tom recently explained this a bit more in his blog post [http://tommorris.org/blog/2007/11/05#pid2533635 Are you on the list? / Once again, in English]:

Tantek: move some ideas for use to best practices

2008-08-30T02:43:12Z

move some ideas for use to best practices

← Older revision		Revision as of 02:43, 30 August 2008
Line 11:		Line 11:

	== Ideas for use ==		== Ideas for use ==
	* ~~Identity providers should provide~~ [[~~hcard~~-~~supporting~~-~~user-profiles\|hCard marked up profile pages~~]]		* see [[openid-best-practices]].
	* re-use [[hcard\|hCard]] (vCard) vocabulary for HTTP query based key-value pairs of information requested and returned		* re-use [[hcard\|hCard]] (vCard) vocabulary for HTTP query based key-value pairs of information requested and returned

Tantek: rm JSON fragment which is covered elsewhere, offtopic for this page

2008-08-30T02:19:35Z

rm JSON fragment which is covered elsewhere, offtopic for this page

← Older revision		Revision as of 02:19, 30 August 2008
Line 59:		Line 59:
	* Will Norris on [http://willnorris.com/2007/11/hcard-is-not-a-provisioning-engine-for-private-data privacy issues in using hcard for data provisioning.]		* Will Norris on [http://willnorris.com/2007/11/hcard-is-not-a-provisioning-engine-for-private-data privacy issues in using hcard for data provisioning.]
	** Most of Will's questions/concerns are explained by Tom's abovementioned blog post.		** Most of Will's questions/concerns are explained by Tom's abovementioned blog post.

	~~== Microformats outside HTML ==~~
	* JSON representations of hCard etc.

	==See also==		==See also==

TomMorris: nice to see myself here! just added some extra notes about it

2007-12-13T17:19:30Z

nice to see myself here! just added some extra notes about it

← Older revision		Revision as of 17:19, 13 December 2007
Line 32:		Line 32:
	Tom recently explained this a bit more in his blog post [http://tommorris.org/blog/2007/11/05#pid2533635 Are you on the list? / Once again, in English]:		Tom recently explained this a bit more in his blog post [http://tommorris.org/blog/2007/11/05#pid2533635 Are you on the list? / Once again, in English]:
	<blockquote><p>Here's what I'm trying to do. I have an hCard on my blog - over in the sidebar. I want to make it so that the people who want to get my contact details can. I've had the fun experience of auto-dialling with Skype when microformats are present, and being able to download phone numbers onto my phone. Basically, I want to simulate electronically the situation I have when one gives their business card out to someone without having to carry bits of card around with me. The user experience should something like this:</p><p>User: "I know Tom. I want to contact him by phone or send him something by post." User goes to my blog and enters their OpenID. If user is on list, user sees extra information - my home address and phone numbers. This is all in an hCard, so they can use hCard tools like Operator to use the information in a more useful way.</p> <p>This is important, as often people want to make data available, but not to everyone. OpenID is a good way of letting people authenticate, but not as intrusive as having them sign up and have to give you their e-mail and so on.</p><p>...</p><p>Ideally, when we have a few more pieces in place, we will have it so that we can do automatic OpenID inference - if you have a WordPress blog and I list you as a friend on say, Flickr and Twitter, then you can get access to my personal details. Personal details are also just the tip of the iceberg - everyone has things which they want only some of their friends to be able to see or use. </p><p>The general overall plan is to make it so that network connections can be used as a way of providing or denying services. Some people are using this 'graph' of connections to determine whether or not you are a comment spammer.</p></blockquote>		<blockquote><p>Here's what I'm trying to do. I have an hCard on my blog - over in the sidebar. I want to make it so that the people who want to get my contact details can. I've had the fun experience of auto-dialling with Skype when microformats are present, and being able to download phone numbers onto my phone. Basically, I want to simulate electronically the situation I have when one gives their business card out to someone without having to carry bits of card around with me. The user experience should something like this:</p><p>User: "I know Tom. I want to contact him by phone or send him something by post." User goes to my blog and enters their OpenID. If user is on list, user sees extra information - my home address and phone numbers. This is all in an hCard, so they can use hCard tools like Operator to use the information in a more useful way.</p> <p>This is important, as often people want to make data available, but not to everyone. OpenID is a good way of letting people authenticate, but not as intrusive as having them sign up and have to give you their e-mail and so on.</p><p>...</p><p>Ideally, when we have a few more pieces in place, we will have it so that we can do automatic OpenID inference - if you have a WordPress blog and I list you as a friend on say, Flickr and Twitter, then you can get access to my personal details. Personal details are also just the tip of the iceberg - everyone has things which they want only some of their friends to be able to see or use. </p><p>The general overall plan is to make it so that network connections can be used as a way of providing or denying services. Some people are using this 'graph' of connections to determine whether or not you are a comment spammer.</p></blockquote>

			* Note from [[User:TomMorris\|Tom Morris]]: My system is implemented using FOAF and SPARQL rather than XFN. It is possible, though, using GRDDL to implement XFN and hCard parsing into the system I currently have built. The technical component is done by compiling all the data from a variety of sources into a handful of FOAF files, then running a query like this: <code>SELECT ?openid WHERE { <http://tommorris.org/foaf#me> foaf:knows ?person. ?person foaf:openid ?openid . }</code> (with all the relevant prefixes) - this then emits an XML or JSON file (I use JSON), which is then uploaded to my site. The JSON is available [http://tommorris.org/openids.json here]. I don't use XFN in this system because most of the social networks I am compiling data from already provide it via APIs which works better with the workflow. It would be trivial to add though, and something I will probably do quite soon. If anyone needs assistance implementing this, feel free to contact me.

	Steve Ivy recently started analyzing how to implement this and diagramming processes:		Steve Ivy recently started analyzing how to implement this and diagramming processes:

SteveIvy: /* OpenID whitelist authentication for private hCard */ rework notes after example markup

2007-12-03T15:23:42Z

OpenID whitelist authentication for private hCard: rework notes after example markup

← Older revision		Revision as of 15:23, 3 December 2007
Line 51:		Line 51:
	</code>		</code>

	A spider processing whitelists ~~would need~~ to follow each <code>url</code> ~~in the hCard~~ and ~~determine~~ (~~using the~~ <code><link rel="openid.provider"></code>?) ~~if the page is an openid for the contact.~~ -- Steve		Though it's not a standard, conceivably a spider processing whitelists could use the "openid" class to determine that a url page is an openid for the contact. Alternatively (and more definitively) follow each <code>url</code> and check to see if it is an openid url (<code><link rel="openid.provider"></code> or <code><link rel="openid.delegate"></code> perhaps?)
			-- Steve

	=== Counterpoints ===		=== Counterpoints ===

SteveIvy: /* OpenID whitelist authentication for private hCard */

2007-11-30T16:34:36Z

OpenID whitelist authentication for private hCard

← Older revision		Revision as of 16:34, 30 November 2007
Line 45:		Line 45:
	class="fn url openid">Chris Messina</a>		class="fn url openid">Chris Messina</a>
	<!-- blog url on the blog name -->		<!-- blog url on the blog name -->
	- <a href="http://factoryjoe.org/blog" class="url ~~acquaintance colleague~~"		- <a href="http://factoryjoe.org/blog" class="url"
	title="Factory Joe">Factory Joe</a>		title="Factory Joe">Factory Joe</a>
	</li>		</li>

SteveIvy: /* OpenID whitelist authentication for private hCard */ comment xfn+openid markup

2007-11-30T16:32:30Z

OpenID whitelist authentication for private hCard: comment xfn+openid markup

← Older revision		Revision as of 16:32, 30 November 2007
Line 41:		Line 41:
	<pre>		<pre>
	<li class="vcard">		<li class="vcard">
	<a href="http://claimid.com/factoryjoe" class="fn url openid">Chris Messina</a>		<!-- openid url on the person's name -->
	- <a href="http://factoryjoe.org/blog~~" rel="acquaintance colleague~~" class="url acquaintance colleague" title="Factory Joe">Factory Joe</a>		<a href="http://claimid.com/factoryjoe" rel="acquaintance colleague"
			class="fn url openid">Chris Messina</a>
			<!-- blog url on the blog name -->
			- <a href="http://factoryjoe.org/blog" class="url acquaintance colleague"
			title="Factory Joe">Factory Joe</a>
	</li>		</li>
	</pre>		</pre>

SteveIvy: /* OpenID whitelist authentication for private hCard */ add example markup for XFN+hCard+OpenID

2007-11-28T15:46:15Z

OpenID whitelist authentication for private hCard: add example markup for XFN+hCard+OpenID

@@ Line 36: / Line 36: @@
 * [http://redmonk.net/archives/2007/11/25/making-a-list-whitelisting-with-openid-and-xfn/ Making a list: Whitelisting with OpenId and XFN] <br > [http://redmonk.net/archives/2007/11/25/making-a-list-whitelisting-with-openid-and-xfn/ http://redmonk.net/files/skitch/new_xfn_openid_whitelist-20071127-210800.png]
 * [http://redmonk.net/archives/2007/11/26/blogrolls-xfn-and-openid-uris/ Blogrolls, XFN, and OpenID URIs]
 === Counterpoints ===