From a8255b10bb9d00d772e4103bb36707da047ed516 Mon Sep 17 00:00:00 2001 From: Simeon Andreas Kepp Date: Sun, 19 Jul 2026 12:20:14 +0200 Subject: [PATCH] Fix inconsistent rule-number heading format for rule 219 Every other rule heading in the guidelines wraps its reference number in square brackets (e.g. "[218]", "[238]", "[126]"), but rule 219 ("MUST provide API audience") was missing the brackets, reading as "... API audience 219" instead of "... API audience [219]". This is the only such inconsistency in the document (checked against every "### ..." heading). The existing internal anchor link to this section (#must-provide-api-audience-219) is unaffected, since GitHub's heading-slug algorithm strips bracket characters either way. Co-authored-by: Laura Serna Gaviria --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0238bda..2f3c629 100644 --- a/README.md +++ b/README.md @@ -147,7 +147,7 @@ Following OpenAPI extension properties **should** be provided in addition: * #/info/contact/{name,url,email} the contact information for the exposed API. -### MUST provide API audience 219 +### MUST provide API audience [219] Each API must be classified with respect to the intended target **audience** supposed to consume the API, to facilitate differentiated standards on APIs for discoverability, changeability, quality of design and documentation, as well as permission granting. We differentiate the following API audience groups with clear organisational and legal boundaries: