From 1e7cd49d0112859f73e0dc5d7ff1eb5abfa03132 Mon Sep 17 00:00:00 2001 From: Relequestual Date: Mon, 10 Aug 2020 23:37:12 +0100 Subject: [PATCH 1/7] Fixes 821 Reference specific version of emca262. --- jsonschema-core.xml | 6 +++--- jsonschema-validation.xml | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index 18ced482..b08cb2a6 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -3221,11 +3221,11 @@ https://example.com/schemas/common#/$defs/count/minimum &RFC8259; &ldp; + target="https://www.ecma-international.org/ecma-262/5.1"> - ECMA 262 specification + ECMA-262 5.1 edition specification - + diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index a8026d89..5eb20257 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -1316,11 +1316,11 @@ &RFC6901; &RFC8259; + target="https://www.ecma-international.org/ecma-262/5.1"> - ECMA 262 specification + ECMA-262 5.1 edition specification - + From 7e31d170059c1784113d4e72cc8b7f7b397eaa24 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Wed, 30 Sep 2020 23:15:37 +0100 Subject: [PATCH 2/7] Reference ECMAScript 10.0 specifically for the purposes of optional regex support --- jsonschema-core.xml | 8 ++++---- jsonschema-validation.xml | 8 ++++---- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index b08cb2a6..04868e5f 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -3221,11 +3221,11 @@ https://example.com/schemas/common#/$defs/count/minimum &RFC8259; &ldp; + target="https://www.ecma-international.org/ecma-262/11.0"> - ECMA-262 5.1 edition specification + ECMA-262 11.0 edition specification - + @@ -3854,7 +3854,7 @@ https://example.com/schemas/common#/$defs/count/minimum Rename $recursive* to $dynamic* $dynamicAnchor defines a fragment like $anchor $dynamic* (previously $recursive) no longer use runtime base URI determination - + Reference ecma262 11th edition for regular expression support diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index 5eb20257..c3b396bc 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -1316,11 +1316,11 @@ &RFC6901; &RFC8259; + target="https://www.ecma-international.org/ecma-262/11.0"> - ECMA-262 5.1 edition specification + ECMA-262 11.0 edition specification - + @@ -1434,7 +1434,7 @@ Correct email format RFC reference to 5321 instead of 5322 Clarified the set and meaning of "contentEncoding" values - + Reference ecma262 11th edition for regular expression support From d74ddb49e4177f6221f2275a0871bf415fc78b38 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Wed, 30 Sep 2020 23:22:59 +0100 Subject: [PATCH 3/7] Update ecma262 section numbers --- jsonschema-core.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index 04868e5f..d1a4bde6 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -545,7 +545,7 @@ Keywords MAY use regular expressions to express constraints, or constrain the instance value to be a regular expression. These regular expressions SHOULD be valid according to the regular expression - dialect described in ECMA 262, section 15.10.1. + dialect described in ECMA 262, section 21.2.1. Furthermore, given the high disparity in regular expression constructs support, From 9b96d6aa3abcbd7425b42e7440a5e8e0c8adf659 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Wed, 14 Oct 2020 11:32:51 +0100 Subject: [PATCH 4/7] Add note regarding regular expression unicode flag requirement --- jsonschema-core.xml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index d1a4bde6..0370e5dc 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -547,6 +547,11 @@ These regular expressions SHOULD be valid according to the regular expression dialect described in ECMA 262, section 21.2.1. + + Regular expressions SHOULD be built with the "u" flag (or equivilent) to provide + Unicode support, or processed in such a way which provides which provides Unicode + as defined by ECMA 262. + Furthermore, given the high disparity in regular expression constructs support, schema authors SHOULD limit themselves to the following regular expression From bb9cba645c49c043da7a7e245382d7078d40d304 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Mon, 26 Oct 2020 21:18:10 +0000 Subject: [PATCH 5/7] Fix duplicated phrase --- jsonschema-core.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index 0370e5dc..c1aa5a20 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -549,7 +549,7 @@ Regular expressions SHOULD be built with the "u" flag (or equivilent) to provide - Unicode support, or processed in such a way which provides which provides Unicode + Unicode support, or processed in such a way which provides Unicode support, as defined by ECMA 262. From 0143f212a96d33007f65b5e46796c38f11f21ff8 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Wed, 30 Sep 2020 23:15:37 +0100 Subject: [PATCH 6/7] Reference ECMAScript 11th Edition specifically for the purposes of optional regex support --- jsonschema-core.xml | 1 + 1 file changed, 1 insertion(+) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index 63212fce..d6735a64 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -3931,6 +3931,7 @@ https://example.com/schemas/common#/$defs/count/minimum $dynamic* (previously $recursive) no longer use runtime base URI determination Reference ecma262 11th edition for regular expression support Define Compound Schema Documents (bundle) and processing + Reference ecma262 11th edition for regular expression support From 918631544ae34593ab0d6c76886adbee343114e1 Mon Sep 17 00:00:00 2001 From: Ben Hutton Date: Tue, 3 Nov 2020 22:15:21 +0000 Subject: [PATCH 7/7] Fix how ECMA-262 is used and referenced --- jsonschema-core.xml | 14 +++++++------- jsonschema-validation.xml | 14 +++++++------- 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/jsonschema-core.xml b/jsonschema-core.xml index d6735a64..3d7c6e31 100644 --- a/jsonschema-core.xml +++ b/jsonschema-core.xml @@ -545,12 +545,12 @@ Keywords MAY use regular expressions to express constraints, or constrain the instance value to be a regular expression. These regular expressions SHOULD be valid according to the regular expression - dialect described in ECMA 262, section 21.2.1. + dialect described in ECMA-262, section 21.2.1. Regular expressions SHOULD be built with the "u" flag (or equivilent) to provide - Unicode support, or processed in such a way which provides Unicode support, - as defined by ECMA 262. + Unicode support, or processed in such a way which provides which provides Unicode + as defined by ECMA-262. Furthermore, given the high disparity in regular expression constructs support, @@ -2485,7 +2485,7 @@ The value of "patternProperties" MUST be an object. Each property name of this object SHOULD be a valid regular expression, according to the - ECMA 262 regular expression dialect. Each property value of this object + ECMA-262 regular expression dialect. Each property value of this object MUST be a valid JSON Schema. @@ -3298,9 +3298,9 @@ https://example.com/schemas/common#/$defs/count/minimum - ECMA-262 11.0 edition specification + ECMA-262, 11th edition specification - + @@ -3931,7 +3931,7 @@ https://example.com/schemas/common#/$defs/count/minimum $dynamic* (previously $recursive) no longer use runtime base URI determination Reference ecma262 11th edition for regular expression support Define Compound Schema Documents (bundle) and processing - Reference ecma262 11th edition for regular expression support + Reference ECMA-262, 11th edition for regular expression support diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml index c3b396bc..3f33f376 100644 --- a/jsonschema-validation.xml +++ b/jsonschema-validation.xml @@ -352,7 +352,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 + valid regular expression, according to the ECMA-262 regular expression dialect. @@ -898,12 +898,12 @@ A regular expression, which SHOULD be valid according to the - ECMA 262 regular expression dialect. + ECMA-262 regular expression dialect. Implementations that validate formats MUST accept at least the subset of - ECMA 262 defined in the Regular Expressions - section of this specification, and SHOULD accept all valid ECMA 262 expressions. + ECMA-262 defined in the Regular Expressions + section of this specification, and SHOULD accept all valid ECMA-262 expressions.
@@ -1318,9 +1318,9 @@ - ECMA-262 11.0 edition specification + ECMA-262, 11th edition specification - + @@ -1434,7 +1434,7 @@ Correct email format RFC reference to 5321 instead of 5322 Clarified the set and meaning of "contentEncoding" values - Reference ecma262 11th edition for regular expression support + Reference ECMA-262, 11th edition for regular expression support