Closed
Description
What happens?
The table AASX File Server Interface
contains wrong operation names:
2+|Interface: [[AASX-File-Server]]AASX File Server
h|Operation Name h|Description
e|GetAllAASXPackageIds |Returns a list of available AASX packages at the server
e|GetAASXByPackageId |Returns a specific AASX package from the server
e|PostAASXPackage |Creates an AASX package at the server
--->e|PutAASXByPackageId |Replaces the AASX package at the server
--->e|DeleteAASXByPackageId |Deletes a specific AASX package
Why is this wrong?
In the following chapters Operations with names DeleteAASXPackageById and PutAASXPackageById are defined.
PutAASXByPackageId
vs. PutAASXPackageById
and DeleteAASXByPackageId
vs. DeleteAASXPackageById
How should it be fixed?
-
If
DeleteAASXPackageById
andPutAASXPackageById
are the correct operation names, the table should be updated accordingly.- In this case we have not consistent operation names. See:
GetAASXByPackageId
vs.PutAASXPackageById
and we should discuss if the suffixByPackageId
orPackageById
should be used.
- In this case we have not consistent operation names. See:
-
If
DeleteAASXByPackageId
andPutAASXByPackageId
are the correct operation names, the operation names in the corresponding Operation Chapters should be updated.