Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit fa6cba4

Browse files
Merge pull request #862 from handrews/encoding
Improve contentEncoding RFC references
2 parents 4d82504 + 3948c47 commit fa6cba4

File tree

1 file changed

+17
-9
lines changed

1 file changed

+17
-9
lines changed

‎jsonschema-validation.xml‎

Lines changed: 17 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -979,19 +979,21 @@
979979
</t>
980980

981981
<t>
982-
Possible values for this property are listed in
983-
<xref target="RFC2045">RFC 2045, Sec 6.1</xref> and
984-
<xref target="RFC4648">RFC 4648</xref>. For "base64", which is defined
985-
in both RFCs, the definition in RFC 4648, which removes line length
986-
limitations, SHOULD be used, as various other specifications have
987-
mandated different lengths. Note that line lengths within a string
988-
can be constrained using the <xref target="pattern">"pattern"</xref> keyword.
982+
Possible values indicating base 16, 32, and 64 encodings with several
983+
variations are listed in <xref target="RFC4648">RFC 4648</xref>. Additionally,
984+
sections 6.7 and 6.8 of <xref target="RFC2045">RFC 2045</xref> provide
985+
encodings used in MIME. As "base64" is defined in both RFCs, the definition
986+
from RFC 4648 SHOULD be assumed unless the string is specifically intended
987+
for use in a MIME context. Note that all of these encodings result in
988+
strings consisting only of 7-bit ASCII characters. Therefore, this keyword
989+
has no meaning for strings containing characters outside of that range.
989990
</t>
990991

991992
<t>
992993
If this keyword is absent, but "contentMediaType" is present, this
993-
indicates that the media type could be encoded into UTF-8 like any
994-
other JSON string value, and does not require additional decoding.
994+
indicates that the encoding is the identity encoding, meaning that
995+
no transformation was needed in order to represent the content in
996+
a UTF-8 string.
995997
</t>
996998

997999
<t>
@@ -1426,6 +1428,12 @@
14261428
</t>
14271429
<t>
14281430
<list style="hanging">
1431+
<t hangText="draft-handrews-json-schema-validation-03">
1432+
<list style="symbols">
1433+
<t>Correct email format RFC reference to 5321 instead of 5322</t>
1434+
<t>Clarified the set and meaning of "contentEncoding" values</t>
1435+
</list>
1436+
</t>
14291437
<t hangText="draft-handrews-json-schema-validation-02">
14301438
<list style="symbols">
14311439
<t>Grouped keywords into formal vocabuarlies</t>

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /