issue #51 added an example of chaining IPADataProcessors.

w3c · Oct 17, 2024 · c6a4f5b · c6a4f5b
1 parent b98ec2e
commit c6a4f5b
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 3 deletions.
diff --git a/voice interaction drafts/paInterfaces/IPADataProcessors.svg b/voice interaction drafts/paInterfaces/IPADataProcessors.svg
diff --git a/voice interaction drafts/paInterfaces/paInterfaces.htm b/voice interaction drafts/paInterfaces/paInterfaces.htm
@@ -331,12 +331,20 @@ <h2 id="component-chaining">
         of the next component. Therefore, we introduced the concept of
         an <b>IPADataProcessor</b> that may receive <b>IPAData</b> from
         incoming <b>IPADataProcessors</b> and forwards <b>IPAData</b>
-        to outgoing <b>IPADataProcessor</b>. This is shown in the
-        following figure for the major components.
+        to outgoing <b>IPADataProcessor</b>. The classes for the major components are shown in the
+        following figure.
     </p>
     <img src="IPADataProcessors.svg" alt="IPA Data Processors"
         style="width: 50%; height: auto;" />
 
+    <p>Actual implementations may link them together as needed. An example is
+        shown in the following figure. For example, The IPADatProcessor Client
+        forwards the IPAData MultimodalInputs to the next IPADataProcessor
+        IPAService.</p>
+    <img src="IPAData-Processing-Chain.svg" alt="IPA Data Processing Chain"
+        style="width: 50%; height: auto;" />
+
+    <h2 id="clientlayer">
     <h1 id="highlevelinterfaces">
         <span class="secno">4. </span>High Level Interfaces
     </h1>