From b1b75866c631f4759fb9229c59dba8b2bf99036f Mon Sep 17 00:00:00 2001 From: aorzelskiGH Date: Fri, 17 Apr 2026 17:17:11 +0200 Subject: [PATCH] docs(access-rules): reference IDTA-01002 normative Operation-to-RIGHT annex Point implementers to the new normative "Operation to RIGHT Mapping" annex in IDTA-01002 for the per-operation RIGHT / ROUTE binding. The indicative RIGHTS-to-verbs table in this spec stays in place for orientation. Refs: Review Finding T-10 Made-with: Cursor --- .../IDTA-01004/modules/ROOT/pages/access-rule-model.adoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/documentation/IDTA-01004/modules/ROOT/pages/access-rule-model.adoc b/documentation/IDTA-01004/modules/ROOT/pages/access-rule-model.adoc index 82e4493..5d7a488 100644 --- a/documentation/IDTA-01004/modules/ROOT/pages/access-rule-model.adoc +++ b/documentation/IDTA-01004/modules/ROOT/pages/access-rule-model.adoc @@ -159,6 +159,8 @@ The RIGHTS values are technology-neutral permissions. For HTTP/REST APIs these p The mapping in <> is intended to improve interoperability when ROUTE objects are used for authorization decisions. Concrete informative examples for RIGHTS, ROUTEs and HTTP requests are given in xref:annex/route-examples.adoc[]. +The normative operation-level mapping for the AAS HTTP/REST API (per-operation RIGHT and ROUTE) is defined in IDTA-01002 ยง "Operation to RIGHT Mapping" (annex). Implementations of this specification MUST follow that mapping when evaluating access rules against concrete HTTP operations. + [[table-rights-to-verbs]] .Indicative mapping of RIGHTS to AAS operation verbs and HTTP methods [cols="1,2,2,4",options="header"]