aas-specs
aas-specs copied to clipboard
Support IRDI-Path from ECLASS
Is your feature request related to a problem? Please describe. In some cases IRDI path need to be added as semanticId to SubmodelElements
Example:
absolute path:
0173-1---ADVANCED_1_1#01-ADO063#012/0173-1#01-AHF601#001/0173-1#02-ABI555#001/0173-1#01-AHF842#001*1/0173-1#02-ABI115#001
relative path with block and cardinality:
0173-1#02-ABI555#001/0173-1#01-AHF842#001*1
Describe the solution you'd like A clear and concise description of what you want to happen.
<semanticId>
<type>ExternalReference</type>
<keys>
<key>
<type>GlobalReference</type>
<value>0173-1#02-ABI555#001</value>
</key>
<key>
<type>GlobalReference</type>
<value>0173-1#01-AHF842</value>
</key>
<key>
<type>FragmentReference</type>
<value>*1</value>
</key>
</keys>
</semanticId>
Describe alternatives you've considered
Alternative 2
use IRDI-path as one global reference
<semanticId>
<type>ExternalReference</type>
<keys>
<key>
<type>GlobalReference</type>
<value>0173-1#02-ABI555#001/0173-1#01-AHF842#001*1</value>
</key>
</keys>
</semanticId>
Alternative 3
introduce new key/type values to explicitly support IRDI-paths.
Additional context Add any other context or screenshots about the feature request here.
see also https://github.com/admin-shell-io/questions-and-answers/issues/94 for allowing AAS ID and Submodel ID within a Reference.