Describe how Arazzo handles API responses that contain files.

Hey everyone!
I’m wondering whether the Arazzo community has already discussed how the specification should handle file responses from APIs.
I couldn’t find any open discussions on this topic so far.

There could be a variety of formats and approaches involved here.
Some file types could potentially already be consumed and processed using existing descriptions, such as .csv or .json files.
Some of the criterion object already can be applied to verify success or failure.

But overall, it seems that the specification currently lacks guidance around handling file responses.

For example:

• How should files be treated within workflows?
• Which file formats are expected or officially supported?
• Should tooling decide on its own whether file contents can or should be processed?
• Should success/failure criteria be applicable to file contents as well?

Looking forward to hearing your thoughts on this topic.

No files, tests, or entry points are identified in the issue. Start by reviewing the Arazzo specification sections covering workflows, API responses, and criterion objects, then seek agreement on supported file-response behavior. Done means the agreed guidance is incorporated into the specification and its examples or validation expectations are updated.