Descriptive content

spec/common/biblio.js

@@ -0,0 +1,55 @@
+const rch = {
+  // Add as the respecConfig localBiblio variable
+  // Extend or override global respec references
+  localBiblio: {
+    "CCG-RDC-FINAL": {
+      id: "CCG-RDC-FINAL",
+      title: "RDF Dataset Canonicalization",
+      authors: ["Dave Longley"],
+      editors: [
+        "Dave Longley",
+        "Manu Sporny"
+      ],
+      date: "2022-10-09",
+      href: "https://www.w3.org/community/reports/credentials/CG-FINAL-rdf-dataset-canonicalization-20221009/",
+      status: "CG-FINAL",
+      publisher: "W3C"
+    },
+    "DesignIssues-Diff": {
+      id: "DesignIssues-Diff",
+      title: "Delta: an ontology for the distribution of differences between RDF graphs",
+      authors: ["Tim Berners-Leee"],
+      date: "2015-09-25",
+      href: "https://www.w3.org/DesignIssues/Diff",
+      status: "unofficial",
+      publisher: "W3C"
+    },
+    "eswc2014Kasten": {
+      id: "eswc2014Kasten",
+      title: "A Framework for Iterative Signing of Graph Data on the Web",
+      authors: ["Andreas Kasten", "Ansgar Scherp", "Peter Schauß "],
+      date: "2014",
+      href: "https://doi.org/10.1007/978-3-319-07443-6_11",
+      status: "unofficial",
+      publisher: "ISWC 2014"
+    },
+    "Hogan-Canonical-RDF": {
+      id: "Hogan-Canonical-RDF",
+      title: "Canonical Forms for Isomorphic and Equivalent RDF Graphs: Algorithms for Leaning and Labelling Blank Nodes",
+      authors: ["Aiden Hogan"],
+      date: "2017-07-17",
+      href: "https://aidanhogan.com/docs/rdf-canonicalisation.pdf",
+      status: "unofficial",
+      publisher: "ACM Transactions on the Web"
+    },
+    "HPL-2003-142": {
+      id: "HPL-2003-142",
+      title: "Signing RDF Graphs",
+      authors: ["Jeremy J. Carroll"],
+      date: "2003-07-23",
+      href: "https://www.hpl.hp.com/techreports/2003/HPL-2003-142.pdf",
+      publisher: "HP Laboratories Bristol",
+      status: "unofficial"
+    }
+  }
+};

spec/common/typographical-conventions.html

@@ -0,0 +1,46 @@
+<p>The following typographic conventions are used in this specification:</p>
+
+<dl class="typography">
+  <dt><code>markup</code></dt><dd>
+    Markup (elements, attributes, properties),
+    machine processable values (string, characters, media types),
+    property names,
+    and file names are in red-orange monospace font.</dd>
+  <dt><var>variable</var></dt><dd>
+    A variable in pseudo-code or in an algorithm description is italicized.</dd>
+  <dt><dfn data-no-xref="">definition</dfn></dt><dd>
+    A definition of a term, to be used elsewhere in this or other specifications,
+    is italicized and in bold.</dd>
+  <dt><a data-lt="definition">definition reference</a></dt><dd>
+    A reference to a definition <em>in this document</em>
+    is underlined and is also an active link to the definition itself. </dd>
+  <dt><a data-lt="definition"><code>markup definition reference</code></a></dt><dd>
+    References to a definition <em>in this document</em>,
+    when the reference itself is also a markup, is underlined,
+    in a red-orange monospace font, and is also an active link to the definition itself.</dd>
+  <dt><a class="externalDFN">external definition reference</a></dt><dd>
+    A reference to a definition <em>in another document</em>
+    is underlined and italicized, and is also an active link to the definition itself.</dd>
+  <dt><a class="externalDFN"><code> markup external definition reference</code></a></dt><dd>
+    A reference to a definition <em>in another document</em>,
+    when the reference itself is also a markup,
+    is underlined and italicized in a red-orange monospace font,
+    and is also an active link to the definition itself.</dd>
+  <dt><a href="">hyperlink</a></dt><dd>
+    A hyperlink is underlined and in blue.</dd>
+  <dt>[<a href="">reference</a>]</dt><dd>
+    A document reference (normative or informative) is enclosed in square brackets
+    and links to the references section.</dd>
+</dl>
+
+<p class="note">Notes are in light green boxes with a green left border and with a "Note" header in green.
+  Notes are always informative.</p>
+
+<pre class="example nohighlight">
+  Examples are in light khaki boxes, with khaki left border,
+  and with a numbered "Example" header in khaki.
+  Examples are always informative. The content of the example is in monospace font and may be syntax colored.
+
+  Examples may have tabbed navigation buttons
+  to show the results of transforming an example into other representations.
+</pre>