Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify how to model streaming binary data (3.1.1 port of #3729) #3769

Merged
merged 1 commit into from
May 9, 2024

Conversation

handrews
Copy link
Member

@handrews handrews commented May 1, 2024

Also make the translation from 3.0 binary modeling a subsection, as otherwise the line about streaming either feels randomly inserted into the middle of the section, or feels disconnected when placed after the conversion table.

Also make the translation from 3.0 binary modeling a subsection,
as otherwise the line about streaming either feels randomly inserted
into the middle of the section, or feels disconnected when placed
after the conversion table.
@handrews handrews added clarification requests to clarify, but not change, part of the spec media and encoding Issues regarding media type support and how to encode data (outside of query/path params) labels May 1, 2024
@handrews handrews added this to the v3.1.1 milestone May 1, 2024
@handrews handrews requested a review from a team May 1, 2024 17:25
Copy link
Contributor

@mikekistler mikekistler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! 👍

@ralfhandl ralfhandl merged commit 8c6c0dd into OAI:v3.1.1-dev May 9, 2024
1 check passed
@handrews handrews deleted the streaming-binary-311 branch May 9, 2024 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification requests to clarify, but not change, part of the spec media and encoding Issues regarding media type support and how to encode data (outside of query/path params)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants