|
105 | 105 | A <a>datatype IRI</a> is an <a>IRI</a> identifying a datatype that determines how the lexical form maps to a |
106 | 106 | <a data-cite="RDF11-CONCEPTS#dfn-literal-value">literal value</a>.</dd> |
107 | 107 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-default-graph" class="preserve">default graph</dfn></dt><dd> |
108 | | - The <a>default graph</a> is an <a>RDF graph</a> having no <a data-lt="graph name">name</a>, which MAY be empty.</dd> |
| 108 | + The <a>default graph</a> of a <a>dataset</a> is an <a>RDF graph</a> having no <a data-lt="graph name">name</a>, which MAY be empty.</dd> |
109 | 109 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-graph-name" class="preserve">graph name</dfn></dt><dd> |
110 | 110 | The <a>IRI</a> or <a>blank node</a> identifying a <a>named graph</a>.</dd> |
111 | 111 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-language-tagged-string" class="preserve">language-tagged string</dfn></dt><dd> |
|
119 | 119 | A set of documents, each containing a representation of a <a>linked data graph</a>.</dd> |
120 | 120 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-rdf-graph" data-lt="linked data graph|graph" class="preserve">RDF graph</dfn></dt><dd> |
121 | 121 | A labeled directed <a>graph</a>, |
122 | | - i.e., a set of <a>nodes</a> connected by directed-arcs.</dd> |
| 122 | + i.e., a set of <a>nodes</a> connected by directed-arcs. |
| 123 | + Also called <a>linked data graph</a>. |
| 124 | + </dd> |
123 | 125 | <dt><dfn data-cite="RDF-SCHEMA#ch_collectionvocab" data-lt="collection|RDF collection" class="preserve">list</dfn></dt><dd> |
124 | 126 | A <a>list</a> is an ordered sequence of <a>IRIs</a>, <a>blank nodes</a>, and <a>literals</a>.</dd> |
125 | 127 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-literal" data-lt="RDF literal" class="preserve">literal</dfn></dt><dd> |
126 | 128 | An <a>object</a> expressed as a value such as a <a>string</a> or <a>number</a>. |
127 | | - Implicitlly or explicitly includes a <a>datatype IRI</a> and, if the datatype is `xsd:string`, an optional <a>language tag</a>.</dd> |
| 129 | + Implicitlly or explicitly includes a <a>datatype IRI</a> and, if the datatype is `rdf:langString`, an optional <a>language tag</a>.</dd> |
128 | 130 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-named-graph" class="preserve">named graph</dfn></dt><dd> |
129 | 131 | A <a>named graph</a> |
130 | 132 | is a <a>linked data graph</a> that is identified by an <a>IRI</a> or <a>blank node</a>.</dd> |
131 | 133 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-node" class="preserve">node</dfn></dt><dd> |
132 | | - A <a>node</a> in an <a>RDF graph</a>, made up of the set of <a>subjects</a> and <a>objects</a> of <a>triples</a> in the <a>graph</a>.</dd> |
| 134 | + A <a>node</a> in an <a>RDF graph</a>, either the <a>subject</a> and <a>object</a> of at least one <a>triple</a>. |
| 135 | + Note that a <a>node</a> can play both roles (<a>subject</a> and <a>object</a>) in a <a>graph</a>, even in the same <a>triple</a>.</dd> |
133 | 136 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-object" class="preserve">object</dfn></dt><dd> |
134 | 137 | An <a>object</a> is a <a>node</a> in a <a>linked data graph</a> |
135 | 138 | with at least one incoming edge.</dd> |
|
142 | 145 | and may be removed in a future version of JSON-LD.</div> |
143 | 146 | Also, see <dfn data-cite="RDF11-CONCEPTS#dfn-predicate" class="preserve">predicate</dfn> in [[RDF11-CONCEPTS]].</dd> |
144 | 147 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-resource" class="preserve">resource</dfn></dt><dd> |
145 | | - A <a>resource</a> donoted by an <a>IRI</a> or <a>literal</a> representing something in the world ( the "universe of discourse").</dd> |
| 148 | + A <a>resource</a> denoted by an <a>IRI</a>, a <a>blank node</a> or <a>literal</a> representing something in the world (the "universe of discourse").</dd> |
146 | 149 | <dt><dfn data-cite="RDF11-CONCEPTS#dfn-rdf-triple" class="preserve">triple</dfn></dt><dd> |
147 | 150 | A component of an <a>RDF graph</a> including a <a>subject</a>, <a>predicate</a>, and <a>object</a>, which represents |
148 | 151 | a node-arc-node segment of an <a>RDF graph</a>.</dd> |
|
244 | 247 | an <a>array</a> of zero or more of the above possibilities. |
245 | 248 | </dd> |
246 | 249 | <dt><dfn data-cite="JSON-LD11#dfn-json-literal">JSON literal</dfn></dt><dd> |
247 | | - A <a>JSON literal</a> is a <a>literal</a> where the associated <a>IRI</a> is <code>rdf:JSON</code>. |
| 250 | + A <a>JSON literal</a> is a <a>literal</a> where the associated <a>datatype IRI</a> is <code>rdf:JSON</code>. |
248 | 251 | In the <a>value object</a> representation, the value of <code>@type</code> is <code>@json</code>. |
249 | 252 | JSON literals represent values which are valid JSON [[RFC8259]]. |
250 | 253 | See <dfn data-cite="JSON-LD11#dfn-json-datatype" data-cite="JSON-LD11#dfn-json-datatype" class="preserve">JSON datatype</dfn> in [[JSON-LD11]]. |
251 | 254 | </dd> |
252 | 255 | <dt><dfn data-cite="JSON-LD11#dfn-json-ld-document">JSON-LD document</dfn></dt><dd> |
253 | 256 | A <a>JSON-LD document</a> is a serialization of |
254 | | - a collection of <a>graphs</a> |
255 | | - and comprises exactly one <a>default graph</a> and zero or more <a>named graphs</a>.</dd> |
| 257 | + an <a>RDF dataset</a>.</dd> |
256 | 258 | <dt><dfn data-cite="JSON-LD11-API#dfn-json-ld-processor" data-lt="json-ld processor|Processors">JSON-LD Processor</dfn></dt><dd> |
257 | 259 | A <a>JSON-LD Processor</a> is a system which can perform the algorithms defined in [[JSON-LD11-API]].</dd> |
258 | 260 | <dt class="changed"><dfn data-cite="JSON-LD11-API#dfn-internal-representation" data-lt="internal representation">JSON-LD internal representation</dfn></dt><dd class="changed"> |
|
266 | 268 | <code>true</code> or <code>false</code>, |
267 | 269 | a <a>typed value</a>, |
268 | 270 | or a <a>language-tagged string</a>. |
| 271 | + It represents an <a>RDF literal</a>. |
269 | 272 | </dd> |
270 | 273 | <dt><dfn data-cite="JSON-LD11#dfn-keyword">keyword</dfn></dt><dd> |
271 | 274 | A <a>string</a> that is specific to JSON-LD, |
|
311 | 314 | when prepended to the suffix of the <a>compact IRI</a>, |
312 | 315 | results in an <a>absolute IRI</a>.</dd> |
313 | 316 | <dt><dfn data-cite="JSON-LD11#dfn-processing-mode">processing mode</dfn></dt><dd> |
314 | | - The processing mode defines how a JSON-LD document is processed. |
| 317 | + The processing mode defines how a <a>JSON-LD document</a> is processed. |
315 | 318 | By default, all documents are assumed to be conformant with <a data-cite="JSON-LD" data-no-xref="">JSON-LD 1.0</a> [[JSON-LD]]. |
316 | 319 | By defining a different version using the <code>@version</code> <a>entry</a> in a <a>context</a>, |
317 | 320 | or via explicit API option, |
318 | 321 | other processing modes can be accessed. |
319 | | - This specification defines extensions for the <code>json-ld-1.1</code> <a>processing mode</a>.</dd> |
| 322 | + This specification extends <a data-cite="JSON-LD" data-no-xref="">JSON-LD 1.0</a> |
| 323 | + via the <code>json-ld-1.1</code> <a>processing mode</a>.</dd> |
320 | 324 | <dt><dfn data-cite="JSON-LD11#dfn-set-object">set object</dfn></dt><dd> |
321 | 325 | A <a>set object</a> is a <a>map</a> that has an <code>@set</code> <a>entry</a>. |
322 | 326 | It may also have an <code>@index</code> key, but no other <a>entries</a>.</dd> |
|
0 commit comments