Introduce a new Asset Administration Shell Repository Basic Profile

[sebbader-sap]

What is missing?

There are currently only three service profiles to describe an Asset Administration Shell Repository:

1. Full
2. Read
3. Query

#1 and #2 require that operations on Referables (SubmodelElements) are possible, while #3 requires query functionality. It is not possible to describe an Asset Administration Shell Repository that operates on Identifiables (AAS + Submodels).

How should it be fixed?

Add a new "Asset Administration Shell Repository - Basic Profile" (final name can be different), with these operations only:

• AAS Repository API:

  • GetAssetAdministrationShellById
  • GetAllAssetAdministrationShellsByAssetId
  • PostAssetAdministrationShell
  • PutAssetAdministrationShellById

• Submodel Repository API by superpath:

  • GetSubmodelById
  • PutSubmodelById

• Description API:

  • GetDescription

• I have signed the required Developer Certificate of Origin (DCO) already.

[aorzelskiGH]

I understand that this shall be a kind of minimal profile which shall:

• only include Identifiables, i.e. AAS and Submodel in this case
• not include ../submodel-elements
• only include normal serialization, i.e. not $reference, $metadata, $value, $path
• not include patch
• no serialization API

A possible name may also be "Asset Administration Shell Repository - Identifiable Profile".
Remark: A possible further profile may also be "Asset Administration Shell Repository - Identifiable Read Profile".

Related to the list above this would include the following API routes then:

get /shells
post /shells
get /shells/{aasIdentifier}
put /shells/{aasIdentifier}
delete /shells/{aasIdentifier}
get /shells/{aasIdentifier}/asset-information
put /shells/{aasIdentifier}/asset-information
get /shells/{aasIdentifier}/asset-information/thumbnail
put /shells/{aasIdentifier}/asset-information/thumbnail
delete /shells/{aasIdentifier}/asset-information/thumbnail
get /shells/{aasIdentifier}/submodel-refs
post /shells/{aasIdentifier}/submodel-refs
delete /shells/{aasIdentifier}/submodel-refs/{submodelIdentifier}
get /shells/{aasIdentifier}/submodels/{submodelIdentifier}
put /shells/{aasIdentifier}/submodels/{submodelIdentifier}
delete /shells/{aasIdentifier}/submodels/{submodelIdentifier}

If further restrictions are needed, it shall be thought about, if this can be handled by forbidding certain API routes.
Delete may simply return a NOT ALLOWED, but no specific related profile without delete would be defined.