docs(annex): add informative Conformance Test Corpus (T-16)#84
Open
aorzelskiGH wants to merge 1 commit into
Open
docs(annex): add informative Conformance Test Corpus (T-16)#84aorzelskiGH wants to merge 1 commit into
aorzelskiGH wants to merge 1 commit into
Conversation
Introduce a new annex that defines a structured, informative set of acceptance tests for conforming implementations of the Access Rule Model. The corpus covers: - Rule loading and validation (JSON/BNF consistency) - Rule evaluation (default deny, permit-overrides, inapplicable rules, formula runtime errors, filter combination) - RIGHTS / operation mapping - Supplemental semantic IDs in rule scopes - Descriptor FieldIdentifier applicability per profile Each test case has a stable ID, one-line purpose and expected behaviour, so the corpus can be turned directly into an executable conformance test suite. Aligned with the matching corpus in IDTA-01002. Refs: Review Finding T-16 Made-with: Cursor
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| | ID | Purpose | Expected | ||
|
|
||
| | RIGHT.map.001 | ||
| | A `GET` on a resource MUST require the RIGHT `READ` according to xref:annex/operation-to-right-mapping.adoc[] of IDTA-01002. |
| This work is licensed under a [Creative Commons Attribution 4.0 International License]( | ||
| https://creativecommons.org/licenses/by/4.0/). | ||
|
|
||
| SPDX-License-Identifier: CC-BY-4.0 |
| //// | ||
|
|
||
| [#conformance-test-corpus] | ||
| = Conformance Test Corpus (informative) |
|
|
||
| This annex defines an informative but structured set of *acceptance tests* for conforming implementations of the AAS Access Rule Model defined in this specification. The corpus is intentionally technology-neutral and worded as a set of test cases; an implementation is said to be conformant to a given area if it passes every required test case in that area. | ||
|
|
||
| The corpus is aligned with the conformance test corpus in IDTA-01002 Part 2: Application Programming Interfaces xref:bibliography.adoc#bib2[[2\]]. Tests that exercise shared formula grammar productions (logical expressions, comparisons, FieldIdentifiers, value literals, type casts, `$match`/`$and`/`$or`/`$not`) are normative for both specifications; IDTA-01002 is the single source of truth for those productions. |
| | ID | Purpose | Expected | ||
|
|
||
| | RIGHT.map.001 | ||
| | A `GET` on a resource MUST require the RIGHT `READ` according to xref:annex/operation-to-right-mapping.adoc[] of IDTA-01002. |
| | Only rules granting `READ` on the matching ROUTE allow the request. | ||
|
|
||
| | RIGHT.map.002 | ||
| | A `POST /.../operations/{idShortPath}/invoke` MUST require the RIGHT `EXECUTE`. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a new informative annex
Conformance Test Corpusto IDTA-01004 with a structured, technology-neutral set of acceptance tests that implementations of the Access Rule Model can run to demonstrate conformance.Problem
IDTA-01004 currently ships example rules but no structured catalogue of test / acceptance criteria. Reviewers and implementers rediscover the same edge cases on every release: default-deny behaviour, permit-overrides combination, treatment of inapplicable rules (
$aasdescin Repository profiles), runtime formula errors, filter combination semantics, RIGHTS mapping for PUT CREATE/UPDATE, supplementalSemanticIds scoping, etc.Solution
documentation/IDTA-01004/modules/ROOT/pages/annex/conformance-test-corpus.adoc.RULE.load.001,EVAL.combine.001,RIGHT.map.003,SUPP.rule.001,DESC.reg.001, ...), a one-line purpose, an expected behaviour and a requirement level.nav.adoc.Affected files
documentation/IDTA-01004/modules/ROOT/pages/annex/conformance-test-corpus.adoc(new)documentation/IDTA-01004/modules/ROOT/nav.adocReview notes
aas-specs-apiadds a matching corpus for the Query Language and HTTP/REST API.Refs: Review Finding T-16