Skip to content

Terminology and definitions #35

@maxashen

Description

@maxashen

This license is not intended to ... [s]tart arguments about terminology or definitions.

Apologies beforehand if I am trespassing on your intentions, but terminology and definitions are critical in licenses. For example the very word "argument" is ambiguous in this sense, it could mean one of two things:

  1. A discussion in which the parties involved express disagreement with one another; a debate
  2. An angry discussion involving disagreement among the participants; a quarrel

By context and good faith (that the above quotation is not a gag rule) I am assuming the intended meaning is the quarrel definition. But it is risky to leave ambiguity in a legal document! Ambiguity should only exist in a final draft when consensus could not be reached; only then is ambiguity an acceptable compromise. Why leave it to a judge to determine the meanings of words if there could be explicit definitions?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions