Skip to content

Commit 73ae7dd

Browse files
committed
Clarify multipart preamble/epilogue
1 parent 7e94e16 commit 73ae7dd

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

src/oas.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -107,6 +107,7 @@ Some examples of sequential media types (including some that are not IANA-regist
107107
In the first three above, the repeating structure is any [JSON value](https://tools.ietf.org/html/rfc8259#section-3).
108108
The fourth repeats `application/geo+json`-structured values, while `text/event-stream` repeats a custom text format related to Server-Sent Events.
109109
The final media type listed above, `multipart/mixed`, provides an ordered list of documents of any media type, and is sometimes streamed.
110+
Note that while `multipart` formats technically allow a preamble and an epilogue, the RFC directs that they are to be ignored, making the effectively comments, and this specification does not model them.
110111

111112
Implementations MUST support mapping sequential media types into the JSON Schema data model by treating them as if the values were in an array in the same order.
112113

0 commit comments

Comments
 (0)