Definitions #3

Open
opened 3 years ago by andrewjskatz · 0 comments
Owner

Definitions are surrounded with double asterisks: Definition

They render as "Definition".

Each time a definition is used in a document, it should be added to a list.

When you use a definition, you surround it with underscores. So in this case you would have Definition.

When you start to type a work beginning with an underscore, you should get a pick list/autocomplete of Definitions that have already been defined to choose from. That way, you can tell what definitions have already been defined, and which ones haven't.

Subsequent functionality:

  1. A contract can have one (and only one) section headed "Definitions" or "Definitions and Interpretation" (which can either be in the body of a contract or in an Appendix). Any definitions which have been used (my definition) but which have not yet been defined cause an automatic entry in the Definitions section starting

My Definition means []

  1. We need syntax for the definition text itself. In the above example, we could surround the definition text with [ and ] for example. So in the above example, we could have

My Definition means [the definition I am using at the moment]

That will then allow us to have a popup or mini window somewhere on the screen which displays the actual definition.

  1. Following from the above, if something is defined inline, but not in the "Definitions" section, then we automatically add the wording:

**My Definition ** is defined in Section [section number]

  1. A reordering option to allow the definitions in the definitions to be ordered in alphabetical order.

  2. A "dependency" ordering option, which allows the definitions to be ordered alphabetical, and then by dependency. So if we have

Sausage Price means [the price of a single Sausage] and
Sausage means [a delicious tube of salt, fat and protein]

Then we ensure that Sausage is ordered before Sausage Price, and immediately before it if possible.

  1. A "order of use" option which allows the definitions to be ordered in the order in which they are used in the contract.

  2. A set of different colours for definitions, indicating whether they have been defined or are pending definition.

Definitions are surrounded with double asterisks: **Definition** They render as "Definition". Each time a definition is used in a document, it should be added to a list. When you use a definition, you surround it with underscores. So in this case you would have _Definition_. When you start to type a work beginning with an underscore, you should get a pick list/autocomplete of Definitions that have already been defined to choose from. That way, you can tell what definitions have already been defined, and which ones haven't. Subsequent functionality: 1. A contract can have one (and only one) section headed "Definitions" or "Definitions and Interpretation" (which can either be in the body of a contract or in an Appendix). Any definitions which have been used (_my definition_) but which have not yet been defined cause an automatic entry in the Definitions section starting > **My Definition** means [] 2. We need syntax for the definition text itself. In the above example, we could surround the definition text with *[ and ]* for example. So in the above example, we could have > **My Definition** means *[the definition I am using at the moment]* That will then allow us to have a popup or mini window somewhere on the screen which displays the actual definition. 3. Following from the above, if something is defined inline, but not in the "Definitions" section, then we automatically add the wording: > **My Definition ** is defined in Section [section number] 4. A reordering option to allow the definitions in the definitions to be ordered in alphabetical order. 5. A "dependency" ordering option, which allows the definitions to be ordered alphabetical, and then by dependency. So if we have > **Sausage Price** means *[the price of a single _Sausage_]* and > **Sausage** means *[a delicious tube of salt, fat and protein]* Then we ensure that **Sausage** is ordered before **Sausage Price**, and immediately before it if possible. 6. A "order of use" option which allows the definitions to be ordered in the order in which they are used in the contract. 7. A set of different colours for definitions, indicating whether they have been defined or are pending definition.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.