Introduce the IDTA Query Language #292
Draft
Conversation
This file contains 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
|
|
Add precedence: AND, OR, NOT Add types and casts: str(), num(), hex(), bool() Add xxx. in FieldIdentifiers, e.g. sm. or sme. Implicit casting to be discussed
This is the first complete grammar for query language and access rules of security.
* improve text * add select explanations * correct comparison operators * remove multilanguage fields * reorder sections * correct examples * add elemMatch * add special functions
…io/aas-specs-api into SeBa/query-language
* minor corrections * fix Typo * fieldIdentifier with <>
BirgitBoss
reviewed
Dec 4, 2024
| @@ -209,7 +209,7 @@ | |||
| <FieldIdentifierString> ::= <FieldIdentifierAAS> | <FieldIdentifierSM> | <FieldIdentifierSME> | <FieldIdentifierCD> | <FieldIdentifierAasDescriptor> | <FieldIdentifierSmDescriptor> | |||
| <FieldIdentifierAAS> ::= "aas." ( "$idShort" | "$displayName." <MultiLanguageClause> | "$description." <MultiLanguageClause> | "$id" | "$assetInformation.$assetKind" | "$assetInformation.$assetType" | "$assetInformation.$globalAssetId" | "$assetInformation." <SpecificAssetIdsClause> | "$submodel." <ReferenceClause> ) | |||
| <FieldIdentifierSM> ::= "sm." ( "$semanticId." <ReferenceClause> | "$idShort" | "$displayName." <MultiLanguageClause> | "description." <MultiLanguageClause> | "$id" ) | |||
| <FieldIdentifierSME> ::= "sme." <idShortPath>? ( "$semanticId." <ReferenceClause> | "$idShort" | "$displayName." <MultiLanguageClause> | "$description." <MultiLanguageClause> | "$value" | "$valueType" ) | |||
| <FieldIdentifierSME> ::= "sme." ( <idShortPath> ".")? ( "$semanticId." <ReferenceClause> | "$idShort" | "$displayName." <MultiLanguageClause> | "$description." <MultiLanguageClause> | "$value" | "$valueType" ) | |||
There was a problem hiding this comment.
use [] for optional parts. Do not mix [] and ? notation in AAS specs
Suggested change
| <FieldIdentifierSME> ::= "sme." ( <idShortPath> ".")? ( "$semanticId." <ReferenceClause> | "$idShort" | "$displayName." <MultiLanguageClause> | "$description." <MultiLanguageClause> | "$value" | "$valueType" ) | |
| <FieldIdentifierSME> ::= "sme." [ <idShortPath> "."] ( "$semanticId." <ReferenceClause> | "$idShort" | "$displayName." <MultiLanguageClause> | "$description." <MultiLanguageClause> | "$value" | "$valueType" ) |
Aorzelski/pr1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.