add new aas repo identifiable profile

[sebbader-sap]

Close #496

[mjacoby]

There are some API calls that have been added/removed according to the proposal at #496 (comment)

✅ 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}
🆕 get /shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/attachment
🆕 put /shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/attachment
🆕 delete /shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/attachment

What is the motivation for these deviations?
At first glance, I do not see any reason to not include the calls to /shells/{aasIdentifier}/asset-information and /shells/{aasIdentifier}/submodel-refs.

Regarding the calls to /shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/attachment I think I understand the intention, as without them no access to the files is possible at all. However, this feels like breaking the intention of the profile that no submodel element-level access should be supported. An alternative would be to add the serialization interface (which could be limited to AASX format) which then would enable access to files.

[BirgitBoss]

inconsistency

in the .yaml there are also contained but not listed here in text:

GetAllAssetAdministrationShells

Not contained in .yaml:
PostSubmodel

[sebbader-sap]

in the .yaml there are also contained but not listed here in text:
GetAllAssetAdministrationShells
Indeed, have removed it from the OpenAPI file as well. The use cases needing this profile have a lot (millions of Shells and Submodels) of data objects, the GetAll... operations are not feasible at all.

[sebbader-sap]

Not contained in .yaml:
PostSubmodel
This is on purpose: The AAS Repository does not have the PostSubmodel operation.

[BirgitBoss]

why only Content "Normal", "Value" also and also the other formats, no?

[sebbader-sap]

No, this is also on purpose: A client in a basic AAS interaction is not aware of the Descriptor or any other metadata source, therefore, always the "Normal" serialisation with the full content is needed.

[sebbader-sap]

There are some API calls that have been added/removed according to the proposal at #496 (comment)

✅ 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} 🆕 get /shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/attachment 🆕 put /shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/attachment 🆕 delete /shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/attachment

What is the motivation for these deviations? At first glance, I do not see any reason to not include the calls to /shells/{aasIdentifier}/asset-information and /shells/{aasIdentifier}/submodel-refs.

/shells/{aasIdentifier}/asset-information and /shells/{aasIdentifier}/submodel-refs are included in the listed operations: asset-information are part of the AAS object, same for submodels (API path /submodel-refs). A client can get this information therefore, no need for fine-grained (but only rarely used) endpoints.

Regarding the calls to /shells/{aasIdentifier}/submodels/{submodelIdentifier}/submodel-elements/{idShortPath}/attachment I think I understand the intention, as without them no access to the files is possible at all.

Indeed, the access to files, in particular HandoverDocumentation files, is absolutely needed. The vast majority of AAS interactions required this submodel, and there is simply no other way if the approach via AASX file exchange is nor possible.