From 982d437c63a0f347a490cc0ed0b3a4af240b7ed7 Mon Sep 17 00:00:00 2001
From: reluc <relu.cri@gmail.com>
Date: Mon, 14 Oct 2024 17:54:06 +0200
Subject: [PATCH 1/2] add explaination about how to get data without validation

fix #554
---
 index.html | 28 +++++++++++++++++++++++++++-
 1 file changed, 27 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 0365920a..dfcba5e0 100644
--- a/index.html
+++ b/index.html
@@ -1024,6 +1024,17 @@ <h2>The <dfn>InteractionOutput</dfn> interface</h2>
           [=Resolve=] |promise| with <a>[[\value]]</a>.
         </li>
       </ol>
+      <p>
+        While the {{value()}} function provides built-in validation, we recognize that some
+        use cases may require returning values without validation. In such cases, developers
+        can use alternative patterns, such as directly accessing the underlying data 
+        using streams or the {{InteractionOutput/arrayBuffer()}} function (See [[[#validation-arraybuffer-example]]] and [[[#stream-example]]]).
+      </p>
+      <p class="advisement" id="non-validating-value-warning" title="Implications for not using validation">
+        <strong>Warning:</strong> Disabling validation may introduce risks, particularly when interacting
+        with remote Things, as mismatches in data formats or schema expectations can lead to
+        unforeseen bugs and vulnerabilities. For more details, see the <a data-cite="wot-thing-description11#behavior-data"> consumer assertions</a>.
+      </p>
     </section>
 
     <section><h3>The  <dfn>arrayBuffer()</dfn> function</h3>
@@ -2472,10 +2483,25 @@ <h2>ConsumedThing Examples</h2>
           // image: ArrayBuffer [0x1 0x2 0x3 0x5 0x15 0x23 ...]
         }
       </pre>
+      <aside id="validation-arraybuffer-example" class="example" title="Read data without validation using arraybuffer()">
+        <p>
+          The {{InteractionOutput/arrayBuffer()}} can be used as a shortcut to skip the validation of the {{value()}} function.
+          See <a href="#non-validating-value-warning"> relevant warning</a> for the implications. 
+        </p>
+        <pre>
+          try{
+            // output is an InteractionOutput instance
+            const value = JSON.parse(Buffer.from(await output.arrayBuffer()).toString())
+            // ... custom validation
+          } catch(ex) {
+            // deal with parsing errors.
+          }
+        </pre>
+      </aside>
       <p>
         Finally, the next two examples shows the usage of a {{ReadableStream}} from an {{InteractionOutput}}.
       </p>
-      <pre class="example" title="Thing Client API example with readable stream (e.g., video stream)">
+      <pre id="stream-example" class="example" title="Thing Client API example with readable stream (e.g., video stream)">
         /*{
         "video": {
           "description" : "the video stream of this camera",

From 7dfafa8934370428ad0ac944a1b7205d7b63e74e Mon Sep 17 00:00:00 2001
From: Cristiano Aguzzi <relu91@users.noreply.github.com>
Date: Tue, 15 Oct 2024 10:47:56 +0200
Subject: [PATCH 2/2] fix "see comment"

Co-authored-by: danielpeintner <daniel.peintner@gmail.com>
---
 index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/index.html b/index.html
index dfcba5e0..b3ac2680 100644
--- a/index.html
+++ b/index.html
@@ -1028,7 +1028,7 @@ <h2>The <dfn>InteractionOutput</dfn> interface</h2>
         While the {{value()}} function provides built-in validation, we recognize that some
         use cases may require returning values without validation. In such cases, developers
         can use alternative patterns, such as directly accessing the underlying data 
-        using streams or the {{InteractionOutput/arrayBuffer()}} function (See [[[#validation-arraybuffer-example]]] and [[[#stream-example]]]).
+        using streams or the {{InteractionOutput/arrayBuffer()}} function (see [[[#validation-arraybuffer-example]]] and [[[#stream-example]]]).
       </p>
       <p class="advisement" id="non-validating-value-warning" title="Implications for not using validation">
         <strong>Warning:</strong> Disabling validation may introduce risks, particularly when interacting