- From: James A Larson <jlarson@infotoday.com>
- Date: Wed, 10 Mar 2021 08:07:44 -0800
- To: public-voiceinteraction@w3.org
- Message-ID: <89586c58-b8c1-0bb5-8b25-7f29d972bb0a@infotoday.com>
Jim’s comments on Intelligent Personal Architecture version 1.1 This is a well-written and well-organized document with lots of good ideas and suggestions. I have one major concern:standards usually involve interfaces between components, not the components or how they work.This document does not identify interfaces that should be standardized. Many of the following comments stretch the discussion from voice-centric to multimodal-centric, which I feel is the direction the world is heading. 1.Introduction Who is the audience of this document? 2.Problem statement I find this confusing.Is it hardware transparency, interoperability, or extensibility? Include principles used to decide how partition the architecture into boxes, such as separation of concerns, each box does a single activity, etc. 2.1. Travel Planning This is an example of a _specialized_ IPA 3.Architecture Begin this section with three boxes labeled client, dialog, and APIs/Data. Then have 3 additional pictures, one for each box enlarged to show its contents. Replace “microphone” by “capture” and then have a separate box to indicate alternative capturae techniques, including <microphone, ASR> < camera, vision algorithm>, <sensor, sensor interpreter> <joystick, joystsick interpreter> etc. Replace “speaker” by “presentation” and then have a separate box to indicate alternative presentation techniques including <speaker, tts>, <screen, layout renderer> and <actuator, actuator activator> Move TTS and ASR out of the dialog into the client box.They are user interface techniques rather than dialog techniques 3.3.2 dialog management(second to last bullet) Undefined term: session 3.2.2.1 (it should be 3.1.3.1) client activation strategy Include a client activation strategy involving pointing or clicking to select to the desired the target of the activation. This can be done with a mouse click or by vision in which the user points to the target. 3.2.2.1 dialog strategy Don’t just list static, preplaned strategies.Add a dialog strategy called “dynamic” that determines the next step based on previous steps. 3.2.8.1 Core dialog Undefined term: entities I ran out of time about half way through his paper.Let me know if you want me to continue with the rest (if you are still speaking to me after all of my comments above.
Received on Wednesday, 10 March 2021 16:11:45 UTC