I just ran across a blogosphere thread starting somewhere around:
http://factoryjoe.com/blog/2007/11/01/hcard-for-openid-simple-registration-and-attribute-exchange/
through
http://willnorris.com/2007/11/hcard-is-not-a-provisioning-engine-for-private-data
- which turns into concrete proposals on
According to [1] it's fine sticking rel attribute in link elements so
I don't see why not, generally. But read on.
I would even extend the question why not adding rev=me since that
url should be mine as well but,this [2] proved me wrong..
[1]
Will Norris made a great suggesting for making OpenID delegation links
compatible with XFN rel-me links. I actually think that it's okay to
use link /'s in the header of a document to point to other social
networks and so on... I understand that this is not kosher with
marking up visible data, but
On 10/13/07, Chris Messina [EMAIL PROTECTED] wrote:
Will Norris made a great suggesting for making OpenID delegation links
compatible with XFN rel-me links. I actually think that it's okay to
use link /'s in the header of a document to point to other social
networks and so on... I understand
On Feb 20, 2007, at 1:24 PM, Thom Shannon wrote:
I was thinking there should be a way to have your OpenID
on other profiles that can easily be consumed, allowing someone to see
you on social network A and add you on their social network B based on
you using the same OpenID.
that's where UID
On Tue, 20 Feb 2007 22:24:00 +0100, Thom Shannon [EMAIL PROTECTED] wrote:
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The
I was picturing something more along the lines of a list of your friends
on your social network, each one with an openID, you'd then want to copy
and paste that to search for the same friend on the other social
network. No one needs to know it's actually a url, not least the user.
Both social
I disagree, it being a URL is a good thing. I have http:/
kevinmarks.com as an openid URL with microformats attached to it
(based on Chris Messina's here):
http://factoryjoe.com/hcard.html
Should I be asserting his urls as a uid?
On Feb 21, 2007, at 2:19 AM, Thom Shannon wrote:
I was
I'm not saying you shouldn't have the option, my openid is my website,
so I want people to link to it too. But if my mum has an openID of
openid.aol.com/mum, then she just needs to remember that, use it, and
know that's her unique identity across the net, she never needs to see
what's actually
Arve Bersvendsen wrote:
On Tue, 20 Feb 2007 22:24:00 +0100, Thom Shannon [EMAIL PROTECTED] wrote:
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID
On Wed, 21 Feb 2007 17:18:41 +0100, John Panzer [EMAIL PROTECTED] wrote:
I would think that using a rel value would make more sense, since rel
exists to signify the relationship between the current document (or
context therein); a href=http://example.com/;
rel=openid.identifierMy
Hi,
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The openid-brainstorming page mentions using hCard on providers profile
pages etc,
Thom Shannon wrote:
Hi,
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The openid-brainstorming page mentions using
The problem here is that there is concept of types in URLS
All parsers see is multiple URLS. We don't know which is the openid URL...
Mike Kaply
On 2/20/07, John Panzer [EMAIL PROTECTED] wrote:
Thom Shannon wrote:
Hi,
Forgive me if this is going over old ground, I just joined
but surely we can just use a class like microformats do to apply types
to other elements? either that or a rel?
Mike Kaply wrote:
The problem here is that there is concept of types in URLS
All parsers see is multiple URLS. We don't know which is the openid
URL...
Mike Kaply
On
I think it should also be possible to use openIDs in other elements than
just anchors. You don't necessarily want to link to them, it's the url
itself which is important not the location.
It should also support none canonical urls so they can be written in the
way users expect, we don't want
On Feb 20, 2007, at 3:24 PM, Thom Shannon wrote:
Forgive me if this is going over old ground, I just joined this
list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The openid-brainstorming page
Scott Reynen wrote:
On Feb 20, 2007, at 3:24 PM, Thom Shannon wrote:
Forgive me if this is going over old ground, I just joined this list and
couldn't find what I was looking for on the wiki. Are there any
particular conventions emerging for embedding an OpenID into a hCard?
The
On 2/20/07, Thom Shannon [EMAIL PROTECTED] wrote:
I think it should also be possible to use openIDs in other elements than
just anchors. You don't necessarily want to link to them, it's the url
itself which is important not the location.
It should also support none canonical urls so they can be
On 2/20/07, anders conbere [EMAIL PROTECTED] wrote:
It derives it's meaning and value from the use of the global
DNS system, regardless if you're actually looking to direct
traffic to your openID or not, it's the nature of it being an
anchor that gives it power.
Check out the 2.0 spec. There
Hi Christopher,
On Feb 20, 2007, at 7:00 PM, Christopher St John wrote:
Check out the 2.0 spec. There are some changes:
http://openid.net/specs/openid-authentication-2_0-11.html
It introduces XRI into the mix (think brand new, non-DNS
naming system) Wouldn't expect it to work so well in an a
21 matches
Mail list logo
