Skip to content

docs(access-rules): reference IDTA-01002 Operation-to-RIGHT annex#80

Draft
aorzelskiGH wants to merge 1 commit into
IDTA-01004-3-1_Workingfrom
docs/operation-to-right-mapping
Draft

docs(access-rules): reference IDTA-01002 Operation-to-RIGHT annex#80
aorzelskiGH wants to merge 1 commit into
IDTA-01004-3-1_Workingfrom
docs/operation-to-right-mapping

Conversation

@aorzelskiGH

Copy link
Copy Markdown
Contributor

Summary

Point the Access Rule Model at the new normative "Operation to RIGHT Mapping" annex that is introduced in IDTA-01002.

Problem

The indicative Rights-to-verbs table in access-rule-model.adoc is not sufficient to derive the required RIGHT for a concrete API operation (e.g. PUT /submodels/{id} => CREATE or UPDATE; POST .../invoke => EXECUTE; GET /shell-descriptors => VIEW). Implementations disagreed on these per-operation bindings.

Solution

Add a short paragraph after the indicative table that directs implementers to the normative per-operation mapping in IDTA-01002. The indicative mapping stays in place for orientation.

Affected files

  • documentation/IDTA-01004/modules/ROOT/pages/access-rule-model.adoc

Review notes

  • Paired API PR: admin-shell-io/aas-specs-api#586 introduces the new annex.
  • Editorial only; no BNF / JSON Schema changes.

Refs: Review Finding T-10

… 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
@Martin187187 Martin187187 marked this pull request as draft June 16, 2026 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants