mirror of
https://github.com/adidas/api-guidelines.git
synced 2025-10-25 15:19:19 +00:00
Updates evolution/naming-conventions.md
Auto commit by GitBook Editor
This commit is contained in:
@@ -12,7 +12,6 @@ Every identifier **MUST** be in `lowercase` except for abbreviations. An identif
|
||||
Every URI **MUST** follow the General Rules. In addition, an URI **MUST NOT** end with a trailing slash (`/`).
|
||||
|
||||
#### Example
|
||||
|
||||
A well-formed URI:
|
||||
|
||||
```
|
||||
@@ -28,14 +27,12 @@ In addition to General Naming Rules, URI Template Variable names **MUST** follow
|
||||
> NOTE: Per RFC6570 Hyphen (`-`) is NOT legal URI Template variable name character.
|
||||
|
||||
#### Example
|
||||
|
||||
A well-formed URI Template Variable:
|
||||
|
||||
```
|
||||
/system_orders/{order_id}/author
|
||||
```
|
||||
|
||||
|
||||
## Representation Format Fields
|
||||
Every representation format field **MUST** conform to the General Naming Rules.
|
||||
|
||||
@@ -45,6 +42,8 @@ Every custom [relation identifier](https://github.com/for-GET/know-your-http-wel
|
||||
## HTTP Headers
|
||||
Every HTTP Header should use `Hyphenated-Pascal-Case`. A custom HTTP Header **SHOULD NOT** start with `X-` ([RFC6648](https://tools.ietf.org/html/rfc6648)).
|
||||
|
||||
#### Example
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user