Re: Session concept

A session may end when the user tells the device to end it. This happens
with my Sonos music streaming player. Devices, especially those that are
"always listening" should always provide a way for a user to end the
session and stop any sound data capture until it hears the start phrase.
It's a matter of consent.

On Wed, Feb 21, 2024 at 3:58 PM Dirk Schnelle-Walka <
dirk@switch-consulting.de> wrote:

> Dear all
>
> In today's session we also spoke about the concept of a session. In
> https://w3c.github.io/voiceinteraction/voice%20interaction%20drafts/paArchitecture/paArchitecture-1-3.htm#session
> we defined a session as:
>
> ---
> Conceptually, multiple sessions can be active in parallel. Dialog
> execution can be governed by a sessions, e.g. to free resources of ASR and
> NLU engines when a session expires. Linguistic phenomena, like anaphoric
> references and ellipsis, are expected to work within a session. The
> selected IPA Providers or the Dialog Manager may have leading roles for
> this task.
>
> A session begins when the user starts to interact with an IPA, may
> continue over multiple interaction turns, i.e. an input and output cycle,
> and ends if the user does not start a new input within a predefined time
> span. This includes the possibility that a session may persist over
> multiple requests.
> ---
>
> Maybe, we could discuss next time, if this is sufficient or ought to be
> changed.
>
> Dirk
>


-- 
Noreen Whysel
nwhysel@gmail.com
http://www.whysel.com