[Specs-cx] Data I/F

[nara hideki]

CX itself do not have to  be  AX compliant.
I think consistency is important.  Application programmer usually uses
library which someone has built.

And how about request authentication ?  If a request is  CX compliant,
the response data can be encrypted in the same way to encrypt CX
Contract.
Do you want to define the other way to resolve this kind issues?

----
hdknr

2010/4/30 Nat Sakimura <n-sakimura at nri.co.jp>:
> Do you think it has to be an AX request?
> I think it is a bit of overkill. It does not have to carry all the overhead.
>
> We can just make it completely RESTful, as I suggested, like:
>
> Endpoint_url?contract=contract_URL
>
> =nat
>
> (2010/04/30 11:52), nara hideki wrote:
>>
>> True.  Thinking of in consistent with other CX request, the following
>> is a way  to get service output defined in a CX Contract.
>>
>>
>> Claiming Service
>> ==================
>>
>> Relying Party MAY claim service concluded in a CX Contract.
>>
>> Request
>> --------
>>
>> * openid.ax.mode
>>
>>    REQUIRED. Value: “fetch_request”
>>
>> * openid.ax.type.cx
>>
>>    REQUIRED. Value: “http://openid.net/srv/cx/1.0/#claim” .
>>
>> * openid.ax.value.cx
>>
>>    REQUIRED. Value:  Identifier for a particular CX Contract.
>>
>> * openid.ax.required
>>
>>    REQUIRED. Value: ‘cx’ MUST be included in the AX required list.
>>
>> Response
>> --------
>>
>> * openid.ax.mode
>>
>>    REQUIRED. Value: “fetch_response”
>>
>> * openid.ax.type.cx
>>
>>    REQUIRED. Value: “http://openid.net/srv/cx/1.0/#claim” .
>>
>> * openid.ax.value.cx
>>
>>    REQUIRED. Value:  Identifier for a particular CX Contract.
>>
>> * openid.ax.type.cx_service
>>
>>    REQUIRED. Value: “http://openid.net/srv/cx/1.0/#service” .
>>
>> * openid.ax.value.cx_service
>>
>>    REQUIRED. Value:  Base 64 encoded data of the service output
>> defined in the CX Contract.
>>
>>
>>
>>
>> 2010/4/30 Nat<sakimura at gmail.com>:
>>
>>>
>>> You still need to indicate what contract you are using to authorize the
>>> fetch.
>>>
>>> =nat @ Tokyo via iPhone
>>>
>>> On 2010/04/30, at 7:01, nara hideki<hdknr at ic-tact.co.jp>  wrote:
>>>
>>>
>>>>
>>>> CX depends AX.  I thinks that AX fetch in direct call can be fine.
>>>>
>>>> 2010/4/22 Nat Sakimura<sakimura at gmail.com>:
>>>>
>>>>>
>>>>> Here is my though about data fetch interface.
>>>>> Suppose https://example.com/datasource/ is the URI from which a
>>>>> recipient
>>>>> can obtain data based on the contract.
>>>>> Suppose http://example.org/contract/1234 is the URI of the Contract.
>>>>> Then, do
>>>>> GET http://example.com/datasource/(http://example.org/contract/1234)
>>>>> to obtain the data which is encrypted by the public key contained in
>>>>> the
>>>>> contract.
>>>>>
>>>>> --
>>>>> Nat Sakimura (=nat)
>>>>> http://www.sakimura.org/en/
>>>>> http://twitter.com/_nat_en
>>>>>
>>>>> _______________________________________________
>>>>> Specs-cx mailing list
>>>>> Specs-cx at lists.openid.net
>>>>> http://lists.openid.net/mailman/listinfo/openid-specs-cx
>>>>>
>>>>>
>>>>>
>>>
>>>
>>
>> _______________________________________________
>> Specs-cx mailing list
>> Specs-cx at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-cx
>>
>
>
> --
> Nat Sakimura (n-sakimura at nri.co.jp)
> Nomura Research Institute, Ltd.
> Tel:+81-3-6274-1412 Fax:+81-3-6274-1547
>
> 本メールに含まれる情報は機密情報であり、宛先に記載されている方のみに送信することを意図しております。意図された受取人以外の方によるこれらの情報の開示、複製、再配布や転送など一切の利用が禁止されています。誤って本メールを受信された場合は、申し訳ございませんが、送信者までお知らせいただき、受信されたメールを削除していただきますようお願い致します。
> PLEASE READ:
> The information contained in this e-mail is confidential and intended for
> the named recipient(s) only.
> If you are not an intended recipient of this e-mail, you are hereby notified
> that any review, dissemination, distribution or duplication of this message
> is strictly prohibited. If you have received this message in error, please
> notify the sender immediately and delete your copy from your system.
>
> _______________________________________________
> Specs-cx mailing list
> Specs-cx at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-cx
>