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.

Sign up for GitHub

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

Jump to bottom

bcp56bis: use shorthand notation for [XML] #511

Merged
merged 1 commit into from Mar 16, 2018
Merged

bcp56bis: use shorthand notation for [XML] #511

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-httpbis-bcp56bis.md
View file
Open in desktop
Expand Up @@ -488,7 +488,7 @@ unless the definition of that header field explicitly allows it (e.g., with an e
## Defining Message Payloads {#payload}

There are many potential formats for payloads; for example, JSON {{?RFC8259}}, XML
{{?W3C.REC-xml-20081126}}, and CBOR {{?RFC7049}}. Best practices for their use are out of scope for
{{?XML=W3C.REC-xml-20081126}}, and CBOR {{?RFC7049}}. Best practices for their use are out of scope for
this document.

Applications SHOULD register distinct media types for each format they define; this makes it
Expand Down