act/index.html at master · conversational-interfaces/act

950 lines (866 loc) · 30.5 KB
<!DOCTYPE html>
  <meta charset='utf-8'>
  <title>Act Instruction Format</title>
  <script src='https://www.w3.org/Tools/respec/respec-w3c' class='remove' async></script>
  <script class='remove'>
    let respecConfig = {
      localBiblio: {
        "ISO-639": {
          title: "ISO-639",
          href: "https://www.iso.org/standard/22109.html",
          publisher: "International Organization for Standardization"
        "BML": {
          title: "BML",
          href: "http://www.mindmakers.org/projects/bml-1-0/wiki",
          publisher: "BML 1.0 Standard"
        "DCMP": {
          title: "DCMP",
          href: "https://www.3playmedia.com/resources/popular-topics/closed-captioning/",
          publisher: "3PlayMedia"
      wg: "Conversational Interfaces Working Group",
      wgURI: "https://www.w3.org/community/conv/",
      wgPublicList: "public-conv",
      specStatus: "CG-DRAFT",
      shortName: "dmpl",
      editors: [{
        name: "Nishant Shukla",
        url: "https://shukla.io",
        w3cid: 112944
        name: "Nawar Rajab",
        url: "https://nawarrajab.com"
        name: "Nelson Solano",
        url: "https://www.linkedin.com/in/nelson-solano-24a935126/",
        w3cid: 113168
      edDraftURI: "https://github.com/conversational-interfaces/act",
      addSectionLinks: true,
      isPreview: true,
      lint: {
        "check-punctuation": true
  </script>
  <section id='abstract'>
      This specification defines the syntax and semantics of a behavior definition language.
      A service may send instructions encoded in this format for clients such as 3D game engines to realize.
      These messages include instructions about positioning objects, activating or deactivating systems,
      changing scenes or contexts, controlling visual properties, animating characters, and playing audio.
  </section>
  <section id='sotd'></section>
  <section id="conformance"></section>
  <section>
    <h2>Introduction</h2>
      The message format outlined in this specification allows for fine-control execution
      of agents in a virtual or live environment.
      <a href="https://www.json.org/">JSON</a> may be one possible vessel for these types of messages.
    <section>
      <h2>Scope</h2>
      <i>This section is informative.</i>
      <p>In progress...</p>
    </section>
    <section>
      <h2>Goals and Motivation</h2>
      <i>This section is informative.</i>
      <p>In progress...</p>
    </section>
  </section>
  <section>
    <h2>Message Format</h2>
    <i>This section is normative.</i>
    <section data-dfn-for="Behavior" data-link-for="Behavior">
      <h2><dfn>Behavior</dfn> Interface</h2>
      The atomic unit that can be immediately realized by a client is called a <a>behavior</a>.
      Consider the sentence, "The boy says hello."
      By analyzing the grammar, we find the subject is "boy", the verb is "says", and the direct-object is "hello".
      The intuition behind the <a>behavior</a> interface is to represent a similar structure.
      <pre class="idl">
        [Exposed]
        interface Behavior {
          attribute long id;
          attribute DOMString subject;
          attribute DOMString action;
          attribute Params params;
          attribute double delay;
          attribute Dictionary start;
          attribute SequenceOfStrings cc;
      </pre>
      <pre class="idl">
        typedef sequence&lt;DOMString&gt; SequenceOfStrings;
      </pre>
      <section>
        <h3><dfn>id</dfn> attribute</h3>
        <p>
          The <a>id</a> specifies the unique identifier. Note that
          <a>id</a>'s are non unique across different blocks.
        </p>
      </section>
      <section>
        <h3><dfn>subject</dfn> attribute</h3>
        <p>
          The <a>subject</a> attribute is the name of the agent that is performing an action. In grammar, this is often
          called the <i>subject</i> of a verb.
          Examples include:
        </p>
        <pre class="example">
              "boy"
          </pre>
        <p>
          And even abstract nouns such as the following.
        </p>
        <pre class="example">
              "system"
          </pre>
      </section>
      <section>
        <h3><dfn>action</dfn> attribute</h3>
        <p>
          Each <a>subject</a> affords a set of actions. The <a>action</a> attribute specifies one of those available
          actions.
          For example, if the subject is "boy", a possible action may look as follows.
        </p>
        <pre class="example">
            "say"
        </pre>
        <p>
          And if the subject is "system", a possible action may be an abstract concept as follows.
        </p>
        <pre class="example">
            "initialize"
        </pre>
      </section>
      <section>
        <h3><dfn>params</dfn> attribute</h3>
        <p>
          The <a>Params</a> attribute specifies the data-structure containing all data to be received and manipulated
          by the client. See <a>Params</a> below.
        </p>
        <pre class="idl">
          [Exposed]
          interface Params {
            attribute String intent;
            attribute String ssml;
            attribute String name;
            attribute String url;
            attribute Phonemes phonemes;
            attribute String language;
            attribute Dictionary context;
        </pre>
        <section>
          <h3><dfn>intent</dfn> attribute</h3>
          <p>
            The <a>intent</a> attribute specifies what a user is trying to accomplish. An <a>intent</a> is specified
            within a <a>String</a> data type.
          </p>
          <pre class="example">
                "statement.i-can-help"
            </pre>
        </section>
        <section>
          <h3><dfn>ssml</dfn> attribute</h3>
          <p>
            The <a>ssml</a> attribute specifies the speech synthesis markup language for the specified intent. The
            <a>ssml</a> is specified within a <a>String</a> data type.
          </p>
          <pre class="example">
                "I can help you with that!"
            </pre>
        </section>
        <section>
          <h2><dfn>name</dfn> attribute</h2>
          <p>
            The <a>name</a> attribute specifies the name of the audio file to be played.
          </p>
          <pre class="example">
            </pre>
        </section>
        <section>
          <h2><dfn>url</dfn> attribute</h2>
          <p>
            The <a>url</a> attribute specifies the source location of the audio file to be played. The <a>url</a>
            attribute is specified within a <a>String</a> data type.
          </p>
          <pre class="example">
                "http://audioURL..."
            </pre>
        </section>
        <section>
          <h3><dfn>language</dfn> attribute</h3>
          <p>
            The <a>language</a> attribute specifies the tongue in which any text, or audio will be communicated in. The
            language is specified by the three letter codec abiding
            <code><dfn data-cite="!ISO-639#">ISO-639.</dfn></code>
            The following example shows the three letter codec for the English language.
          </p>
          <pre class="example">
              "eng"
          </pre>
        </section>
        <section>
          <h3><dfn>phonemes</dfn> attribute</h3>
          <p>
            The <a>phonemes</a> attribute is an object containing the phonetic translation and
            total
            number of frames belonging to the corresponding <a>ssml</a> text. See <a>Phonemes</a> below.
          </p>
          <pre class="example">
              "segments": [
                  "phonemeLabel": "IY",
                  "startFrame": 3
              "framecount": 202
          </pre>
          <pre class="idl">
            typedef sequence< Dictionary > dictionarySequence;
            [Exposed]
            interface Phonemes {
              attribute dictionarySequence segments;
              attribute long framecount;
          </pre>
          <section>
            <h3><dfn>segments</dfn> attribute</h3>
              A custom <a>typedef</a> was defined such that a <a>sequence</a> of <a>Dictionary</a>'s corresponds to a
              <a>dictionarySequence</a>. Each <a>Dictionary</a> object within the <a>segments</a> attribute is a
              <a>Dictionary</a> containing a pair of <code>key:value</code> attributes. The first item in each nested
              <a>Dictionary</a> is specified by a <code><a>String</a>:<a>String</a></code> pairing denoting a phonetic
              label. The second <a>Dictionary</a> item corresponds to a
              <code><a>String</a> : <a>double</a></code> pairing
              corresponding to the start frame of the phonetic label.
            </p>
            <pre class="example">
                  "phonemeLabel": "IY",
                  "startFrame": 3
            </pre>
          </section>
          <section>
            <h3><dfn>framecount</dfn> attribute</h3>
              The <a>framecount</a> attribute specifies the total number of feature frames of the transcribed ssml
              text.
            </p>
            <pre class="example">
              </pre>
          </section>
        </section>
        </section>
        <section>
          <h3><dfn>context</dfn> attribute</h3>
          <p>
            The <a>context</a> attribute specifies a
            <code><dfn data-cite="!WebIDL-1/#dfn-dictionary">Dictionary</dfn></code> as defined
            in [[WebIDL-1]]. The dictionary members are specified in <code>key:value</code> pairs where both
            <code>key</code> and <code>value</code> of of type <a>String</a>.
          </p>
          <pre class="example">
              "category": "colors",
              "gamestate" : "1",
              "target" : "blue"
          </pre>
        </section>
        <section>
          <h3><dfn>delay</dfn> attribute</h3>
          <p>
            The <a>delay</a> attribute specifies the number of seconds to wait to perform a corresponding action through a
            <code><dfn data-cite="!WebIDL-1/#idl-double">double</dfn></code> data type.
          </p>
          <pre class="example">
            </pre>
        </section>
        <section>
          <h3><dfn>start</dfn> attribute</h3>
          <p>
            The <a>start</a> attribute is an optional <a>Dictionary</a> argument that specifies when the <a>Behavior</a>
            should begin
            its execution, specified by a <code>trigger</code> and an <code>id</code>.
          </p>
          <section>
            <h3><dfn>trigger</dfn> key</h3>
              The <b>trigger</b> attribute specifies the point at which the <a>Behavior</a> corresponding to the
              specified <a>id</a> should begin its execution. The trigger value may be <code>"start"</code> or <code>"end"</code>.
            </p>
          </section>
          <section>
            <h3><a>id</a> key</h3>
              The <b>id</b> key specifies the <a>Behavior</a> that will be affected by the corresponding
              <a>trigger</a> value.
            </p>
            <pre class="example">
            </pre>
            <pre class="example">
                  "trigger" : "end",
              </pre>
          </section>
        </section>
        <section>
          <h3><dfn>cc</dfn> attribute</h3>
          <p>
            In defining the <a>cc</a> attribute, a custom
            <code><a>typedef</a></code> was used such that a <a>sequence</a> of the <a>String</a>'s corresponds to a
            <a>SequenceOfStrings</a> data type. The <dfn data-cite="!WebIDL-1/#idl-DOMString">String</dfn> data type
            defined in [[WebIDL-1]] is used. The <a>cc</a> attribute is then specified by a
            <a>sequence</a> of
            <code><dfn data-cite="!DCMP#">DCMP</dfn></code> standard abiding <a>String</a>'s, containing the textual
            representation of any corresponding events within the message.
          </p>
          <!--https://www.captioningkey.org/speaker_identification.html-->
          <!--https://www.captioningkey.org/sound_effects.html-->
          <p>
            The following example describes the closed captioning for the event where a character named Frog excitedly
            says 'Hi there!'.
          </p>
          <pre class="example">
                  "[Frog excited]",
                  "Hi there!"
          </pre>
          <p>
            The following example describes the closed captioning for the event where a character named Pig says
            'Welcome back!' in a Southern Accent.
          </p>
          <pre class="example">
                  "[Pig Southern Accent]",
                  "Welcome back!"
          </pre>
          <p>
            The following example shows the closed captioning for the event where three characters are simultaneously
            cheering.
          </p>
          <pre class="example">
              "[Frog, Pig, Goose cheering]"
          </pre>
          <p>
            The following example shows the closed captioning for the event where a Cow is Mooing.
          </p>
          <pre class="example">
              "[Cow moo's]"
          </pre>
        </section>
    </section>
  </section>
  <section>
    <h2>Blocks</h2>
    <i>This section is informative.</i>
      In order to synchronize behavior (especially the "say" and "animate" actions), we propose to use the
      "message block". A message block is an ordered <a>sequence</a> of <a>Behavior</a> objects, where each object
      conforms to the
      <a>Behavior</a> message format specified within this document. The server sends sequences of blocks, and the
      client (e.g. Unity)
      must fully process one block of <a>Behavior</a> before reading the next block. While processing a single
      block of <a>Behavior</a>s,
      the client should schedule <a>Behavior</a>s by putting them on "tracks"(every action of every object has a
      track),
      then all the tracks start simultaneously.
    <section>
      <h2>Examples</h2>
      <i>This section is informative.</i>
        Suppose a humanoid agent named <code>goose</code> stands near a landmark labelled <code>Landmark_1</code>.
      <p><i>Goose walks towards a landmark named <code>Landmark_1</code></i>.</p>
      <pre class="example" title="Walk towards an object">
            "subject": "goose",
            "action": "do",
            "params": {
              "name": "walk",
              "context": ["Landmark_1"]
      </pre>
      <p><i>Goose points at a landmark named <code>Landmark_1</code>.</i></p>
      <pre class="example" title="Point at an object indefinitely">
            "object": "goose",
            "action": "do",
            "params": {
              "name": "point",
              "context": ["Landmark_1", "enabled"]
      </pre>
      <p><i>Goose points at a landmark named <code>Landmark_1</code>, and stops after 2 seconds.</i></p>
      <pre class="example" title="Point for 2 seconds">
            "object": "goose",
            "action": "do",
            "params": {
              "name": "point",
              "context": ["Landmark_1", "enable"]
            "object": "goose",
            "action": "do",
            "params": {
              "name": "point",
              "context": ["Landmark_1", "disable"]
            "delay": 2.0
      </pre>
      <p><i>Goose looks at a landmark named <code>Landmark_1</code>.</i></p>
      <pre class="example" title="Look at an object indefinitely">
            "object": "goose",
            "action": "do",
            "params": {
              "name": "look",
              "context": ["Landmark_1", "enable"]
      </pre>
      <p><i>Goose looks at a landmark named <code>Landmark_1</code>, and stops after 2 seconds.</i></p>
      <pre class="example" title="Look for 2 seconds">
            "object": "goose",
            "action": "do",
            "params": {
              "name": "look",
              "context": ["Landmark_1", "enable"]
            "object": "goose",
            "action": "do",
            "params": {
              "name": "look",
              "context": ["Landmark_1", "disable"]
            "delay": 2.0
      </pre>
      <p><i>Goose turns body to a landmark named <code>Landmark_1</code>.</i></p>
      <pre class="example" title="Turn to an object">
            "object": "goose",
            "action": "do",
            "params": {
              "name": "turn",
              "context": ["Landmark_1"]
      </pre>
      <p><i>Goose walks towards a landmark named <code>Landmark_1</code> while pointing at it.</i></p>
      <pre class="example" title="Point and walk">
            "object": "goose",
            "action": "do",
            "params": {
              "name": "point",
              "context": ["Landmark_1", "enable"]
            "object": "goose",
            "action": "walk",
            "params": {
              "name": "point",
              "context": ["Landmark_1"]
      </pre>
      <p><i>Goose walks towards a landmark named <code>Landmark_1</code> while pointing at it, then stops
          pointing.</i></p>
      <pre class="example" title="Point and walk">
            "object": "goose",
            "action": "do",
            "params": {
              "name": "point",
              "context": ["Landmark_1", "enable"]
            "object": "goose",
            "action": "walk",
            "params": {
              "name": "point",
              "context": ["Landmark_1"]
            "object": "goose",
            "action": "do",
            "params": {
              "name": "point",
              "context": ["Landmark_1", "disable"]
      </pre>
        In the following example we examine events A and B: we want to enforce that event B can't start
        until event A has started.
      <p><i>Right when Goose starts speaking, Fox jumps.</i></p>
      <pre class="example" title="Start-to-Start">
            "subject": "goose",
            "action": "say",
            "params": {"name": "GO_0020" , "ssml": "I can help you with that!"}
            "subject": "fox",
            "action": "animate",
            "params": {"name": "FX_Jump"}
      </pre>
        In this example we want to run the statements in a particular sequence. Specifically, B can't start until
        A has finished. In order to achieve the desired order, we place each behavior in a separate block.
      <i>Only when Goose is done speaking, is the Fox able to jump.</i>
      <pre class="example" title="Finish-to-Start">
            "subject": "goose",
            "action": "say",
            "params": {"name": "GO_0020" ,"intent": "statement.i-can-help","ssml": "I can help you with that!"}
            "subject": "fox",
            "action": "animate",
            "params": {"name": "FX_Jump"}
      </pre>
        In this example we show how to sequence actions together.
      <i>Goose waves hands as it starts speaking. After hand-waving animation completes, sound effect plays.</i>
      <pre class="example" title="Sequencing Actions">
          {"id": "0", "subject": "goose", "action": "animate", "params": {"name": "wave-hands"}},
          {"subject": "goose", "action": "say", "params": {"name": "GO_0020" ,"intent": "greeting"}},
          {"subject": "sound", "action": "play", "params": {"name": "sfx.boom" ,"intent": "sfx.boom"}, "start": {"trigger" : "end", "id":0}}
      </pre>
    </section>
      In this example we show how to sequence actions together.
    <i>Goose waves hands as it starts speaking. After audio of utterances completes, then the sound effect plays.</i>
    <pre class="example" title="Sequencing Actions">
        {"subject": "goose", "action": "animate", "params": {"name": "wave-hands"}},
        {"subject": "goose", "action": "say", "params": {"name": "GO_0020" ,"intent": "greeting"}},
        {"subject": "sound", "action": "play", "params": {"name": "sfx.boom"}, "start": {"trigger" : "end", "id":1}}
      In this example we show how to control different subjects in parallel.
    <i>Goose and fox cheer "yay!", together at the same time.</i>
    <pre class="example" title="Parallel Actions">
        {"subject": "goose", "action": "say", "params": {"name": "GO_0020","intent": "yay"}},
        {"subject": "fox", "action": "say", "params": {"name": "FX_0020","intent": "yay"}}
      In this example we show how to control different subjects in parallel.
    <i>Goose and fox cheer together, and then jump together.</i>
    <pre class="example" title="Parallel Actions">
        {"subject": "goose", "action": "say", "params": {"name": "GO_0020" ,"intent": "yay"}},
        {"subject": "fox", "action": "say", "params": {"name": "FX_0020" ,"intent": "yay"}}
        {"subject": "goose", "action": "animate", "params": {"name": "jump"}},
        {"subject": "fox", "action": "animate", "params": {"name": "jump"}}
      In the following examples we show how to control different objects in parallel.
    <i>Goose and fox cheer together (goose finishes before fox). Goose's jump animation starts right after cheering.
      Same for Fox.</i>
    <pre class="example" title="Parallel Actions">
        {"id": "0", "subject": "goose", "action": "say", "params": {"name": "GO_0020" ,"intent": "yay"}},
        {"id": "1", "subject": "fox", "action": "say", "params": {"name": "FX_0020" ,"intent": "yay"}},
        {"subject": "goose", "action": "animate", "params": {"name": "jump"}, "start": {"trigger" : "end", "id":0}},
        {"subject": "fox", "action": "animate", "params": {"name": "jump"}, "start": {"trigger" : "end", "id":1}}
    <i>The Goose says 'hello' and waves hand at the Fox. The Fox says 'hi' back (without interrupting the goose's
      utterance.</i>
    <pre class="example">
        {"subject": "goose", "action": "say", "params": {"name": "GO_0020" ,"intent": "greeting"}},
        {"subject": "goose", "action": "animate", "params": {"name": "wave-hands"}},
        {"subject": "fox", "action": "say", "params": {"name": "FX_0020" ,"intent": "greeting"}, "start": {"trigger" : "start", "id":1}, "delay": 0.5}
  </section>
  <section>
    <h2>More Examples</h2>
    <i>This section is normative.</i>
      The following are examples of objects and their associated behaviors. Note that the specified parameters
      for each of the following actions are <i>normative</i>.
    <section>
      <h2><code><dfn>Animate</dfn></code></h2>
        An <a>animate</a> payload specifies an object to be animated by the client.
      <pre class="example" title="Animate Message Payload">
          "subject": "goose",
          "action": "animate",
          "delay": 0,
          "params": { "name": "FR_Maracas_1" }
      </pre>
    </section>
    <section>
      <h2><code><dfn>Say</dfn></code></h2>
      <p>A <a>say</a> payload specifies what the desired subject should say.</p>
      <pre class="example" title="Say Message Payload">
          "subject": "frog",
          "action": "say",
          "delay": 0,
          "params": {
            "intent": "statement.i-can-help",
            "ssml": "I can help you with that!",
            "name": "GO_0020",
            "url": "http://audioURL...",
            "phonemes": {
              "segments": [
                  "phonemeLabel": "IY",
                  "startFrame": 3
              "framecount": 202
      </pre>
    </section>
    <section>
      <h2><code><dfn>Do</dfn></code></h2>
      <p>A <a>do</a> payload specifies the name of the action the specified target should perform.</p>
      <pre class="example" title="Do Message Payload">
              "subject": "goose",
              "action": "do",
              "delay": 0,
              "params": { "name": "walk", "context" : ["pig"]}
          </pre>
    </section>
    <section>
      <h2><code><dfn>Play</dfn></code></h2>
      <p>A <a>play</a> payload specifies the audio clip the client should play.</p>
      <pre class="example" title="Play Message Payload">
              "subject": "sound",
              "action": "play",
              "delay": 0,
              "params": { "name": "sxf.bonusround.wav" }
          </pre>
    </section>
    <section>
      <h2><code><dfn>Spawn</dfn></code></h2>
      <p>A <a>spawn</a> payload notifies the client to display the specified object.</p>
      <pre class="example" title="Spawn Message Payload">
          "subject": "system",
          "action": "spawn",
          "delay": 0,
          "params": {"name": "frog", "context": ["character2"]}
      </pre>
    </section>
    <section>
      <h2><code><dfn>Destroy</dfn></code></h2>
      <p>A <a>destroy</a> payload notifies the client to remove the specified object.</p>
      <pre class="example" title="Destroy Message Payload">
          "subject": "system",
          "action": "destroy",
          "delay": 0,
          "params": {"name": "frog"}
      </pre>
    </section>
    <section>
      <h2>Interruption handling</h2>
        The client may store blocks in a queue and realize the behaviors at its own pace.
        In the following example, the queue is cleared by calling <code>clear</code> action on a <code>system</code> subject.
      <pre class="example">
          "subject": "system",
          "action": "clear"
      </pre>
        Clearing the queue only removes future actions, but doesn't interrupt the current actions.
        The following example shows how to immediately terminte actions that are currently being performed.
        The <code>params.ignore</code> field is a list of subjects to ignore/skip, if desired.
      <pre class="example">
          "subject": "system",
          "action": "interrupt",
          "params": {
            "ignore": ["music"]
      </pre>
        Clearing the queue and interrupting current actions are two behaviors that tend to be performed together.
        The following block shows how to send both behaviors at once.
      <pre class="example">
            "subject": "system",
            "action": "clear"
            "subject": "system",
            "action": "interrupt",
            "params": {
              "ignore": ["music"]
      </pre>
    </section>
  </section>
  <section>
    <h2>Related Technologies</h2>
    <i>This section is informative.</i>
    <section>
      <h2><a href="http://www.mindmakers.org/projects/bml-1-0/wiki">BML</a></h2>
        The following <code><dfn data-cite="!BML#">BML</dfn></code> snippet simultaneously starts an
        animation and a speech utterance.
      <pre class="example">
        &ltbml character="Alice"&gt
            &ltpointing target="blueBox" mode="RIGHT_HAND" start="speech1:start"/&gt
            &ltspeech id="speech1"&gt
                &lttext>Look there!&lt/text&gt
            &lt/speech&gt
        &lt/bml&gt
      </pre>
    </section>
    <p>The equivalent behavior can be represented as follows.</p>
    <pre class="example">
        {"subject": "Alice", "action": "do", "params": {"name": "point", "context": ["blueBox", "mode": "RIGHT_HAND"]}},
        {"subject": "Alice", "action": "say", "params": {"intent": "look"}}
    <p><a>BML</a> documentation recommends using <code>&ltwait&gt</code> to align behavior with a condition or an
      event.</p>
    <pre class="example">
      &ltbml character="Alice"&gt
        &ltgesture id=”g1” type=”point” target=”object1”/&gt
        &ltbody id=”b1” posture=”sit”/&gt
        &ltwait id=”w1” condition=”g1:end AND b1:end”/&gt
        &ltgaze target=”object2” start=”w1:end”/&gt
      &lt/bml&gt
    <p>The <code>&ltwait&gt</code> is unnecessary since we can synchronize 
      behaviors by placing them in different blocks.</p>
    <pre class="example">
        {"subject": "Alice", "action": "do", "params": {"name": "point", "context": ["object1"]}},
        {"subject": "Alice", "action": "do", "params": {"name": "body", "context": ["sit"]}}
        {"subject": "Alice", "action": "animate", "params": {"name": "gaze"}}
      Multi-party behavior synchronization is limited. 
      It's non-trivial to have two characters say something at the same time as <a>BML</a>.
    <pre class="example">
      &ltbml character="Alice"&gt
          &ltspeech&gt&lttext&gtYay!&lt/text&gt&lt/speech&gt
      &lt/bml&gt
      &ltbml character="Bob"&gt
          &ltspeech&gt&lttext&gtYay!&lt/text&gt&lt/speech&gt
      &lt/bml>
    <p>Act message format allows fine-control of multi-party behaviors, with a natural syntax.</p>
    <pre class="example">
        {"subject": "Alice", "action": "say", "params": {"intent": "yay"}},
        {"subject": "Bob", "action": "say", "params": {"intent": "yay"}}
  </section>
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

FilesExpand file tree

index.html

Latest commit

History

index.html

File metadata and controls
