Q: How should ValueIDs be using within Submodels to model to model ENUMS from IEC 61360-based semantic dictionaries like CDD and ECLASS.
A:
In scope of AAS modeling, the concept of ValueIDs should be used to map those ENUMS. Typically enum values have a string representation and an IRDI for unique identification. AAS specs state the following usage guide:
Which can be seen in the example of "IP65"( IEC 61360 english preffered name) as value. Preferred name should be English only - translation can be done by a look-up of the IRDI if needed.
We encourage using both the string value and the equivalent ValueID to provide best human and machine-readability.
The IRDI of the value list itself should be used in submodel template definitions to restrict the allowed sting values.
Q: How should ValueIDs be using within Submodels to model to model ENUMS from IEC 61360-based semantic dictionaries like CDD and ECLASS. A: In scope of AAS modeling, the concept of ValueIDs should be used to map those ENUMS. Typically enum values have a string representation and an IRDI for unique identification. AAS specs state the following usage guide:
Which can be seen in the example of "IP65"( IEC 61360 english preffered name) as value. Preferred name should be English only - translation can be done by a look-up of the IRDI if needed.
We encourage using both the string value and the equivalent ValueID to provide best human and machine-readability.
The IRDI of the value list itself should be used in submodel template definitions to restrict the allowed sting values.