@@ -436,30 +436,6 @@ <h2>Design Goals and Rationale</h2>
436
436
</dl>
437
437
</section>
438
438
439
- <section class="informative">
440
- <h2>Processor Levels</h2>
441
- <p>JSON-LD mostly uses the JSON syntax [[RFC8259]] along with
442
- various micro-syntaxes based on XML Schema datatypes [[XMLSCHEMA11-2]].
443
- However, it has become increasingly common to include JSON within
444
- a <a data-cite="HTML/semantics-scripting.html#the-script-element">script element</a>
445
- within an HTML document [[HTML]],
446
- as described in <a href="#embedding-json-ld-in-html-documents" class="sectionRef"></a>.
447
- As not all processors operate in an environment which can include HTML,
448
- this specification describes various categories of JSON-LD processors.</p>
449
-
450
- <p>A <dfn>pure JSON Processor</dfn> only requires the use of a
451
- JSON processor and is restricted to processing documents retrieved
452
- with a JSON content type (e.g., <code>application/ld+json</code> or other JSON type).</p>
453
-
454
- <p>A <dfn>event-based JSON Processor</dfn> processes a stream of characters
455
- expecting an event after each syntactic element is encountered.
456
- Such processors are sensitive to the order of the members of <a>JSON objects</a>,
457
- which can have a performance impact if the members of <a>JSON objects</a> are encountered in an unexpected order.</p>
458
-
459
- <p>A <dfn>full Processor</dfn> is capable of JSON-LD embedded in HTML,
460
- in addition to the capabilities of a <a>pure JSON Processor</a>.</p>
461
- </section>
462
-
463
439
<section class="informative">
464
440
<h2>Data Model Overview</h2>
465
441
@@ -668,6 +644,37 @@ <h2>Syntax Tokens and Keywords</h2>
668
644
<p>These are used within this document as part of a <a>compact IRI</a>
669
645
as a shorthand for the resulting <a>absolute IRI</a>, such as <code>dcterms:title</code>
670
646
used to represent <code>http://purl.org/dc/terms/title</code>.</p>
647
+
648
+ <section>
649
+ <h2>Processor Levels</h2>
650
+ <p>JSON-LD mostly uses the JSON syntax [[RFC8259]] along with
651
+ various micro-syntaxes based on XML Schema datatypes [[XMLSCHEMA11-2]].
652
+ However, it has become increasingly common to include JSON within
653
+ a <a data-cite="HTML/semantics-scripting.html#the-script-element">script element</a>
654
+ within an HTML document [[HTML]],
655
+ as described in <a href="#embedding-json-ld-in-html-documents" class="sectionRef"></a>.
656
+ As not all processors operate in an environment which can include HTML,
657
+ this specification describes various categories of JSON-LD processors.</p>
658
+
659
+ <p>A <dfn>pure JSON Processor</dfn> only requires the use of a
660
+ JSON processor and is restricted to processing documents retrieved
661
+ with a JSON content type (e.g., <code>application/ld+json</code> or other JSON type).</p>
662
+
663
+ <p>A <dfn>full Processor</dfn> is capable of processing JSON-LD embedded in HTML,
664
+ in addition to the capabilities of a <a>pure JSON Processor</a>.</p>
665
+
666
+ <section class="informative">
667
+ <h3>Additional Processor Levels</h3>
668
+
669
+ <p>In addition to the normatively defined processor levels, an additional processor
670
+ level is defined for reference.</p>
671
+
672
+ <p>A <dfn>event-based JSON Processor</dfn> processes a stream of characters
673
+ expecting an event after each syntactic element is encountered.
674
+ Such processors are sensitive to the order of the members of <a>JSON objects</a>,
675
+ which can have a performance impact if the members of <a>JSON objects</a> are encountered in an unexpected order.</p>
676
+ </section>
677
+ </section>
671
678
</section>
672
679
673
680
<section class="informative">
0 commit comments