Semantic code project
Create (or select) a standard proposition
Select a standard proposition. These will be coded with a “c-” and you can find a complete list here:
If there isn’t one, create a new one — but note, the name of the game is to have as few “canonical” propositions as possible. The form should be:
|
Name: t-[NAME]<noinclude>{{c|Template propositions}}</noinclude> |
Note:
- Change [NAME] and {VAR1}, {VAR2} and {VAR3} to suit your proposition. Note ALL ARE CASE SENSITIVE. Suggest using only lowercase. Bear in mind the command calling the template also has to be case-correct.
- “Label” above is fixed text and will help in correctly taxonomising. Don’t change this. Also leave <noinclude>{{c|Template propositions}}</noinclude> as is — this adds the template to the correct category and helps you to find it later.
Create a corresponding proposition in your agreement schema
You should have an agreement schema (a structured skeleton of the agreement in question. This has a unique taxonomised template name following this format: [Code] [Agreement] [Edition Year] [Clause reference]. For example, Section 1(a) of the 2002 ISDA is {{Code 2002 ISDA 1(a)}}
Create the new template (eg) {{Code 2002 ISDA 1(a)}} and call the template proposition using the “pr” template operator. eg: if you want to put a "right" operator in {{Code 2002 ISDA 1(a)}} template, insert: right [
- label [[:template:{{{label}}} rt|{{{label}}} rt]]
- who {{{who}}}
- action {{{action}}}
- how {{{how}}}
- when {{{when}}}
- condition {{{condition}}}] there. This should prompt you for a bunch of inputs which are not there yet (eg {{{label}}}, {{{action}}} etc).
To do
Devise a proposition labelling taxonomy, that can neatly (and predictably) cover: proposition type, agreement type, location and clause reference