I have a skill that accepts an AMAZON.DATE slot and confirms the intent. This slot accepts a number of different values, like "tomorrow", "this weekend", or "this spring" (see all the different possibilities here). These relative/less precise dates result in slot values like "2017-W33-WE" (the weekend of week 33 in 2017). When these values appear in the confirmation dialog, Alexa speaks these values literally instead of repeating them the way the user spoke them.
Using the example above, Alexa says "The event will take place on twenty seventeen double-u thirty-three we". I would expect her to say "The event will take place this weekend", since this is what the user spoke.
Is there a way around this? I know I could move the confirmation logic into my Lambda function, instead of relying on the dialog model for slot validation/confirmation, but this would be quite a bit more work - the dialog model makes this kind of conversation very easy to implement.