[Openid-specs-ab] "id" for identifying a OpenID message

nara hideki hdknr at ic-tact.co.jp
Tue Jun 8 08:29:38 UTC 2010


I mean "id" is mostly equal to XML's id attribute and "id" can be used
in response JSON as well.
But I'd not stick to my idea.

Regards.

2010/6/8 Nat <sakimura at gmail.com>:
> Does it have to be 'id' or could it have a more discriptive name such as
> 'request_id'?
>
> =nat
>
> On 2010/06/08, at 16:50, nara hideki <hdknr at ic-tact.co.jp> wrote:
>
>> xs:anyURI is fine.
>>
>> As you say, it implicitly means request_file parameter in artifact
>> binding authentication request file.
>> We can think that "ns" is a "class id" and "id" is an "instance id" if
>> a request file is stored in persistance.
>>
>> CX needs this kinda parameter anyway. I just want this to be a
>> reserved parameter so that other extensions would not use this in
>> different semantic.
>>
>> 2010/6/8 Nat Sakimura <sakimura at gmail.com>:
>>>
>>> What is the semantics?
>>> Is it an identifier of this request_file?
>>> How can we ensure that it is unique across the domains?
>>> Is it type xs:String or xs:anyURI?
>>>
>>> On Tue, Jun 8, 2010 at 2:16 PM, nara hideki <hdknr at ic-tact.co.jp> wrote:
>>>>
>>>> Actually an addition like this.
>>>>
>>>> 5.3.  Request File
>>>>
>>>> ....(cut)...
>>>>
>>>> Following is the list of variables to be sent:
>>>>
>>>>  ....(cut)....
>>>>
>>>>   * id
>>>>
>>>>         Value: (Optional) unique identifier to refer the information
>>>> set held in JSON format.
>>>>
>>>>   ...(cut)....
>>>>
>>>> 2010/6/8 Nat Sakimura <sakimura at gmail.com>:
>>>>>
>>>>> Could you give me an example text modification?
>>>>> =nat
>>>>>
>>>>> On Tue, Jun 8, 2010 at 10:32 AM, nara hideki <hdknr at ic-tact.co.jp>
>>>>> wrote:
>>>>>>
>>>>>> No, I mean the identifier to JSON node itself.
>>>>>>
>>>>>> 2010/6/7 Nat Sakimura <sakimura at gmail.com>:
>>>>>>>
>>>>>>> Do yo mee the Identifier of the Subject?
>>>>>>> Then, it has. It has subject_id.
>>>>>>> =nat
>>>>>>>
>>>>>>> On Mon, Jun 7, 2010 at 12:40 PM, Hdknr TACT <hdknr at ic-tact.co.jp>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> hi all,
>>>>>>>>
>>>>>>>> I'm working on CX with Nat and other experts.
>>>>>>>> As the subject says, "id" parameter would help us. Because,
>>>>>>>>
>>>>>>>> (1) easy to refer a message in persistence.
>>>>>>>> (2) easy to refer the other contained (sub,sibling) messages.
>>>>>>>>
>>>>>>>> I know that authentication messages are rather short living than CX
>>>>>>>> messages and "id" is not necessary, but reserving "id" would make CX
>>>>>>>> and
>>>>>>>> other coming extensions easier.
>>>>>>>>
>>>>>>>> Best regards.
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Openid-specs-ab mailing list
>>>>>>>> Openid-specs-ab at lists.openid.net
>>>>>>>> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Nat Sakimura (=nat)
>>>>>>> http://www.sakimura.org/en/
>>>>>>> http://twitter.com/_nat_en
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Nat Sakimura (=nat)
>>>>> http://www.sakimura.org/en/
>>>>> http://twitter.com/_nat_en
>>>>>
>>>
>>>
>>>
>>> --
>>> Nat Sakimura (=nat)
>>> http://www.sakimura.org/en/
>>> http://twitter.com/_nat_en
>>>
>


More information about the Openid-specs-ab mailing list