|
1353 | 1353 | </t>
|
1354 | 1354 | <t>
|
1355 | 1355 | 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 |
1358 | 1358 | <xref target="RFC3987">absolute-IRI</xref> (without a fragment),
|
1359 | 1359 | or to a IRI with an empty fragment.
|
1360 | 1360 | </t>
|
|
1392 | 1392 | <xref target="RFC3986">RFC 3986 section 5.1.2</xref> regarding
|
1393 | 1393 | encapsulating entities, if an "$id" in a subschema is a relative
|
1394 | 1394 | 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>. |
1396 | 1399 | </t>
|
1397 | 1400 | <t>
|
1398 | 1401 | If no parent schema object explicitly identifies itself as a resource
|
|
1458 | 1461 | </t>
|
1459 | 1462 | </section>
|
1460 | 1463 |
|
1461 |
| - <section title="Duplicate schema identifiers"> |
| 1464 | + <section title="Duplicate schema identifiers" anchor="duplicate-iris"> |
1462 | 1465 | <t>
|
1463 | 1466 | A schema MAY (and likely will) have multiple IRIs, but there is no way
|
1464 | 1467 | for an IRI to identify more than one schema. When multiple schemas
|
|
0 commit comments