Started working on the custom speech api #3
Conversation
|
As I haven't used the Speech API since 2012, I'd imagine that things have changed a bit. I'll review the code and see if it makes sense to make the modifications you recommended. I may also ping the good folks at AT&T to see if they have someone willing to be an active maintainer, since not using the API actively has left me with little context for this update. Thanks for your work on making the API and its Node wrapper better, either way! Michael Owens
|
I've started implementing the custom speech api.
Unfortunately the project I've been working on most likely wont use this anymore but I figure you might want this source code anyway.
It may seem that there are a lot changes here. Mostly I just made the quotation marks consistent throughout the JS file.
Something I've found wierd about this API is that you require a different access token for the custom speech and regular speech. This might become a consideration going forward cause currently you'd be instantiating two instances of watson-js in order to use functionality. It might be good to save the access token per scope.