How to manage ConceptDescription correctly

[MarlonSchwank]

Hi,

In a recent hackherthon the question popped up of how to manage concept description correctly within your AAS.

We would like to clarify if the following approach is correct by the example of the SME “ManufacturerName” of the SM Nameplate V2.0 with the ConceptDescription “0173-1#02-AAO677#002” (ECLASS):

SemanticId of the SME:
Type: ExternalReference
KeyType: ConceptDescription
KeyValue: 0173-1#02-AAO677#002

IsCaseOf of the ConceptDescription element
Type: ExternalReference
KeyType: GlobalReference
KeyValue: 0173-1#02-AAO677#002

We collected a few uncertainties / questions here:

1. Should there be a local ConceptDescription element within the AAS for global unique IDs like ECLASS properties?
2. If yes should be the type of the semanticId of the SME an “External” or a “ModelReference” because there is a CD element within the enviorment of the AAS.
3. Is this the correct use of “isCaseOf” as shown above (demonstrate that the CD is copied from an external one)

Another discussed approach would be to not add ConceptDescription elements for Semantic IDs that link to an external unique ID (like ECLASS). But in this case the information from the DataSpecificationIEC61360 e.g., the UOM would not be linked directly to the SME.