Explanation about user acts

[yobekiko]

Please update the README. The REQUEST act for user may also have optional values, just like the system REQUEST. Here is an example in dev/dialogues_018.json:

{
        "frames": [
          {
            "actions": [
              {
                "act": "REQUEST",
                "canonical_values": [
                  "2016"
                ],
                "slot": "year",
                "values": [
                  "2016"
                ]
              },
              {
                "act": "REQUEST",
                "canonical_values": [],
                "slot": "genre",
                "values": []
              }
            ],
            "service": "Music_1",
            "slots": [],
            "state": {
              "active_intent": "LookupSong",
              "requested_slots": [
                "genre",
                "year"
              ],
              "slot_values": {}
            }
          }
        ],
        "speaker": "USER",
        "utterance": "What genre is it and was it released three years back?"
      }

[abhirast]

Thank you for pointing this out. In the cases when REQUEST act has a value, the user asks the system if the slot has that value.

REQUEST(cuisine) -> What type of food does the restaurant serve?
REQUEST(cuisine=indian) -> Does the restaurant serve indian food?

We have updated the documentation accordingly.