Correct statement that media type */* is equivalent to application/octet-stream

The OAS 3 documentation states:

application/octet-stream: # any media type is accepted, functionally equivalent to */*

I believe the intent here it to state that the type application/* is functionally equivalent to application/octet-stream. Perhaps not. At any rate, */*, if * is a wildcard, would not thought to be equivalent to application/octet-stream in the common sense, as the wildcard for type (remember, media type is {type} + '/' + {subtype}) should be taken to allow text, image, multipart, message, and so on in addition to application. If my spec says my service endpoint accepts */*, I don’t want the callers to infer from OAS documentation that they are required to send some subtype of application.

It could also be that I’m missing something that came out of internal discussion. Can you please explain this decision so my teams can better understand how to interact with the spec or otherwise consider my request to change the specification and existing documentation?

[MikeRalphson]

Will be included in v3.0.3. Thanks again for pointing this out.

[darrelmiller]

We shall remove the comment “# any media type is accepted, functionally equivalent to */*” as it does not appear to add any value.