-
Notifications
You must be signed in to change notification settings - Fork 3
Add Recognition-Timeout as an Input attribute #95
Conversation
@@ -35,6 +35,12 @@ | |||
<uri>http://voxeolabs.com</uri> | |||
</author> | |||
<revision> | |||
<version>0.4</version> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll bump the version on submission to the XSF. There are other changes that need submitting and I'm overdue on a batch update.
It's also necessary to add this to the schema for a full specification. |
Changes made minus the "schema"; I don't understand what you mean by "add this to the schema". |
gotcha. thanks |
<attribute name="recognition-timeout" type="core:timeoutType" use="optional" default="-1"> | ||
<annotation> | ||
<documentation> | ||
Indicates the time (in seconds) alloted to match speech input before triggering a Nomatch completion. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other places in the specification [such as the INPUT element, and the RECORD element) reference milliseconds for timeouts. I'd suggest we need to be consistent. Plus, milliseconds is probably more appropriate when dealing with small values of time such as these kinds of timeouts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I only chose seconds rather than milliseconds since that's how MRCP describes the setting. If we feel strongly, it's OK by me to change this to milliseconds.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The priority is for Rayo to be self-consistent rather than consistent with other specs.
@benlangfeld @bklang changed to milliseconds as requested |
Could you explain how this is different from the initial-timeout already specified? |
|
Could that be clarified in the spec itself? |
Add Recognition-Timeout as an Input attribute
Thanks @Jared-Prime. This will be included in the next version of the Rayo spec. I'll prepare and submit that to the XSF today. |
Submitted to the XSF. Will post here when I receive confirmation of publication of Rayo v0.5 |
Published by the XSF: http://xmpp.org/extensions/xep-0327.html |
Update to Rayo protocol to add support for
Recognition-Timeout
MRCP header in support of Punchblock Pull Request 228 .