<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Nat,<br>
<br>
Can you define the term "contract"? Is it legally binding? It is just a
signed set of attributes? Who are the parties involved with signing the
contract? The RP, OP, and user? Instead of defining a new CX extension,
would it just be sufficient to define new attributes using AX?<br>
<br>
Would it make more sense to use OAuth instead of defining a new OpenID
extension? OAuth is designed to allow a user to authorize an RP (aka
Consumer) to access protected resources hosted by the user's OP (aka
Service Provider). It might make more sense to use the OpenID+OAuth
hybrid protocol along with an OAuth protected web service to exchange
contract information.<br>
<br>
Thanks<br>
Allen<br>
<br>
<br>
<br>
<br>
Nat Sakimura wrote:
<blockquote
cite="mid:bf26e2340901130123v2227546xd73b629898e8ed90@mail.gmail.com"
type="cite">I have edited the Contract Exchange Proposal on the wiki. <br>
<br>
<a moz-do-not-send="true"
href="http://wiki.openid.net/Working_Groups%3AContract_Exchange_1">http://wiki.openid.net/Working_Groups%3AContract_Exchange_1</a><br>
<br>
It is substantially shorter and easier to parse, hopefully. <br>
<br>
Please discuss. <br clear="all">
<br>
-- <br>
Nat Sakimura (=nat)<br>
<a moz-do-not-send="true" href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
specs mailing list
<a class="moz-txt-link-abbreviated" href="mailto:specs@openid.net">specs@openid.net</a>
<a class="moz-txt-link-freetext" href="http://openid.net/mailman/listinfo/specs">http://openid.net/mailman/listinfo/specs</a>
</pre>
</blockquote>
<br>
</body>
</html>