Key Terms

Within this document, the keywords “MUST”, “MUST NOT”, “SHOULD”, “SHOULD NOT”, and “MAY” are to be interpreted as described in the table below. Note that “MUST” is not intended to convey that publishing an API may be blocked if it does not comply but that the API MUST look and behave this way if we are to achieve a cohesive, consistent experience across the whole platform catalog.

Keyword	Interpretation
MUST	Adherence is critical to a consistent client-side developer experience.
MUST NOT	Avoidance is critical to a consistent client-side developer experience.
SHOULD	Adherence is recommended for a good client-side developer experience.
SHOULD NOT	Avoidance is recommended for a good client-side developer experience.
MAY	Encouraged. The client-side developer experience won’t be negatively impacted if this is not implemented.