Fix: #156. Update media type registration information.

spec/index.html

@@ -32,12 +32,12 @@
     }],
 
     localBiblio: {
-      "I-D.ietf-httpapi-yaml-mediatypes": {
+      "RFC9512": {
         title: "YAML Media Type",
-        href: "https://www.ietf.org/archive/id/draft-ietf-httpapi-yaml-mediatypes-03.html",
+        href: "https://www.rfc-editor.org/rfc/rfc9512",
         publisher: "IETF",
-        date: "2022-08-05",
-        status: "WG Document",
+        date: "2022-02-14",
+        status: "Informational",
         authors: [
           "Roberto Polli",
           "Erik Wilde",
@@ -355,7 +355,7 @@ <h2>Introduction</h2>
     <p>
       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 <a>YAML-LD document</a> can be represented in JSON-LD.
     </p>
@@ -902,7 +902,7 @@ <h2>Comments</h2>
       </p>
 
       <p>
-        See Interoperability considerations of [[I-D.ietf-httpapi-yaml-mediatypes]]
+        See Interoperability considerations of "+yaml" structured syntax suffix
         for more details.
       </p>
     </section>
@@ -1036,8 +1036,8 @@ <h2>Mapping Key Types</h2>
   <section id="sec" class="informative">
     <h2>Security Considerations</h2>
 
-    <p>See <a data-cite="JSON-LD11#iana-security">Security considerations in JSON-LD 1.1</a>.
-      Also, see the YAML media type registration.</p>
+    <p>See <a data-cite="JSON-LD11#iana-security">Security considerations in JSON-LD 1.1</a>
+       and <code>+yaml</code> structured syntax suffix.</p>
   </section>
 
   <section id="int" class="informative">
@@ -1046,7 +1046,7 @@ <h2>Interoperability Considerations</h2>
     <p>
       For general interoperability considerations on the serialization of
       <a>JSON documents</a> in [[YAML]], see YAML
-      and the Interoperability consideration of <code>application/yaml</code> [[I-D.ietf-httpapi-yaml-mediatypes]].
+      and the Interoperability consideration of <code>+yaml</code> structured syntax suffix.
     </p>
     <p>
       The YAML-LD format and the media type registration are not restricted to a specific
@@ -1146,7 +1146,7 @@ <h2>Streams</h2>
 
     <p class="note" title="Interoperability considerations on YAML streams">
       For interoperability considerations on YAML streams,
-      see <a data-cite="I-D.ietf-httpapi-yaml-mediatypes#section-3.2">the relevant section in YAML Media Type</a>.
+      see <a data-cite="RFC9512#section-3.2">the relevant section in YAML Media Type</a>.
     </p>
   </section>
 
@@ -1212,7 +1212,7 @@ <h3>application/ld+yaml</h3>
         </dl>
       </dd>
       <dt>Encoding considerations:</dt>
-      <dd>See <a data-cite="I-D.ietf-httpapi-yaml-mediatypes#">YAML media type</a>.</dd>
+      <dd>Same as <code>+yaml</code>.</dd>
       <dt id="iana-security">Security considerations:</dt>
       <dd>See <a href="#sec" class="sectionRef"></a>.</dd>
       <dt>Interoperability considerations:</dt>
@@ -1226,8 +1226,10 @@ <h3>application/ld+yaml</h3>
       <dt>Additional information:</dt>
       <dd>
         <dl>
+          <dt>Deprecated alias names for this type:</dt>
+          <dd>N/A</code></dd>
           <dt>Magic number(s):</dt>
-          <dd>See <code>application/yaml</code></dd>
+          <dd>Same as <code>application/yaml</code></dd>
           <dt>File extension(s):</dt>
           <dd>
             <ul>
@@ -1236,7 +1238,9 @@ <h3>application/ld+yaml</h3>
             </ul>
           </dd>
           <dt>Macintosh file type code(s):</dt>
-          <dd>TEXT</dd>
+          <dd>Same as <code>application/yaml</code></dd>
+          <dt>Windows Clipboard Name:</dt>
+          <dd>Same as <code>application/yaml</code></dd>
         </dl>
       </dd>
       <dt>Person &amp; email address to contact for further information:</dt>