Remove "Using an HTML document as a Context section. #212
Conversation
This reverts w3c/json-ld-api#66, which we can do because of #204.
|
For #172. |
| @@ -13443,10 +13302,6 @@ <h2>Changes since JSON-LD Community Group Final Report</h2> | |||
| <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 | |||
| expand to an <a>IRI</a> other than the expansion of the key itself.</li> | |||
| <li>Define different processor modes: <a>pure JSON Processor</a>, <a>event-based JSON processor</a>, and <a>full Processor</a>.</li> | |||
There was a problem hiding this comment.
Should we also remove these processor modes now?
There was a problem hiding this comment.
We might rename it, but the full Processor mode still defines the ability to extract JSON-LD from html. The PR just removes the need to use this for contexts.
There was a problem hiding this comment.
k. We at least have a naming collision here then.
Processing mode (changed via @version)
vs.
Processor Levels (pure, full, and event-based)
|
Is it intended that we still have a broken reference to the removed section (at the end of section 5)? |
No, of course not. This was something dangling between the two different PRs, apparently. Fixed in 06505e3. |
This reverts w3c/json-ld-api#66, which we can do because of #204.
Preview | Diff