Remove appendix on fetching and validating a TD

Author: JKRhb

index.html

@@ -4280,17 +4280,6 @@ API design rationale
         into consideration when designing a Scripting API for WoT.
       p>
     section>
-    <section> <h4>Fetching and validating a TDh4>
-      <p>
-        The <code>fetch(url)code> method has been part of this API in earlier versions. However, now fetching a <a>TDa> given a URL should be done with an external method, such as the <a data-cite="fetch#fetch-api">Fetch APIa> or a HTTP client library, which offer already standardized options on specifying fetch details. The reason is that while simple fetch operations (covering most use cases) could be done in this API, when various fetch options were needed, there was no point in duplicating existing work to re-expose those options in this API.
-      p>
-      <p>
-        Since fetching a <a>TDa> has been scoped out, and <a>TDa> validation
-        is defined externally in the [[[WOT-TD]]] specification, that is scoped out, too.
-        This specification expects a <a>TDa> as
-        <a data-cite="infra#parse-json-bytes-to-a-javascript-value">parsed JSON objecta> that has been validated according to the [[[WOT-TD]]] specification.
-      p>
-    section>
     <section> <h4>Observersh4>
       <p>
         Earlier drafts used the