@@ -678,52 +678,6 @@ <h2>Syntax Tokens and Keywords</h2>
678
678
<p>These are used within this document as part of a <a>compact IRI</a>
679
679
as a shorthand for the resulting <a>absolute IRI</a>, such as <code>dcterms:title</code>
680
680
used to represent <code>http://purl.org/dc/terms/title</code>.</p>
681
-
682
- <section>
683
- <h2>Processor Levels</h2>
684
-
685
- <!--
686
- **************** IMPORTANT WARNING ****************
687
- This section is duplicated (with a few adaptations)
688
- in other JSON-LD specifications. Since these
689
- definitions are normative, it is important to
690
- reflect any change in the other documents.
691
- ***************************************************
692
- -->
693
-
694
- <p>JSON-LD mostly uses the JSON syntax [[RFC8259]] along with
695
- various micro-syntaxes based on XML Schema datatypes [[XMLSCHEMA11-2]].
696
- However, it has become increasingly common to include JSON within
697
- a <a data-cite="HTML/scripting.html#the-script-element">script element</a>
698
- within an HTML document [[HTML]],
699
- as described in <a href="#embedding-json-ld-in-html-documents" class="sectionRef"></a>.
700
- As not all processors operate in an environment which can include HTML,
701
- this specification describes various categories of JSON-LD processors.</p>
702
-
703
- <p>A <dfn>pure JSON Processor</dfn> only requires the use of a
704
- JSON processor and is restricted to processing documents retrieved
705
- with a JSON content type (e.g., <code>application/ld+json</code> or other JSON type).</p>
706
-
707
- <p>A <dfn>full Processor</dfn> is capable of processing JSON-LD embedded in HTML,
708
- in addition to the capabilities of a <a>pure JSON Processor</a>.</p>
709
-
710
- <section class="informative">
711
- <h3>Additional Processor Levels</h3>
712
-
713
- <p>In addition to the normatively defined processor levels, an additional processor
714
- level is defined for reference.</p>
715
-
716
- <p>A <dfn>event-based JSON Processor</dfn> processes a stream of characters
717
- expecting an event after each syntactic element is encountered.
718
- Such processors are sensitive to the order of the members of <a>JSON objects</a>,
719
- which can have a performance impact if the members of <a>JSON objects</a> are encountered in an unexpected order.
720
- An <a>event-based JSON Processor</a> may process JSON-LD embedded in HTML.</p>
721
-
722
- <p class="note">An <a>event-based JSON Processor</a>
723
- may be sensitive to processing certain keywords in order, including
724
- <code>@context</code>, <code>@id</code>, and <code>@type</code>.</p>
725
- </section>
726
- </section>
727
681
</section>
728
682
729
683
<section class="informative">
@@ -9807,7 +9761,7 @@ <h3>Graph Containers</h3>
9807
9761
of JSON-LD (see <a href="#forms-of-json-ld" class="sectionRef"></a>).
9808
9762
This includes a general mechanism for loading remote documents,
9809
9763
including referenced JSON-LD documents and remote contexts,
9810
- and extracting embedded JSON-LD from other formats such as [[HTML]].
9764
+ and potentially extracting embedded JSON-LD from other formats such as [[HTML]].
9811
9765
This is more fully described in
9812
9766
<a data-cite="JSON-LD11-API#remote-document-and-context-retrieval">Remote Document and Context Retrieval</a>
9813
9767
in [[JSON-LD11-API]].</p>
@@ -11007,7 +10961,10 @@ <h3>Graph Containers</h3>
11007
10961
11008
10962
<section class="changed"><h2>Embedding JSON-LD in HTML Documents</h2>
11009
10963
11010
- <p class="note">This section describes features available to a <a>full Processor</a>.</p>
10964
+ <p class="note">This section describes features available
10965
+ with a <a>documentLoader</a> supporting <a data-cite="JSON-LD11-API#html-script-extraction">HTML script extraction</a>.
10966
+ See <a data-cite="JSON-LD11-API#remote-document-and-context-retrieval">Remote Document and Context Retrieval</a>
10967
+ for more information.</p>
11011
10968
11012
10969
<p>
11013
10970
JSON-LD content can be easily embedded in HTML [[HTML]] by placing
@@ -12734,7 +12691,7 @@ <h3>Privacy Considerations</h3>
12734
12691
(see [[?fingerprinting-guidance]]), and
12735
12692
and provide an opportunity for a man-in-the-middle attack.
12736
12693
To protect against this, publishers should consider caching remote contexts for future use,
12737
- or use the <a data-cite="JSON-LD11-API#dom-jsonldoptions-documentloader" >documentLoader</a>
12694
+ or use the <a>documentLoader</a>
12738
12695
to maintain a local version of such contexts.</p>
12739
12696
</section>
12740
12697
@@ -13374,7 +13331,6 @@ <h2>Changes since JSON-LD Community Group Final Report</h2>
13374
13331
Define the <code>rdf:JSON</code> datatype.</li>
13375
13332
<li><a>Term definitions</a> with keys which are of the form of a <a>compact IRI</a> or <a>absolute IRI</a> MUST NOT
13376
13333
expand to an <a>IRI</a> other than the expansion of the key itself.</li>
13377
- <li>Define different processor modes: <a>pure JSON Processor</a>, <a>event-based JSON processor</a>, and <a>full Processor</a>.</li>
13378
13334
<li>A <a>frame</a> may also be located within an HTML document, identified
13379
13335
using type <code>application/ld+json;profile=http://www.w3.org/ns/json-ld#frame</code>.</li>
13380
13336
<li>Term definitions can now be <a href="#protected-term-definitions">protected</a>,
0 commit comments