@@ -243,7 +243,7 @@ <h2>Introduction</h2>
243
243
< p >
244
244
Since YAML is more expressive than JSON,
245
245
both in the available data types and in the document structure
246
- (see [[I-D.ietf-yaml-mediatypes]]),
246
+ (see [[I-D.ietf-httpapi- yaml-mediatypes]]),
247
247
this document identifies constraints on YAML documents
248
248
such that they can be used to represent JSON-LD documents.
249
249
</ p >
@@ -308,7 +308,7 @@ <h2>Basic Concepts</h2>
308
308
JSON encoding is UTF-8.
309
309
</ p >
310
310
311
- < p > Example: the JSON-LD document below
311
+ < p data-format =" markdown >Example: the JSON-LD document below
312
312
313
313
```
314
314
{
@@ -345,7 +345,7 @@ <h2>Basic Concepts</h2>
345
345
</ p >
346
346
</ section >
347
347
< section id ="specifications " class ="normative ">
348
- < h2 > Specifications </ h2 >
348
+ < h2 > Core Requirements </ h2 >
349
349
350
350
< p >
351
351
A YAML-LD document is a [[YAML]] document that can be interpreted as linked data.
@@ -373,7 +373,7 @@ <h2>Specifications</h2>
373
373
When interpreting the document as JSON-LD,
374
374
alias nodes MUST be resolved by value to their target nodes.
375
375
</ p >
376
- < p >
376
+ < p data-format =" markdown >
377
377
Example: The following YAML-LD document
378
378
contains alias nodes for the { "@id ": "country:ITA"} object;
379
379
0 commit comments