From d308b1e171e7e1401f587172cd0369be4ce7289d Mon Sep 17 00:00:00 2001 From: Henry Andrews Date: Wed, 13 Jun 2018 16:52:52 -0700 Subject: [PATCH] Allow RFC 4648 content encodings RFC 4648 is a more modern standard for encodings, and addresses ambiguities and application-specific limits of the "base64" encoding from RFC 2045. It also adds several commonly used variations, such as "base64url", that are relevant to modern systems. RFC 2045 values are still allowed, although for "base64", RFC 4648 now takes precedence. --- jsonschema-validation.xml | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index d38ae783..6ae9131e 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -10,6 +10,7 @@ + @@ -330,7 +331,7 @@ -
+
The value of this keyword MUST be a string. This string SHOULD be a valid regular expression, according to the ECMA 262 regular expression @@ -759,8 +760,16 @@ If the instance value is a string, this property defines that the string SHOULD be interpreted as binary data and decoded using the encoding named by this property. - RFC 2045, Sec 6.1 lists the possible - values for this property. + + + + Possible values for this property are listed in + RFC 2045, Sec 6.1 and + RFC 4548. 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. @@ -991,6 +1000,7 @@ &RFC3986; &RFC3987; &RFC4291; + &RFC4648; &RFC5322; &RFC5890; &RFC5891;