4 ms·
They have listed the problems with such systems in the first paragraph. They claim to overcome these by restricting to very specific domains. But specific doma
by cosmic_ape 8y ago
They have listed the problems with such systems in the first paragraph. They claim to overcome these by restricting to very specific domains. But specific domains are usually still wide. A table for two, but in the garden or inside? Inside on which floor? Sometimes it doesn't matter, sometimes it does, and these things are specific and different for every business.
Really skeptical about this. And if this does become a thing, it will dumb down the interaction.
- sushirain 8y agoThe bot can gather this restaurant specific information over several conversations with the restaurant. This wasn't possible before. This domain isn't too wide.
- cosmic_ape 8y agoYou are probably right that in principle one could eventually come up with a full catalog of features of a reservation. There would be about, say, 100 of those. I seriously doubt that they will proceed to define and collect them, since those are probably 10% or less of all reservations, but lets say they would. Then still, the conversation you make to make the reservation is a process in which you make the decision. Say, there is a place inside at 20:00 or a place in the garden at 20:30. Are you going to let Google choose between the two options for you? Do you imagine there would be an api in which you specify to the assistant, before it makes a call, your preferences in that much granularity?