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 af23dbd

Browse files
Merge pull request #965 from Relequestual/fixes/821
Reference ECMAScript 11.0 specifically (#821)
2 parents 75085c2 + 9186315 commit af23dbd

File tree

2 files changed

+20
-13
lines changed

2 files changed

+20
-13
lines changed

‎jsonschema-core.xml‎

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -545,7 +545,12 @@
545545
Keywords MAY use regular expressions to express constraints, or constrain
546546
the instance value to be a regular expression.
547547
These regular expressions SHOULD be valid according to the regular expression
548-
dialect described in <xref target="ecma262">ECMA 262, section 15.10.1</xref>.
548+
dialect described in <xref target="ecma262">ECMA-262, section 21.2.1</xref>.
549+
</t>
550+
<t>
551+
Regular expressions SHOULD be built with the "u" flag (or equivilent) to provide
552+
Unicode support, or processed in such a way which provides which provides Unicode
553+
as defined by ECMA-262.
549554
</t>
550555
<t>
551556
Furthermore, given the high disparity in regular expression constructs support,
@@ -2480,7 +2485,7 @@
24802485
<t>
24812486
The value of "patternProperties" MUST be an object. Each property name
24822487
of this object SHOULD be a valid regular expression, according to the
2483-
ECMA262 regular expression dialect. Each property value of this object
2488+
ECMA-262 regular expression dialect. Each property value of this object
24842489
MUST be a valid JSON Schema.
24852490
</t>
24862491
<t>
@@ -3291,11 +3296,11 @@ https://example.com/schemas/common#/$defs/count/minimum
32913296
&RFC8259;
32923297
&ldp;
32933298
<reference anchor="ecma262"
3294-
target="http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf">
3299+
target="https://www.ecma-international.org/ecma-262/11.0">
32953300
<front>
3296-
<title>ECMA262 specification</title>
3301+
<title>ECMA-262, 11th edition specification</title>
32973302
<author/>
3298-
<date/>
3303+
<datemonth="June"year="2020"/>
32993304
</front>
33003305
</reference>
33013306
</references>
@@ -3924,7 +3929,9 @@ https://example.com/schemas/common#/$defs/count/minimum
39243929
<t>Rename $recursive* to $dynamic*</t>
39253930
<t>$dynamicAnchor defines a fragment like $anchor</t>
39263931
<t>$dynamic* (previously $recursive) no longer use runtime base URI determination</t>
3932+
<t>Reference ecma262 11th edition for regular expression support</t>
39273933
<t>Define Compound Schema Documents (bundle) and processing</t>
3934+
<t>Reference ECMA-262, 11th edition for regular expression support</t>
39283935
<t></t>
39293936
<t></t>
39303937
<t></t>

‎jsonschema-validation.xml‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -352,7 +352,7 @@
352352
<section title="pattern" anchor="pattern">
353353
<t>
354354
The value of this keyword MUST be a string. This string SHOULD be a
355-
valid regular expression, according to the ECMA262 regular expression
355+
valid regular expression, according to the ECMA-262 regular expression
356356
dialect.
357357
</t>
358358
<t>
@@ -898,12 +898,12 @@
898898
</t>
899899
<t>
900900
A regular expression, which SHOULD be valid according to the
901-
<xref target="ecma262">ECMA262</xref> regular expression dialect.
901+
<xref target="ecma262">ECMA-262</xref> regular expression dialect.
902902
</t>
903903
<t>
904904
Implementations that validate formats MUST accept at least the subset of
905-
ECMA262 defined in the <xref target="regexInterop">Regular Expressions</xref>
906-
section of this specification, and SHOULD accept all valid ECMA262 expressions.
905+
ECMA-262 defined in the <xref target="regexInterop">Regular Expressions</xref>
906+
section of this specification, and SHOULD accept all valid ECMA-262 expressions.
907907
</t>
908908
</section>
909909
</section>
@@ -1316,11 +1316,11 @@
13161316
&RFC6901;
13171317
&RFC8259;
13181318
<reference anchor="ecma262"
1319-
target="http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-262.pdf">
1319+
target="https://www.ecma-international.org/ecma-262/11.0">
13201320
<front>
1321-
<title>ECMA262 specification</title>
1321+
<title>ECMA-262, 11th edition specification</title>
13221322
<author/>
1323-
<date/>
1323+
<datemonth="June"year="2020"/>
13241324
</front>
13251325
</reference>
13261326
<reference anchor="relative-json-pointer">
@@ -1434,7 +1434,7 @@
14341434
<list style="symbols">
14351435
<t>Correct email format RFC reference to 5321 instead of 5322</t>
14361436
<t>Clarified the set and meaning of "contentEncoding" values</t>
1437-
<t></t>
1437+
<t>Reference ECMA-262, 11th edition for regular expression support</t>
14381438
<t></t>
14391439
<t></t>
14401440
<t></t>

0 commit comments

Comments
(0)

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