[voiceinteraction] minutes June 14, 2023

https://www.w3.org/2023/06/14-voiceinteraction-minutes.html
and below as text
   [1]W3C

      [1] https://www.w3.org/

                             - DRAFT -
                   Voice Interaction Community Group

14 June 2023

   [2]Agenda. [3]IRC log.

      [2] https://lists.w3.org/Archives/Public/public-voiceinteraction/2023Jun/0001.html
      [3] https://www.w3.org/2023/06/14-voiceinteraction-irc

Attendees

   Present
          -

   Regrets
          bev, noreen

   Chair
          debbie

   Scribe
          ddahl2

Contents

    1. [4]look at todos

Meeting minutes

   req 47 and 49 the IPA service must forward audio output and
   text output to the IPA client if supported
   . 42 should be MUST

   57

   NLU must be able to interpret activation strategies that
   require NLU

   dirk: we want to be able to identify the target IPA
   . combine activation strategy and command in one utterance

   the NLU may be able to interpret utterances that are a
   combination of activation strategies and commands

   actually, the NLU SHOULD would be better

   58 is from an error in the architecture document

   The NLU make make use of the Data Provider to access local or
   external data

   62 is it the NLU that interprets sentiments?

   debbie: emotion can be extracted from text

   jon: EU AI act?
   . some clauses about the use of sentiment or emotion analysis

   remove intention from 62, already covered in 56

   dirk: the NLU may make use of additional multimodal input like
   emotion, sentiment and so on

   dirk: we were missing the "external service registry" in the
   diagram in 3.6

   dirk: in 69, replace "provider selection service" with
   "external service registry"

   dirk: will update the requirements and architecture documents
   with changes discussed today

   dirk: we can review the GitHub diff

   debbie: will look at the changes and make any comments

  look at todos

   dirk: will take a first pass

   debbie: number 39 is out of scope

   dirk: not sure sure what "functionality as a client activation
   strategy will be discussed in a future document" #38
   . we should remove

   dirk: "handling in case the inputs are forwarded to a nested
   IPA will be discussed in a future version of this document"

   debbie: is that any different from any input handling?

   dirk: we could delete #37

   debbie: agrees

Received on Wednesday, 14 June 2023 20:13:17 UTC