Versioning of API Operations

[sebbader-sap]

We need to clarify the behavior of version upgrades for API Operations in new (minor) releases.

Status Quo

• Full Profile of the AAS Repository (V3.0.x_SSP-001)
  - API Operations with x-semanticIds like https://admin-shell.io/aas/API/GetAllAssetAdministrationShells/3/0
• Full Profile of the AAS Repository (V3.1.0_SSP-001)
  - API Operations with x-semanticIds like https://admin-shell.io/aas/API/GetAllAssetAdministrationShells*/3/0* (as the API Operation has not been changed)
• Query Profile (V3.1.0_SSP-003)
  - API Operations with x-semanticIds like https://admin-shell.io/aas/API/QueryAssetAdministrationShells/3/1 (as the API Operation has been introduced with V3.1)

Alternative

• Full Profile of the AAS Repository (V3.0.x_SSP-001)
  - API Operations with x-semanticIds like https://admin-shell.io/aas/API/GetAllAssetAdministrationShells/3/0
• Full Profile of the AAS Repository (V3.1.0_SSP-001)
  - API Operations with x-semanticIds like https://admin-shell.io/aas/API/GetAllAssetAdministrationShells*/3/1* (as the API Operation is now part of a V3.1 Profile, even though it is identical to the .../3/0 one)
• Query Profile (V3.1.0_SSP-003)
  - API Operations with x-semanticIds like https://admin-shell.io/aas/API/QueryAssetAdministrationShells/3/1 (as the API Operation has been introduced with V3.1)

Question to be discussed: Shall all API Operations of a higher Profile share the same (minor) version?
see also #229

[sebbader-sap]

Point of view as of 21.01.2025: Independent versioning of API Operations introduces a significant maintenance effort while not clearly providing added value...