Skip to content

Commit bd20d6d

Browse files
committed
Clarify streaming binary/string usage.
Tighten up the wording a bit to ensure the scope of this technique is immediately clear.
1 parent d5916fd commit bd20d6d

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

src/oas.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1665,8 +1665,8 @@ This poses a challenge for streamed media, particularly streams where the client
16651665

16661666
###### Binary Streams
16671667

1668-
The `maxLength` keyword MAY be used to set an expected upper bound on the length of a streaming payload.
1669-
The keyword can be applied to either string data, including encoded binary data, or to unencoded binary data. For unencoded binary, the length is the number of octets.
1668+
The `maxLength` keyword MAY be used to set an expected upper bound on the length of a streaming payload that consists of either string data, including encoded binary data, or to unencoded binary data.
1669+
For unencoded binary, the length is the number of octets.
16701670
For this use case, `maxLength` MAY be implemented outside of regular JSON Schema evaluation as JSON Schema does not directly apply to binary data, and an encoded binary stream may be impractical to store in memory in its entirety.
16711671

16721672
###### Streaming Sequential Media Types

0 commit comments

Comments
 (0)