Jam: Useful parameters
In order for legal docs to be re-usable, it helps if we develop a common set of parameters that are called in various template documents. From the codification work done here is below what came out so far. Note the following naming convention: while files use underscore (Distribution_Core doc), parameters use dot.
Company
Company=Name of company
Co.Legalform=Inc. or LTD or however the legal structure is described
Co.Description=typical description that comes after the name in a legal doc, for example "a company registered in Delaware"
Co.FullAddress=
Co.Telephone=
Co.Fax=
Within the company itself there are people:
Co.Rep.Name=
Co.Rep.Title=
Other parties
Legal docs are between a company or a person and something (or somebody else). For example a partner or a Customer
Partner=
Partner.Legalform=
Partner.Description=
Partner.Rep.Name=
Partner.Rep.Title=
Customer=
Cust.Legalform=
Cust.Description=
Cust.Rep.Name=
Cust.Rep.Title=
Typical parameters within a contract
Effective.Date=
Yes!
You'll find pretty much this at - [http://www.commonaccord.org/index.php?action=source&file=./core/id/acme_incorporated]
Note the links to other persons and the link to the "class" ID_Entity. That links to ID. (Similar for ID_Female, which links to ID_Individual and then to ID. So a lot of variations of the address etc, he-she, are available.
Differences:
-
A few labels, and more granularity since some of the elements (like address) have to be recombined in different orders depending on context (sometimes separated by commas, sometimes by line breaks, sometimes you want only the city, etc.).
-
Since the person plays different roles (buyer in this agreement, licensor in another, president of a company in another) the info is generic and the roles are handled by prefixing. Persons form a graph, connected by prefixing.
The most important point is that this info will actually be defined once - by a provider, e.g. a telco which can assure participants of the identity of persons - a third party such as a credit service - or by the persons themselves reinforce by certification.
I am told that ldap is a relevant technology, and of course systems like OpenID and the blockchain have their methods.