Subject: Re: [speechsc] unsupported language errors do not indicate theunsupported language

From: "Dave Burke" <[email-masked]>
Date: Sun, 2 Jul 2006 22:44:28 +0100

I suppose Completion-Reason could be used for a non-machine processable result. I'm in favour of an Unsupported-Language header field being added. Obviously applies to both the speech synthesiser and speech recogniser resources. 

Dave
  ----- Original Message ----- 
  From: Andrew Wahbe 
  To: IETF SPEECHSC (E-mail) 
  Sent: Thursday, June 29, 2006 3:21 PM
  Subject: [speechsc] unsupported language errors do not indicate theunsupported language

  Most of the resource types provide an "unsupported-language" completion-cause code but there doesn't seem to be any way to indicate what language(s) were not supported.

  Options here could be re-using the speech-language header for this, adding a new "unsupported-language" header or defining a content type (as discussed for failed URIs) that cause describe what went wrong with the request.

------------------------------------------------------------------------------

  _______________________________________________
  Speechsc mailing list
  [email-masked]
  https://www1.ietf.org/mailman/listinfo/speechsc
_______________________________________________
Speechsc mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/speechsc