docs(access-rule-model): reference cross-spec terminology matrix (T-09)#81
Open
aorzelskiGH wants to merge 1 commit into
Open
docs(access-rule-model): reference cross-spec terminology matrix (T-09)#81aorzelskiGH wants to merge 1 commit into
aorzelskiGH wants to merge 1 commit into
Conversation
Add a NOTE in the grammar introduction that explicitly maps each FieldIdentifier prefix ($aas / $sm / $sme / $cd / $aasdesc / $smdesc) to the corresponding Metamodel class (IDTA-01001) and API resource path (IDTA-01002). References the new normative terminology matrix in IDTA-01001 as the single source of truth and states that prefixes are lower-case only. Refs: Review Finding T-09 Made-with: Cursor
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
|
||
| [NOTE] | ||
| ==== | ||
| The FieldIdentifier prefixes `$aas`, `$sm`, `$sme`, `$cd`, `$aasdesc` and `$smdesc` correspond directly to the Metamodel classes `AssetAdministrationShell`, `Submodel`, `SubmodelElement`, `ConceptDescription`, `AssetAdministrationShellDescriptor` and `SubmodelDescriptor`, and to the API resources `/shells`, `/submodels`, `.../submodel-elements/{idShortPath}`, `/concept-descriptions`, `/shell-descriptors` and `/submodel-descriptors` respectively. The normative cross-specification mapping is given in the "Terminology Across IDTA-01001, IDTA-01002 and IDTA-01004" section of IDTA-01001 (AAS Metamodel). All prefixes are lower-case; variants such as `$aasDesc` or `$SmDesc` MUST be rejected by conforming parsers. |
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 NOTE in the grammar introduction of the Access Rule Model chapter that explicitly maps each FieldIdentifier prefix (
$aas,$sm,$sme,$cd,$aasdesc,$smdesc) to the corresponding Metamodel class and API resource path, and points to the new normative cross-spec terminology matrix in IDTA-01001.Problem
The Access Rule Model chapter names the possible FieldIdentifier prefixes but does not make the link to Metamodel classes and API resources explicit. Across the three specs different surface forms are used for the same concept (
AssetAdministrationShellvs./shellsvs.$aas), which regularly produces small inconsistencies (e.g.$aasDescvs.$aasdesc).Solution
$aasDescMUST be rejected by conforming parsers.Affected files
documentation/IDTA-01004/modules/ROOT/pages/access-rule-model.adocReview notes
admin-shell-io/aas-specs-metamodel(introduces the matrix) andadmin-shell-io/aas-specs-api(mirrors this NOTE in the Query Language chapter).Refs: Review Finding T-09