Skip to content

Commit 853c82b

Browse files
committed
Don't forbid cases already noted as errors
But do highlight that they are errors in the section where that is likely to be the most relevant.
1 parent 170ba3b commit 853c82b

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

jsonschema-core.xml

+7-4
Original file line numberDiff line numberDiff line change
@@ -1353,8 +1353,8 @@
13531353
</t>
13541354
<t>
13551355
If present, the value for this keyword MUST be a string, and MUST represent a
1356-
valid <xref target="RFC3987">IRI-reference</xref> with a non-empty non-fragment
1357-
component. This IRI-reference SHOULD be normalized, and MUST resolve to an
1356+
valid <xref target="RFC3987">IRI-reference</xref>. This IRI-reference
1357+
SHOULD be normalized, and MUST resolve to an
13581358
<xref target="RFC3987">absolute-IRI</xref> (without a fragment),
13591359
or to a IRI with an empty fragment.
13601360
</t>
@@ -1392,7 +1392,10 @@
13921392
<xref target="RFC3986">RFC 3986 section 5.1.2</xref> regarding
13931393
encapsulating entities, if an "$id" in a subschema is a relative
13941394
IRI-reference, the base IRI for resolving that reference is the IRI of
1395-
the parent schema resource.
1395+
the parent schema resource. Note that an "$id" consisting of an empty IRI or
1396+
of the empty fragment only will result in the embedded resource having
1397+
the same IRI as the encapsulating resource, which SHOULD be considered
1398+
an error per section <xref target="duplicate-iris" format="counter"></xref>.
13961399
</t>
13971400
<t>
13981401
If no parent schema object explicitly identifies itself as a resource
@@ -1458,7 +1461,7 @@
14581461
</t>
14591462
</section>
14601463

1461-
<section title="Duplicate schema identifiers">
1464+
<section title="Duplicate schema identifiers" anchor="duplicate-iris">
14621465
<t>
14631466
A schema MAY (and likely will) have multiple IRIs, but there is no way
14641467
for an IRI to identify more than one schema. When multiple schemas

0 commit comments

Comments
 (0)