Giorgio Robino
My feedback
-
175 votesReceived · 17 comments · Alexa Skills - Developer Voice And Vote » Routines · Flag idea as inappropriate… · Admin →Giorgio Robino
supported this idea
·
-
502 votesReceived · 296 comments · Alexa Skills - Developer Voice And Vote » Other · Flag idea as inappropriate… · Admin →Giorgio Robino
supported this idea
·
-
366 votesReceived · 14 comments · Alexa Skills - Developer Voice And Vote » Other · Flag idea as inappropriate… · Admin →Giorgio Robino
supported this idea
·
-
11 votesReceived · 1 comment · Alexa Skills - Developer Voice And Vote » Interaction Model · Flag idea as inappropriate… · Admin →Giorgio Robino
supported this idea
·
-
77 votesReceived · 7 comments · Alexa Skills - Developer Voice And Vote » Other · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment An error occurred while saving the comment Giorgio Robino
commented
Hi Mark, I voted and of course I fully agree with the change request you propose.
I reckon there are some simple solutions to manage the required state machine.
1/ simple:with a simple modification of intent model, adding a "state" attribute.
2/ a bit complex: decomposing the "singleton" Alexa cloud side machine learning in multiple learnings ( basically: different ML for different states(contexts you say).my two cents
giorgioGiorgio Robino
supported this idea
·
-
4 votesReceived · 1 comment · Alexa Skills - Developer Voice And Vote » ASK SDK · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Giorgio Robino
commented
for more details, see also: https://forums.developer.amazon.com/idea/194438/integrate-the-alexa-developer-portal-with-a-boiler.html
Giorgio Robino
shared this idea
·
-
4 votesReceived · 0 comments · Alexa Skills - Developer Voice And Vote » Other · Flag idea as inappropriate… · Admin →Giorgio Robino
supported this idea
·
-
6 votesReceived · 1 comment · Alexa Skills - Developer Voice And Vote » Other · Flag idea as inappropriate… · Admin →Giorgio Robino
supported this idea
·
-
3 votesReceived · 0 comments · Alexa Skills - Developer Voice And Vote » Alexa Developer Console · Flag idea as inappropriate… · Admin →Giorgio Robino
supported this idea
·
-
151 votesReceived · 5 comments · Alexa Skills - Developer Voice And Vote » Reminders / Timers / Alarms · Flag idea as inappropriate… · Admin →Giorgio Robino
supported this idea
·
-
55 votesReceived · 8 comments · Alexa Skills - Developer Voice And Vote » Flash Briefing · Flag idea as inappropriate… · Admin →Giorgio Robino
supported this idea
·
-
156 votes6 comments · Alexa Skills - Developer Voice And Vote » Reminders / Timers / Alarms · Flag idea as inappropriate… · Admin →
Thanks a lot for posting this request. Your request has been received
Giorgio Robino
supported this idea
·
-
277 votes24 comments · Alexa Skills - Developer Voice And Vote » Other · Flag idea as inappropriate… · Admin →
Thanks a lot for submitting this request. Your request has been recorded.
Giorgio Robino
supported this idea
·
Hi Mark, I voted and of course I fully agree with the change request you propose.
I reckon there are some simple solutions to manage the required state machine.
1/ simple:with a simple modification of intent model, adding a "state" attribute.
2/ a bit complex: decomposing the "singleton" Alexa cloud side machine learning in multiple learnings ( basically: different ML for different states(contexts you say).
my two cents
giorgio