@@ -574,18 +574,17 @@ <h1>Conformance</h1>
574
574
< code class ="idlMemberName "> < a href ="#widl-JsonLdOptions-processingMode "> processingMode</ a > </ code >
575
575
option of < a > JsonLdOptions</ a > ).</ p >
576
576
577
+ < p > JSON-LD Implementations or Processors MUST NOT attempt to correct malformed
578
+ < tref title ="IRI "> IRIs</ tref > or language tags; however, they MAY issue validation
579
+ warnings. IRIs are not modified other than converted between
580
+ < tref title ="relative IRI "> relative</ tref > and
581
+ < tref title ="absolute IRI "> absolute IRIs</ tref > .</ p >
582
+
577
583
< p > The algorithms in this specification are generally written with more concern for clarity than
578
584
efficiency. Thus, JSON-LD Implementations and Processors may implement the algorithms
579
585
given in this specification in any way desired, so long as the end result is indistinguishable
580
586
from the result that would be obtained by the specification's algorithms.</ p >
581
587
582
- < p > This specification does not define how JSON-LD Implementations or Processors handle
583
- non-conforming input documents. This implies that JSON-LD Implementations or Processors
584
- MUST NOT attempt to correct malformed < tref title ="IRI "> IRIs</ tref > or language tags;
585
- however, they MAY issue validation warnings. IRIs are not modified other than converted
586
- between < tref title ="relative IRI "> relative</ tref > and
587
- < tref title ="absolute IRI "> absolute IRIs</ tref > .</ p >
588
-
589
588
< p class ="note "> Implementers can partially check their level of conformance to
590
589
this specification by successfully passing the test cases of the JSON-LD test
591
590
suite [[JSON-LD-TESTS]]. Note, however, that passing all the tests in the test
0 commit comments