Add Recognition-Timeout as an Input attribute

[Jared-Prime]

Update to Rayo protocol to add support for Recognition-Timeout MRCP header in support of Punchblock Pull Request 228 .

[benlangfeld]

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.

[benlangfeld]

It's also necessary to add this to the schema for a full specification.

[Jared-Prime]

Changes made minus the "schema"; I don't understand what you mean by "add this to the schema".

[benlangfeld]

Here: https://github.com/Jared-Prime/xmpp/blob/feature/rayo/extensions/xep-0327.xml#L3947-L3960

[Jared-Prime]

gotcha. thanks

[bklang]

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.

[Jared-Prime]

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.

[benlangfeld]

The priority is for Rayo to be self-consistent rather than consistent with other specs.

[Jared-Prime]

@benlangfeld @bklang changed to milliseconds as requested

[benlangfeld]

Could you explain how this is different from the initial-timeout already specified?

[Jared-Prime]

intitial-timeout states how long to wait for speech before timing out.
recognition-timeout states, after speech has begun, how many more seconds
of input to allow prior to determining a positive match.

[benlangfeld]

Could that be clarified in the spec itself?

[benlangfeld]

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.

[benlangfeld]

Submitted to the XSF. Will post here when I receive confirmation of publication of Rayo v0.5

[benlangfeld]

Published by the XSF: http://xmpp.org/extensions/xep-0327.html