I am developing a relatively complex skill, and I am coming up against some issues and limitations in the dialog model.
In more than one part of the skill, a RESTful API call is done, and information is retrieved and parsed into a list that the user "steps" or "chunks" through. For example, one piece has a list of movie theaters, where each theater is numbered and is read as chunks of three. i.e "Theater One is blahlblahblah, Theater Two is blablah, Theater Three is blah. Please choose a theater or say next or previous"
The issue I am coming across is, because I am using the dialog model elsewhere in the skill, the skill is unable to accept just a slot as an utterance, so a user could not say just "one", they must say "theater one". This issue comes up in other places as well, where the user has to say "theater x", "time x".
Now, I'd happily use :elicitSlot over an :ask to try to get around this, but there doesn't seem to be an easy way to handle "next" and "previous" utterances. Does anyone have any ideas on how to use the Dialog Model in the same area of a skill that is also handling next/previous chunking of information?
Ideally they'd do away with the limitations that the Dialog Model pushes on skills. The ability to use AMAZON.YesIntent/AMAZON.NoIntent/using only slots and utterances would be really nice.