Skip to content
Browse files

Draft3 : Abstrat is updated

  • Loading branch information...
1 parent e424d97 commit c84184e0e1b8c9ee1cd1303583bb1a91ecf51810 hdknr committed
Showing with 20 additions and 5 deletions.
  1. +6 −1 spec/draft-3/abstract.tmpl
  2. +7 −2 spec/openid-cx.draft-3.html
  3. +7 −2 spec/openid-cx.draft-3.xml
View
7 spec/draft-3/abstract.tmpl
@@ -1,2 +1,7 @@
-<t> This extension defines 1) An extensible Contract format, 2) Protocol to exchange the Contract. Contact consists of Proposal and Agreement. The Proposer creates a signed Proposal and send it to the counter party. The counter party, upon agreeing to it, signs the Agreement. The combination of the Proposal and Agreement is the mutually signed contract, which is potentially legally binding. This Contract needs to be stored by both parties for a given length of time, usually spanning over many years depending on jurisdictions. </t>
+<t> This extension defines 1) an extensible Contract format, 2) protocol to exchange the Contract, 3)protocol to share privacy data based on the Contract and 4)protocol to provide access log.
+The Proposer creates a signed Proposal which describes what privacy data is wanted and send it to the Signatory specified the End User.
+The Signatory, upon agreeing to it, signs agreements and provides the Contract.
+The combination of the Proposal and Contract is the mutually signed and is potentially legally binding.
+This Contract needs to be stored by all bound parties for a given length of time, usually spanning over many years depending on jurisdictions.
+</t>
<t> As these document size may be large while the user agent capability may be limited (e.g., mobile phones), sending them via direct communication and passing only the small reference called "Artifact" through the user agents are advisable. Therefore, as the protocol, use of Artifact Binding is strongly recommended. </t>
View
9 spec/openid-cx.draft-3.html
@@ -146,13 +146,18 @@
<tr><td class="header">&nbsp;</td><td class="header">NRI</td></tr>
<tr><td class="header">&nbsp;</td><td class="header">H. Nara</td></tr>
<tr><td class="header">&nbsp;</td><td class="header">TACT Communications,Inc</td></tr>
-<tr><td class="header">&nbsp;</td><td class="header">October 27, 2010</td></tr>
+<tr><td class="header">&nbsp;</td><td class="header">November 04, 2010</td></tr>
</table></td></tr></table>
<h1><br />Contract Exchange Extension 1.0 - Draft 3</h1>
<h3>Abstract</h3>
-<p> This extension defines 1) An extensible Contract format, 2) Protocol to exchange the Contract. Contact consists of Proposal and Agreement. The Proposer creates a signed Proposal and send it to the counter party. The counter party, upon agreeing to it, signs the Agreement. The combination of the Proposal and Agreement is the mutually signed contract, which is potentially legally binding. This Contract needs to be stored by both parties for a given length of time, usually spanning over many years depending on jurisdictions.
+<p> This extension defines 1) an extensible Contract format, 2) protocol to exchange the Contract, 3)protocol to share privacy data based on the Contract and 4)protocol to provide access log.
+The Proposer creates a signed Proposal which describes what privacy data is wanted and send it to the Signatory specified the End User.
+The Signatory, upon agreeing to it, signs agreements and provides the Contract.
+The combination of the Proposal and Contract is the mutually signed and is potentially legally binding.
+This Contract needs to be stored by all bound parties for a given length of time, usually spanning over many years depending on jurisdictions.
+
</p>
<p> As these document size may be large while the user agent capability may be limited (e.g., mobile phones), sending them via direct communication and passing only the small reference called "Artifact" through the user agents are advisable. Therefore, as the protocol, use of Artifact Binding is strongly recommended.
</p><a name="toc"></a><br /><hr />
View
9 spec/openid-cx.draft-3.xml
@@ -70,10 +70,15 @@
</address>
</author>
- <date day="27" month="October" year="2010" />
+ <date day="04" month="November" year="2010" />
<abstract>
- <t> This extension defines 1) An extensible Contract format, 2) Protocol to exchange the Contract. Contact consists of Proposal and Agreement. The Proposer creates a signed Proposal and send it to the counter party. The counter party, upon agreeing to it, signs the Agreement. The combination of the Proposal and Agreement is the mutually signed contract, which is potentially legally binding. This Contract needs to be stored by both parties for a given length of time, usually spanning over many years depending on jurisdictions. </t>
+ <t> This extension defines 1) an extensible Contract format, 2) protocol to exchange the Contract, 3)protocol to share privacy data based on the Contract and 4)protocol to provide access log.
+The Proposer creates a signed Proposal which describes what privacy data is wanted and send it to the Signatory specified the End User.
+The Signatory, upon agreeing to it, signs agreements and provides the Contract.
+The combination of the Proposal and Contract is the mutually signed and is potentially legally binding.
+This Contract needs to be stored by all bound parties for a given length of time, usually spanning over many years depending on jurisdictions.
+</t>
<t> As these document size may be large while the user agent capability may be limited (e.g., mobile phones), sending them via direct communication and passing only the small reference called "Artifact" through the user agents are advisable. Therefore, as the protocol, use of Artifact Binding is strongly recommended. </t>
</abstract>
</front>

0 comments on commit c84184e

Please sign in to comment.
Something went wrong with that request. Please try again.