From d11f6e575a7e297c8fb1fa18bfcd1cc920e1d871 Mon Sep 17 00:00:00 2001 From: Roberto Polli Date: Thu, 14 Nov 2024 17:08:06 +0100 Subject: [PATCH] Fix: #156. Update media type registration information. (#157) * Fix: #156. Update media type registration information. * RFC9512 is in specref. YAML 1.2.2 is not * YAML 1.2.2 is in specref too ;) * Change contact information to WG.. --------- Co-authored-by: Gregg Kellogg --- spec/index.html | 48 ++++++++++++++---------------------------------- 1 file changed, 14 insertions(+), 34 deletions(-) diff --git a/spec/index.html b/spec/index.html index e2564b1..adbc9e9 100644 --- a/spec/index.html +++ b/spec/index.html @@ -32,19 +32,6 @@ }], localBiblio: { - "I-D.ietf-httpapi-yaml-mediatypes": { - title: "YAML Media Type", - href: "https://www.ietf.org/archive/id/draft-ietf-httpapi-yaml-mediatypes-03.html", - publisher: "IETF", - date: "2022-08-05", - status: "WG Document", - authors: [ - "Roberto Polli", - "Erik Wilde", - "Eemeli Aro" - ] - }, - "json-ld-bp": { title: "JSON-LD Best Practices", href: "https://w3c.github.io/json-ld-bp/", @@ -61,17 +48,6 @@ "Philippe Le Hegaret", ], }, - - "YAML": { - title: "YAML Ain’t Markup Language (YAML™) version 1.2.2", - href: "https://yaml.org/spec/1.2.2/", - date: "2021-10-01", - authors: [ - "Oren Ben-Kiki", - "Clark Evans", - "Ingy döt Net" - ] - } }, // Cross-reference definitions @@ -355,7 +331,7 @@

Introduction

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.

@@ -902,7 +878,7 @@

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 @@

Mapping Key Types

Security Considerations

-

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.

@@ -1046,7 +1022,7 @@

Interoperability Considerations

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 @@

Streams

For interoperability considerations on YAML streams, - see the relevant section in YAML Media Type. + see the relevant section in YAML Media Type.

@@ -1212,7 +1188,7 @@

application/ld+yaml

Encoding considerations:
-
See YAML media type.
+
Same as +yaml.
Security considerations:
See .
Interoperability considerations:
@@ -1226,8 +1202,10 @@

application/ld+yaml

Additional information:
+
Deprecated alias names for this type:
+
N/A
Magic number(s):
-
See application/yaml
+
Same as application/yaml
File extension(s):
    @@ -1236,11 +1214,13 @@

    application/ld+yaml

Macintosh file type code(s):
-
TEXT
+
Same as application/yaml
+
Windows Clipboard Name:
+
Same as application/yaml
Person & email address to contact for further information:
-
Philippe Le Hégaret <plh@w3.org>
+
W3C JSON-LD Working Group <public-json-ld-wg@w3.org>
Intended usage:
Common
Restrictions on usage: