[#83]: Add Node Identifier Value Types section

Author: anatoly-scherbakov

index.html

@@ -1032,6 +1032,48 @@ <h2>Mapping Key Types</h2>
         Mapping key type MUST be a <code>string</code>. Otherwise, a processing error is raised.
       </p>
     </section>
+
+    <section id="scalar-value-types">
+      <h2>Scalar Value Types</h2>
+
+      <p>
+        YAML-LD supports only the data types that [[JSON]] supports: <a>string</a>,
+        <a>number</a>, <a>boolean</a>, <a>null</a>, and the composite types <a>array</a>
+        and <a>object</a>.
+        The <a data-cite="YAML#core-schema">YAML Core Schema</a> may recognize additional
+        scalar types, such as date (e.g. unquoted <code>2018-04-01</code>).
+        Such YAML-native types are not supported.
+        Documents containing scalar values that are not one of the supported JSON types
+        MAY cause <a data-cite="JSON-LD11-API#dom-jsonlderrorcode-loading-document-failed">loading-document-failed</a>
+        error.
+        Authors SHOULD use quoted strings for date-like values (e.g. <code>"2018-04-01"</code>)
+        to ensure they are parsed as strings.
+      </p>
+    </section>
+
+    <section id="node-identifier-value-types">
+      <h2>Node Identifier Value Types</h2>
+
+      <p id="aa-id-value-type" data-tests="
+        manifest.html#id-type-date-negative,
+        manifest.html#id-type-int-negative,
+        manifest.html#id-type-bool-true-negative,
+        manifest.html#id-type-float-negative,
+        manifest.html#id-type-bool-false-negative,
+        manifest.html#id-type-bool-yes-negative,
+        manifest.html#id-type-bool-no-negative,
+        manifest.html#id-type-bool-on-negative,
+        manifest.html#id-type-bool-off-negative">
+        Values of <code>@id</code> and of properties with <code>@type: "@id"</code> in context
+        MUST be <a>strings</a> for IRI resolution.
+        The <a data-cite="YAML#core-schema">YAML Core Schema</a> may recognize values such as
+        <code>true</code>, <code>42</code>, <code>3.14</code>, and <code>2018-04-01</code>
+        as boolean, integer, float, or date.
+        Documents with non-string values in those positions cause a
+        <a data-cite="JSON-LD11-API#dom-jsonlderrorcode-loading-document-failed">loading-document-failed</a>
+        error.
+      </p>
+    </section>
   </section>
 
   <section id="sec" class="informative">