From 05fe4a384958c727790ab373bd86c5e4e11538b1 Mon Sep 17 00:00:00 2001 From: Henry Andrews Date: Thu, 20 Feb 2020 23:11:49 -0800 Subject: [PATCH 1/3] Improve contentEncoding RFC references The reference to RFC 2045 was ambiguous and misleading. Emphasize RFC 4648 more, and clarify what from 2045 is relevant and when. --- jsonschema-validation.xml | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index 58d334fc..7c5c3b4b 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -979,19 +979,19 @@ - Possible values for this property are listed in - RFC 2045, Sec 6.1 and - RFC 4648. For "base64", which is defined - in both RFCs, the definition in RFC 4648, which removes line length - limitations, SHOULD be used, as various other specifications have - mandated different lengths. Note that line lengths within a string - can be constrained using the "pattern" keyword. + Possible values indicating base 16, 32, and 64 encodings with several + variations are listed in RFC 4648. Additionally, + sections 6.7 and 6.8 of RFC 2045 provide + encodings used in MIME. As "base64" is defined in both RFCs, the definition + from RFC 4648 SHOULD be assumed unless the string is specifically intended + for use in a MIME context. If this keyword is absent, but "contentMediaType" is present, this - indicates that the media type could be encoded into UTF-8 like any - other JSON string value, and does not require additional decoding. + indicates that the encoding is the identity encoding, meaning that + no transformation was needed in order to represent the content in + a UTF-8 string. From 6fa4289049b90e3c7800917193b70b5bb5344bba Mon Sep 17 00:00:00 2001 From: Henry Andrews Date: Thu, 19 Mar 2020 16:13:52 -0700 Subject: [PATCH 2/3] Review feedback on contentEncoding, add change log --- jsonschema-validation.xml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index 7c5c3b4b..013fd37a 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -984,7 +984,9 @@ sections 6.7 and 6.8 of RFC 2045 provide encodings used in MIME. As "base64" is defined in both RFCs, the definition from RFC 4648 SHOULD be assumed unless the string is specifically intended - for use in a MIME context. + for use in a MIME context. Note that all of these encodings result in + strings consisting only of 7-bit ASCII characters. Therefore, this keyword + has no meaning for strings containing characters outside of that range. @@ -1426,6 +1428,11 @@ + + + Clarified the set and meaning of "contentEncoding" values + + Grouped keywords into formal vocabuarlies From 3948c470cd0457b04b63c8e95a14abc3225565f5 Mon Sep 17 00:00:00 2001 From: Henry Andrews Date: Thu, 19 Mar 2020 16:16:13 -0700 Subject: [PATCH 3/3] Change log entry for email format fix --- jsonschema-validation.xml | 1 + 1 file changed, 1 insertion(+) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index 013fd37a..c1b995e5 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -1430,6 +1430,7 @@ + Correct email format RFC reference to 5321 instead of 5322 Clarified the set and meaning of "contentEncoding" values