From d11f6e575a7e297c8fb1fa18bfcd1cc920e1d871 Mon Sep 17 00:00:00 2001
From: Roberto Polli
Since YAML is more expressive than JSON,
both in the available data types and in the document structure
- (see [[I-D.ietf-httpapi-yaml-mediatypes]]),
+ (see [[RFC9512]]),
this document identifies constraints on YAML
such that any YAML-LD document can be represented in JSON-LD.
Introduction
Comments
- See Interoperability considerations of [[I-D.ietf-httpapi-yaml-mediatypes]] + See Interoperability considerations of "+yaml" structured syntax suffix for more details.
@@ -1036,8 +1012,8 @@See Security considerations in JSON-LD 1.1. - Also, see the YAML media type registration.
+See Security considerations in JSON-LD 1.1
+ and +yaml
structured syntax suffix.
For general interoperability considerations on the serialization of
JSON documents in [[YAML]], see YAML
- and the Interoperability consideration of application/yaml
[[I-D.ietf-httpapi-yaml-mediatypes]].
+ and the Interoperability considerations of the +yaml
structured syntax suffix.
The YAML-LD format and the media type registration are not restricted to a specific @@ -1146,7 +1122,7 @@
For interoperability considerations on YAML streams, - see the relevant section in YAML Media Type. + see the relevant section in YAML Media Type.
+yaml
.application/yaml
application/yaml
application/yaml
application/yaml