mmond Reed; Dick Hardt; McGovern, James F (HTSC, IT)
Cc: specs@openid.net
Subject: RE: Features for Future Versions
I also agree with the feedback however I wanted to just pass along how I
am using authentication and authorization on a series of applications
that I am working on.
I have a
/(+phone)
chat: =les/skype/chat
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf
> Of Drummond Reed
> Sent: Monday, April 02, 2007 2:26 PM
> To: 'Dick Hardt'; 'McGovern, James F ((HTSC, IT))'
> Cc: specs@openid.net
>
lf
> Of Drummond Reed
> Sent: Monday, April 02, 2007 11:26 AM
> To: 'Dick Hardt'; 'McGovern, James F ((HTSC, IT))'
> Cc: specs@openid.net
> Subject: RE: Features for Future Versions
>
> James,
>
> I agree with Dick's feedback. I don't belie
net
Subject: Re: Features for Future Versions
On 2-Apr-07, at 8:09 AM, McGovern, James F ((HTSC, IT)) wrote:
> I originally joined this list with the hopes of injecting support
> for relationships, authorization and attestation into the
> specification but have been somewhat dis
On 2-Apr-07, at 8:09 AM, McGovern, James F ((HTSC, IT)) wrote:
> I originally joined this list with the hopes of injecting support
> for relationships, authorization and attestation into the
> specification but have been somewhat disappointed. I do have the
> following questions?
>
> 1. Wil
I originally joined this list with the hopes of injecting support for
relationships, authorization and attestation into the specification but have
been somewhat disappointed. I do have the following questions?
1. Will OpenID avoid incorporating features where identity selectors such as
Cardspac