title: How to address binary transfer protocols with multiple "fields" in OpenAPI 3.0?
body: <p>I have an API endpoint, that requires binary input. I have to document that using the OpenAPI 3.0 specification.</p>
  <p>The binary input of that API endpoints expects the following:</p>
  <div class="s-table-container">
  <table class="s-table">
  <thead>
  <tr>
  <th style="text-align: right;">Byte position</th>
  <th style="text-align: left;">Description</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td style="text-align: right;">0 - 15</td>
  <td style="text-align: left;">Nonce</td>
  </tr>
  <tr>
  <td style="text-align: right;">16 - EOS</td>
  <td style="text-align: left;">Data (until end of stream)</td>
  </tr>
  </tbody>
  </table>
  </div>
  <p>Another endpoint would expect the following:</p>
  <div class="s-table-container">
  <table class="s-table">
  <thead>
  <tr>
  <th style="text-align: right;">Byte position</th>
  <th style="text-align: left;">Description</th>
  </tr>
  </thead>
  <tbody>
  <tr>
  <td style="text-align: right;">0</td>
  <td style="text-align: left;">Action</td>
  </tr>
  <tr>
  <td style="text-align: right;">1 - 8</td>
  <td style="text-align: left;">Fixed data 1</td>
  </tr>
  <tr>
  <td style="text-align: right;">9</td>
  <td style="text-align: left;">Size (&quot;n&quot;) of data 2</td>
  </tr>
  <tr>
  <td style="text-align: right;">10 - 13</td>
  <td style="text-align: left;">Size (&quot;m&quot;) of data 3</td>
  </tr>
  <tr>
  <td style="text-align: right;">14 - 14+n</td>
  <td style="text-align: left;">Data 2</td>
  </tr>
  <tr>
  <td style="text-align: right;">15+n - 15+n+m</td>
  <td style="text-align: left;">Data 3</td>
  </tr>
  <tr>
  <td style="text-align: right;">16+n+m - EOS</td>
  <td style="text-align: left;">Data 4 (until end of stream)</td>
  </tr>
  </tbody>
  </table>
  </div>
  <p>Is this &quot;documentable&quot; at all with OpenAPI 3.0? I only have found simple &quot;single data&quot; binary upload (e.g. file uploads) and multipart file uploads. However, those does not apply to my scenario because I do not have fields (named or as an array), I have a &quot;raw binary protocol&quot;.</p>
  <p>Edit: If there is no way to document this, how can I document this within OpenAPI for humans only.</p>