From 7da5a4bd576082b9ab0e365b508023d9401a41a8 Mon Sep 17 00:00:00 2001 From: BvanRaaij Date: Mon, 23 Feb 2026 15:34:21 +0100 Subject: [PATCH 1/4] Update designRules.md Changed statements to use consistent terms to Indicate Requirement Levels (MUST, SHOULD, ...) --- sections/designRules.md | 65 +++++++++++++++++++++++++++-------------- 1 file changed, 43 insertions(+), 22 deletions(-) diff --git a/sections/designRules.md b/sections/designRules.md index 60c76cb..c3f19b0 100644 --- a/sections/designRules.md +++ b/sections/designRules.md @@ -9,12 +9,13 @@ The REST architectural style is centered around the concept of a [=resource=]. A resource is an abstraction of a conceptual entity, identified by a globally unique [=URI=]. It may correspond to anything from a physical object (e.g. a building or a person) to an abstract concept (e.g. a permit, an event or today's weather). Although a resource is not tied to any specific exchange format, its current state can be transferred to clients through one or more representations, such as JSON or XML. +

Use nouns to name resources

Statement
- Resources are referred to using nouns (instead of verbs) that represent entities meaningful to the API consumer. + Resources MUST be referred to using nouns (instead of verbs) that represent entities meaningful to the API consumer.