Inconsistent OpenAPI specification for PutFileByPath

[mhrimaz]

The OpenAPI the specification mentions two parameter as form-data.

But in API specificaiton there is only a binary file payload.

So as an example in Postman, which type of request is valid?

Could you clarify on that?

[sebbader-sap]

The second one with the "form-data" option (adding implicitly the http header "multipart/form-data" to the request) is the right one. Please note that chapter 5 and all other ones before chapter 12 are protocol-independent and therefore not the normative context for HTTP calls.

[mjacoby]

This means that the HTTP PUT contains both the filename and file content in the body, correct? If yes, what is the expected behavior regarding the file name?

Image the following example...

Given the model

AAS -> Submodel (id=submodel1) -> File (idShort=file1) and the File.value is foo.pdf.

Now the following request is executed PUT submodels/c3VibW9kZWwx/submodel/submodel-elements/file1/attachment with body

• filename = bar.pdf
• file = ...

What is the expected behavior?

1. The call is rejected as invalid because the file name present the File object (foo.pdf) and the one provided in the request (bar.pdf) do not match?
2. Is the file name in the File object updated to the one provided in the request, i.e. File.value = bar.pdf after processing the request?
3. Is the filename in the request simply ignored and the file content is just written to the file given by File.value i.e. foo.pdf?
4. Something else not listed here

[BirgitBoss]

Are the "File" API operation dealing with submodel elements "Blob" or "File" or both? Please make this clearer in textual documentation. This is a constraint that the idPath needs to reference to a Blob

[sebbader-sap]

@aorzelskiGH can you have a look?