[Specs-cx] Data I/F

[nara hideki]

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
>>>
>>>
>