openid-brainstorming-fr: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m ([fr: sync'd - à relire])
(→‎authentification OpenID en liste blanche pour hCard privée: sync'd with english version - added Steve Ivy diagram to be translated)
Line 33: Line 33:
Dans ce billet de blog [http://adactio.com/journal/1348/ MicroformatID], Jeremy Keith a expliqué comment fonctionne le blog de Tom : <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>
Dans ce billet de blog [http://adactio.com/journal/1348/ MicroformatID], Jeremy Keith a expliqué comment fonctionne le blog de Tom : <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 expliquait cela récemment un peu plus dans son billet de blog [http://tommorris.org/blog/2007/11/05#pid2533635 Are you on the list? / Une fois de plus en anglais ]:
Tom expliquait cela récemment un peu plus dans son billet de blog [http://tommorris.org/blog/2007/11/05#pid2533635 Are you on the list? / Une fois de plus en anglais] :
<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>


=== Contrepoints ===
Steve Ivy a commencé récemment à analyser la manière d'implémenter cela et à illustrer les processus :
* 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.]
* [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]
 
 
=== Contre-arguments ===
* Will Norris sur [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 à l'extérieur du HTML ==
== Microformats à l'extérieur du HTML ==

Revision as of 06:50, 28 November 2007

OpenId + Microformats Brainstorming

Ceci est un espace public pour saisir quelques idées sur la façon dont [[OpenID-fr|OpenID] et les Microformats peuvent fonctionner ensemble.

Microformats pertinents

  • hCard - pour les profils
  • XFN
    • rel="friend" etc. pour marquer les relations entre profils
    • rel="me" pour la consolidation d'identité entre profils
      • Est-ce que Yadis devrait être étendu pour supporter rel="me"?

Idées pour utilisation

  • Les fournisseurs d'identité devraient fournir des pages profils marquées avec hCard
  • réutilisation du vocabulaire de hCard (vCard) pour les requêtes HTTP basées sur des paires de valeurs-clé d'information requêtées et retournées.

Remplacer les attributs SREG avec hCard

Remplacer les attributs Attribute Exchange avec hCard

Beaucoup d'attributs dans le attribute registry établi sur axschema.org sont des réinventions de propriétés définies dans la vCard (et par conséquent hCard). Ce serait préférable de réutiliser un tel vocabulaire plutôt que de le réinventer (voir aussi principes de nommage).

authentification OpenID en liste blanche pour hCard privée

Un blog peut utiliser les URLs dans sa blogroll XFN sous forme d'une liste blanche OpenID pour fournir plus d'informaiton à ceux qui se connectent sur le blog avec l'une de ces URLs. Cette technique peut être utilisée pour fournir ne information de contact plus privée sous hCard pour seulement un sous-ensemble de personnes (ou de services). Vous pourriez aussi construire la liste blanche des OpenIDs en analysant les données d'une API de réseau social à l'extérieur ou une liste agrégée XFN d'amis d'amis (en suivant les idées sur la portabilité-du-réseau-social).

Tom Morris a implémenté ça sur son blog, et sur un "extranet de famille".

Dans ce billet de blog MicroformatID, Jeremy Keith a expliqué comment fonctionne le blog de Tom :

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.

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.

hCard | OpenID | XFN… it’s like Unix pipes for the Web: small pieces, loosely joined.

Tom expliquait cela récemment un peu plus dans son billet de blog Are you on the list? / Une fois de plus en anglais :

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:

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.

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.

...

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.

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.

Steve Ivy a commencé récemment à analyser la manière d'implémenter cela et à illustrer les processus :


Contre-arguments

Microformats à l'extérieur du HTML

  • représentations JSON de hCard etc.

Voir aussi