Birgit Boss

In Part 2 for interfaces  Mandatory and Cardinality are distinguished. So there might be an optional element but the cardinality is 1. No Null object allowed in this case....

TF 2024-06-12 Decision Proposal Handle valueId (with CD for values of enumerations) and isCaseOf of ConceptDescriptions like all other references to semantic definitions

Workstream AAS Spec 2024-06-13 accepted, handling the same as for semanticId

Decision Proposal TF Part 1 2024-05-15 Besides https://github.com/admin-shell-io/aas-specs/issues/412#issuecomment-2061377393 make the following attributes optional as well: **File/contentType Blob/contentType** Reason: - contentType may not be fixed at time of creation of a...

Workstream AAS Sepc 2024-06-13 accepted make the following attributes optional - (Annotated)RelationshipElement/first - (Annotated)RelationshipElement/second - File/contentType - Blob/contentType

Decision Work Stream AAS Specifications 2023-12-14: individual versioning

@mristin yes, I assumed so. However, what aas-core defined is not the namespace for the elements but just the version of the specification as a whole the elements are part...

2024-03-07 Workstream AAS Discussion: Distinguish between: - Generating Schema - Redirect semantic Identifier - Documentation  Alternatives discussed: A) (revise decision) increase all versions (of classes and operations and profiles...

solved in IDTA-01001-3-0-1: https://industrialdigitaltwin.org/wp-content/uploads/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf

Decision Proposal TF AAS Part 1: - no change It is true that Boolean Range does not make sense but it is the task of SMT creators to only define...