ID of data specification with http and/or https only

[BirgitBoss]

Is your feature request related to a problem? Please describe.
https://github.com/admin-shell-io/temp-aasx-package-explorer/issues/117

Allow both:
https://admin-shell.io/DataSpecificationTemplates/DataSpecificationIec61360/3/0 (as specified now)
and
http://admin-shell.io/DataSpecificationTemplates/DataSpecificationIec61360/3/0 (deprecated)

But should we support both for V3.1?

[BirgitBoss]

Proposal:

SemanticId for Data Specification IEC61360:

https://admin-shell.io/DataSpecificationTemplates/IEC61360/3/0

deprecated IDs:
https://admin-shell.io/DataSpecificationTemplates/DataSpecificationIec61360/3/0
and
http://admin-shell.io/DataSpecificationTemplates/DataSpecificationIec61360/3/0

The ID of the template was derived conformant to the rules for semantic IDs for metamodel and data specifications as defined in Part 1 “Metamodel” of the document series [AAS-Part1]:
"https://admin-shell.io/DataSpecificationTemplates/IEC61360/3/0"

Deviations: Instead of “DataSpecifications” as defined in the grammar “DataSpecificationTemplates” is used. Two IDs are deprecated but can still be used: in these cases the class name of the DataSpecificationContent was used instead of the name of the DataSpecification itself. Sometimes the ID was used with “https”, sometimes with “http”. “DataSpecificationTemplates” is also used in https://github.com/admin-shell-io/id/tree/master/DataSpecificationTemplates.

This ID will be used in hasDataSpecification/dataSpecification.

[BirgitBoss]

see #4
both are allowed, http is deprecated

[BirgitBoss]

see also eclipse-aaspe/package-explorer#196 (comment)
Iec and IEC seems also to be a mitmatch

[BirgitBoss]

Template IEC61360 id:

https://admin-shell.io/DataSpecificationTemplates/DataSpecificationIec61360/3/0
<<deprecated>> http://admin-shell.io/DataSpecificationTemplates/DataSpecificationIec61360/3/0
<<deprecated>> https://admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/3/0
<<deprecated>> http://admin-shell.io/DataSpecificationTemplates/DataSpecificationIEC61360/3/0

• all constraints corrected (from http to https)

[BirgitBoss]

Workstream AAS Specs 2024-06-13
resolution see admin-shell-io/aas-specs#307

[BirgitBoss]

resolved as described in admin-shell-io/aas-specs#307 (comment)