<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi,<br>
my original contribution agreement is here at the OpenID website:<br>
<a class="moz-txt-link-freetext" href="http://openid.net/ipr/Non-Assertion-Agreement/executed/">http://openid.net/ipr/Non-Assertion-Agreement/executed/</a><br>
But since there is some confusion about this, I attach a signed version
of the newer edition.<br>
<br>
I have two (mutually contradictory?) comments to the structure of the
contract::<br>
<br>
1.<br>
To keep the structure generic, I propose that <br>
>Main Content of this Contract<br>
>- What is to be provided (text)<br>
>- What is received in return (text)<br>
is replaced by the more symmetric (e.g. covering NDA and collaboration
agreements, rather than just seller/buyer relationships):<br>
Main Content of this Contract<br>
- Obligations of Party A (text)<br>
- Obligations of Party B (text)<br>
<br>
2.<br>
For specific "order confirmation" type of contracts compatibility with
the OASIS UBL 2.0 structure would be desirable, if it could be achieved
without too many complications<br>
<dl>
<dt><span class="term"> <span class="bold"><strong>UBL 2.0 Order</strong></span>
</span></dt>
<dd>
<p> <a
href="http://docs.oasis-open.org/ubl/os-UBL-2.0/uml/UBL-2.0-OrderDocumentAssembly.html"
target="_top">Order Class Diagram</a> </p>
<p> <a
href="http://docs.oasis-open.org/ubl/os-UBL-2.0/mod/maindoc/UBL-Order-2.0.ods"
target="_top">mod/maindoc/UBL-Order-2.0.ods</a> </p>
<p> <a
href="http://docs.oasis-open.org/ubl/os-UBL-2.0/mod/maindoc/UBL-Order-2.0.xls"
target="_top">mod/maindoc/UBL-Order-2.0.xls</a> </p>
</dd>
</dl>
<pre class="moz-signature" cols="72">
Best Regards,
Henrik Biering
=henrik
</pre>
<br>
<br>
Nat Sakimura skrev:
<blockquote
cite="mid:bf26e2340907072115k36a8f599s3f5cd6ac529582b7@mail.gmail.com"
type="cite">Hi. <br>
<br>
Sorry that it is so slow for me to get fully involved. <br>
<br>
I would like to start discussion from the concept. <br>
Without understanding the general concept, the discussion can go
sideways quite easily. <br>
<br>
The main aim of Contract Exchange is to define a way to exchange the
"(possibly) Legally Binding Contract" between parties. <br>
<br>
Thus, defining what should be in that Contract Document is one of the
main task of this WG. <br>
<br>
The other task is to define a protocol that enables parties to achieve
the creation and exchange of such contract documents. <br>
<br>
>From my experiecne, a contract generally has the following in it. <br>
<br>
Contract ID (uri)<br>
Party A (uri)<br>
Party B (uri)<br>
Signatory of Party A (text)<br>
Signatory of Party B (text) <br>
Contact Address of Party A (text or uri?)<br>
Contact Address of Party B (text or uri?)<br>
Main Content of this Contract<br>
- What is to be provided (text)<br>
- What is received in return (text)<br>
Term and Termination<br>
- Term / Validity Period of the Contract (Datetime-Datetime)<br>
- Termination (text)<br>
- Survival of Certain Terms (text)<br>
Damages<br>
- Explanation (text)<br>
- max amount from A to B (number?)<br>
- max amount from B to A (number?)<br>
Non Disclosure<br>
- How to specify (text)<br>
- How Long (datetime-datetime)<br>
Relationship to other Contracts (text)<br>
Signature of the Signatory of Party A (text)<br>
Date of the Signature A (datetime)<br>
Signature of the Signatory of Party B (text)<br>
Date of the Signature B (datetime)<br>
<br>
Is this generally good or are there anything that are necessary in
addition to these? <br>
<br>
Should we specify the schema for these or should we keep it to bare
minimal and let everything else be represented as text? <br>
Should we try to incorporate LegalXML etc. <br>
<br>
These are the kind of questions that I have in mind for the "Contract
as a document" portion. <br>
<br>
Fortunately, we have Scott Blackmer in this WG who is a knowledgeable
lawyer, so Scott could cast some insight on this issue. <br>
<br>
Then, there will be the protocol for exchanging this along with some
technical requirement such as inclusion of the public key of the
parties. <br>
I will touch on these on a separate post. <br>
<br>
Please discuss. <br>
<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-cx mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Specs-cx@openid.net">Specs-cx@openid.net</a>
<a class="moz-txt-link-freetext" href="http://openid.net/mailman/listinfo/specs-cx">http://openid.net/mailman/listinfo/specs-cx</a>
</pre>
</blockquote>
</body>
</html>