Skip to content

Instantly share code, notes, and snippets.

@brwillis

brwillis/semantics-and-compliance-md

Created May 5, 2016 17:03
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save brwillis/8f4bce1093251c38f08d983ad2d89e5c to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save brwillis/8f4bce1093251c38f08d983ad2d89e5c to your computer and use it in GitHub Desktop.
Download ZIP
Raw
semantics-and-compliance-md
# Semantics and Compliance
Interpret the key words **MUST**, **MUST NOT**, **REQUIRED**, **SHALL**, **SHALL NOT**, **SHOULD**, **SHOULD NOT**, **RECOMMENDED**, **MAY** and **OPTIONAL** in this document as follows:
- **MUST** This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification.
- **MUST NOT** This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification.
- **SHOULD** This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. Exceptions require Brand Marketing Operations approval.
- **SHOULD NOT** This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. Exceptions require Brand Marketing Operations approval.
- **MAY** This word, or the adjective "OPTIONAL", mean that an item is truly optional.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment