Birgit Boss

The links you provide are working: where are the links not working?

Thanks for the finding. I would consider "`{min": "123"} `and `{"max": "123"}` as valid Value Only representations of a Range Submodel Element. So this information should be added to the...

2026-01-21 Workstream AAS Sepcs Range ist still on state, i.e. non-backward compatible changes are allowed. So we remove the sentences `If the min value is missing, the value is assumed...

issue transferred from Questions and Answers to metamodel workstream

There are three relevant specifications in SMT: The qualifier "OneToMany" (as used in https://github.com/admin-shell-io/aas-specs-metamodel/issues/644#issuecomment-3655285366) or "ZeroToMany" does not make any sense for a SML. In this case you would do...

2026-01-21 Workstream AAS Specs in Normal: [ [typeValueListElement: xsd:float value: 0.4], [ typeValueListElement: xsd:float] , [typeValueListElement: xsd:float value: 0.2 ] in ValueOnly [ [0.4],[0.2 ] ] ==> index for 0.2...

@MichaelHoffmeisterFesto may you please also have a look at this issue? Thank you. Birgit

Since the qualifier definitions are not part of the specification but of the How To create a SMT we can only discuss it in the corresponding workstream on SMT Process.

I forwarded it to the process group

Thank you for your questions and proposals. I would say that most of what you require is already specified. `Reference/referredSemanticId `states the semantics of the references element. `key/type` with [KeyTypes](https://industrialdigitaltwin.io/aas-specifications/IDTA-01001/v3.1.1/spec-metamodel/referencing.html#_key_types_enumeration)...