Merge pull request #67 from darobin/fix/de-nonsensify-description-of-DAG-JSON

address issue 65

Author: darobin

drisl.src.html

@@ -70,24 +70,5 @@ <h2>CIDs in CBOR</h2>
         For more information, see the [[cbor-tag42]] appendix to the [[drisl]] specification.
       </p>
     </section>
-    <section>
-      <h2>Debugging Considerations</h2>
-      <p>
-        It is often convenient to represent DRISL in textual formats for debugging
-        purposes, for example using JSON.
-      </p>
-      <p>
-        One common convention for doing so is historically referred to as "DAG-JSON," which is a JSON expression
-        of the DRISL data in which CIDs are represented as the object
-        <code>{ "/": "string CID" }</code>, i.e., DASL CIDs in their base-32 ASCII representation ([[cid]]), NOT in their CBOR representation ([[cbor-tag42]])). Another option is
-        <a href="https://datatracker.ietf.org/doc/draft-ietf-cbor-edn-literals/">CBOR
-        Extended Diagnostic Notation</a>.
-      </p>
-      <p>
-        In any case, note that the CIDs used in such debugging outputs that may
-        point to <em>other</em> parts of the debugging output should be the CIDs
-        of the DRISL content, not of the debugging resources.
-      </p>
-    </section>
   </body>
 </html>