|
320 | 320 | when prepended to the suffix of the <a>compact IRI</a>,
|
321 | 321 | results in an <a>absolute IRI</a>.</dd>
|
322 | 322 | <dt><dfn data-cite="JSON-LD11#dfn-processing-mode">processing mode</dfn></dt><dd>
|
323 |
| - The processing mode defines how a <a>JSON-LD document</a> is processed. |
324 |
| - By default, all documents are assumed to be conformant with <a data-cite="JSON-LD10" data-no-xref="">JSON-LD 1.0</a> [[JSON-LD10]]. |
| 323 | + The <a>processing mode</a> defines how a <a>JSON-LD document</a> is processed. |
| 324 | + By default, all documents are assumed to be conformant with this specification. |
325 | 325 | By defining a different version using the <code>@version</code> <a>entry</a> in a <a>context</a>,
|
326 |
| - or via explicit API option, |
327 |
| - other processing modes can be accessed. |
| 326 | + publishers can ensure that processors conformant with <a data-cite="JSON-LD10" data-no-xref="">JSON-LD 1.0</a> [[JSON-LD10]] |
| 327 | + will not accidently process JSON-LD 1.1 documents, possibly creating a different output. |
| 328 | + The API provides an option for setting the <a>processing mode</a> to `json-ld-1.0`, |
| 329 | + which will prevent JSON-LD 1.1 features from being activated, |
| 330 | + or error if <code>@version</code> <a>entry</a> in a <a>context</a> is explicitly set to `1.1`. |
328 | 331 | This specification extends <a data-cite="JSON-LD10" data-no-xref="">JSON-LD 1.0</a>
|
329 |
| - via the <code>json-ld-1.1</code> <a>processing mode</a>.</dd> |
| 332 | + via the `json-ld-1.1` <a>processing mode</a>.</dd> |
330 | 333 | <dt><dfn data-cite="JSON-LD11#dfn-set-object">set object</dfn></dt><dd>
|
331 | 334 | A <a>set object</a> is a <a>map</a> that has an <code>@set</code> <a>entry</a>.
|
332 | 335 | It may also have an <code>@index</code> key, but no other <a>entries</a>.</dd>
|
|
0 commit comments