You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The original implementation of this skill liberally used AMAZON.LITERAL for all slot types. This worked fine, but when I had to adapt to changes in the backend show JSON, I was unable to deploy the skill because AMAZON.LITERAL is deprecated.
For simplicity's sake, I changed the slots to AMAZON.SearchQuery, which is roughly equivalent to AMAZON.LITERAL, but a wiser move would be to create a custom entity type for shows. In it's simplest form, the type could be hard-coded with an entry to represent all NFJS events (e.g., "Northern Virginia Software Symposium", "Lone Star Software Symposium", "Progressive Web Experience") as well as synonyms for each of those (e.g., "Reston", "Dallas", "Clearwater").
That would work until a new NFJS event is created. Suppose that we decide to do an Australian tour, there would be no entries for Sydney, Melbourne, etc, so the interaction model would need to be updated to include the new events and the skill republished. Instead, it might be wiser still to create a custom type for shows, but make it a dynamic entity (see https://developer.amazon.com/docs/custom-skills/use-dynamic-entities-for-customized-interactions.html) which is populated from actual show data. Then it would be flexible enough to support any new shows that are introduced.
The text was updated successfully, but these errors were encountered:
The original implementation of this skill liberally used
AMAZON.LITERAL
for all slot types. This worked fine, but when I had to adapt to changes in the backend show JSON, I was unable to deploy the skill becauseAMAZON.LITERAL
is deprecated.For simplicity's sake, I changed the slots to
AMAZON.SearchQuery
, which is roughly equivalent toAMAZON.LITERAL
, but a wiser move would be to create a custom entity type for shows. In it's simplest form, the type could be hard-coded with an entry to represent all NFJS events (e.g., "Northern Virginia Software Symposium", "Lone Star Software Symposium", "Progressive Web Experience") as well as synonyms for each of those (e.g., "Reston", "Dallas", "Clearwater").That would work until a new NFJS event is created. Suppose that we decide to do an Australian tour, there would be no entries for Sydney, Melbourne, etc, so the interaction model would need to be updated to include the new events and the skill republished. Instead, it might be wiser still to create a custom type for shows, but make it a dynamic entity (see https://developer.amazon.com/docs/custom-skills/use-dynamic-entities-for-customized-interactions.html) which is populated from actual show data. Then it would be flexible enough to support any new shows that are introduced.
The text was updated successfully, but these errors were encountered: