002 Minutes June 17, 2019

Agenda

1. Introduce yourself (5 min)
2. DMPL status update (10 min)
3. Personal Utility Model update (5 min)
4. Behavior constraint definition language proposal to begin specs (5 min)
5. Other proposals (5 min)

Tasks

• [Nishant] Ensure accessibility standards manifest in act messages.

Attendees

• Nishant
• Tim
• John
• Arpana
• Yanick

Minutes

• [All] Intros.
• [Nishant] Demonstration of DMPL progress.
  • [Nishant] Any questions?
  • [Yanick] ML techniques allows fixing conversations while they happen. How is that possible within this JSON spec?
    • [Nishant] The JSON spec outlines what actions are possible, but not which are preferred. The Personal Utility Model is one way to specify preferences, so that ML techniques may adjust weights from training data.
  • [Yanick] How is scalability addressed?
    • [Nishant] The use and run statements in DMPL allow splitting a complex dialogue experience into multiple components. Each component may be worked on independently. An inter-bot communication protocol (managing a federation of bots/skills) is in scope for a future spec.
• [John, Tim] Scripting animations has some guidelines (blind users for example). Animations need textual alternatives ("audio description", like CC). Need to think about this textualization for Act messages
  • all outputs are available on-demand
  • is the animation important or not? priority flag? so that runtime will know whether it should be described.
  • CC always in audio and text for all intents
  • However, there's more flexibility for audio descriptions of animations. Over-doing it may hurt more than help.
  • input statements should be as open as possible, too