Hi.
I am kind of new to this field, and this topic may have been discussed
before, but since a Google search on [site:http://openid.net/pipermail/
attribute exchange external reference ] did not match anything, let me bring
this up.
On scanning http://openid.net/specs/openid-attribute-exchange-
The "attribute" exchanged can be a reference rather then the data
itself.
http://axschema.org/media/image/default/
Is an example.
-- Dick
On 4-Jun-07, at 12:23 AM, =nat wrote:
> Hi.
>
> I am kind of new to this field, and this topic may have been discussed
> before, but since a Google search
> So I ask again - does anyone see any issues with the
> fragments being used like this:
>
> http://openid.net/pipermail/specs/2007-May/001767.html
>
Seems reasonable in essence. But it adds complexity and
removes some immediacy of URL identifiers-as-is.
Do fragments need special handl
On 4-Jun-07, at 7:51 AM, Granqvist, Hans wrote:
>> So I ask again - does anyone see any issues with the
>> fragments being used like this:
>>
>> http://openid.net/pipermail/specs/2007-May/001767.html
>>
>
> Seems reasonable in essence. But it adds complexity and
> removes some immediacy of
Dick Hardt wrote:
> Hi Mark
>
> Let me restate your concern so that I'm sure I understand it:
...
> The OP would then store this attribute as
> axschemas.org/schema#SingleValuedSaluation
> for later retreival since it has learned what value the user would like
> to use in this case
Correct,
I would postulate that if you want to be able to prove your identity,
you cannot allow your credential to be lost, interpreting
"credential" to be all the information that bears onto establishing
your identity. (saying it this way, it is a tautology.)
This is independent of whether anybody u
