Files
api-guidelines/evolution/naming-conventions.md
apidesigner dea91f6c6e Updates evolution/naming-conventions.md
Auto commit by GitBook Editor
2017-02-20 10:24:01 +01:00

1.2 KiB

Naming Conventions

General Naming Rules

  • Use lowercase ("snake_case")
  • Don't use acronyms
  • Use underscore to delimit words

Every identifier MUST be in lowercase except for abbreviations. Abbreviations MAY be in UPPERCASE. An identifier SHOULD NOT contain acronyms. Underscore (_) MUST be used to delimit combined words.

URI

Every URI MUST follow the General Rules. In addition, an URI MUST NOT end with a trailing slash (/).

Query Parameters and Path Fragments

Every URI query parameter or fragment MUST follow the General Rules. In addition, they MUST NOT clash with the reserved query parameter names.

URI Template Variables

In addition to General Naming Rules, URI Template Variable names MUST follow the RFC6570. That is, the variable names can consist only from ALPHA / DIGIT / "_" / pct-encoded.

NOTE: Per RFC6570 Hyphen (-) is NOT legal URI Template variable name character.

Representation Format Fields

Every representation format field MUST conform to the General Naming Rules.

Relation Type Identifier

HTTP Headers