[BUG]Data specification IEC61360 id does not work due to case sensitivity.

[JS-Aibel]

Describe the bug
According to “IDTA-01003-a-3-0_SpecificationAssetAdministrationShell_Part3a_DataSpecification_IEC61360”, the id of the Data Specification IEC61360 Template is https://admin-shell.io/DataSpecificationTemplates/DataSpecificationIec61360/3/0
By using the id, an error message in the Package Explorer (v2024-02-27) is saying that the
Data specification Reference could not be identified. Thus, no content attributes could be provided.

Expected behavior
By changing the letters IEC in the id to uppercase, Package Explorer is showing the attributes as expected.
https://admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/3/0

[juileetikekar]

Hi @JS-Aibel,

Could you please provide steps to reproduce, respective logs and screenshots for this issue?

[JS-Aibel]

Hi, @juileetikekar

1. Create a Concept Description with HasDataSpesification of type “DataSpecificationIEC61360”.

• If the id https://admin-shell.io/DataSpecificationTemplates/DataSpecificationIec61360/3/0 is used, an error message occurs as shown below.

• If the id https://admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/3/0 is used, the ConceptDescription behaves as expected.

2. When changing ids, make sure to save the file to see the effect.

The difference between the two ids is the uppercase letters EC in the word DataSpecificationIEC61360.

[MichaelHoffmeisterFesto]

Hello,

thanks for reporting this bug! It seems to be pretty severe. According to the latest spec, it is not only about case-mismatch of "IEC" vs "Iec", but also the scheme changed from scheme "http://" to "https://" (Spec 01003-a-3-0 from March 2023).
I would assume, that the Package Explorer implemented the (pre-liminary) URI and the spec changed this during the process without noticing.
As a result, I assume that a large number of wrong data specs are now in the wild.

For the current branch (MIHO/Post_XMAS2023_Bugfixes) I've now changed this. The AASPE uses the correct URI as a preset and takes both variants ("http://" and "https://") with case-insensitive matching.

[BirgitBoss]

Please also see this issue for the specification of the data specification itself:
admin-shell-io/aas-specs-iec61360#2 (comment)
We will provide a bugfix allowing both variants, with http and https. But probably we missed the Iec and IEC part.

[BirgitBoss]

Bugfix V3.0.2 of Part 3a and Bugfix V3.0.1 of Part 1 are now released. I hope that #233 will fix this issue as well.

[MichaelHoffmeisterFesto]

I hope I've fixed it now in the main branch.