Open johnataylor opened 6 years ago
@tellarin, should we address this one?
This is lower priority for now. And the initial implementation would need a config flag (or resolution policy) to toggle between the old value representation and the new one.
Recognizing an utterance such as 'fifty percent' as a percentage value is great but it would be more helpful to client code if the resolution was to a floating point value.
Specifically: an utterance such as 'fifty percent' results in: "resolution": { "value": "50%" },
Given the type has been correctly identified as percentage it would be better for the client code to receive a floating point number.
This would also fit more naturally with NumberFormat where the client could use code like this:
Which would assume obj.value to be 0.5 for 50%