You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by Stu Robertson <sr...@nvisia.com> on 2005/06/13 22:23:03 UTC

RDC: Plan B for getting Nuance to work with RDCs

Hmm.  I'm starting to suspect that nuance folks mainly use GSL.  I'm  
still hoping for some help from the newsgroup posts I've made to  
voxeo and bevocal, but I'm not counting on it.

If we're likely to have separate grammars I'm considering just using  
GSL for nuance.  RDCs still abstract the app from the grammars, and  
hopefully longer term we can just use SRGS for both.  It's a pain  
though, since we'll need to have internationalization for RDCs to be  
widely adopted, and GSL would double that work.

Anyway, what do you think about that?  And do you know where I can  
find any ready-to-go digit, alpha and alphanum gsl grammars?  Have  
you or anyone you worked with done enough with GSL to create  
something quickly?  I'm starting to google right now, but if you have  
any resources on this, I'd appreciate it.

I agree it'd be fine to have the grammar-type/platform specified in  
an init parm.  The next question is where to put the grammars.  What  
about creating two sub dirs under .grammar, one for srgs and one for  
gsl?  The servlet would use the init parm to figure out which to  
use.  There's the issue of file name suffixes of course.  If you  
think this is a reasonable approach, I'll take a stab at the  
necessary changes.

Hopefully somebody will help us get nuance srgs to work and make the  
GSL part unnecessary...though we'd still probably need the subdirs  
for grammars.

Stu

---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org


Re: RDC: Plan B for getting Nuance to work with RDCs

Posted by Rahul P Akolkar <ak...@us.ibm.com>.
Stu Robertson <sr...@nvisia.com> wrote on 06/13/2005 11:59:22 PM:
<snip/>
>  We are still unable to test 
> anything until 1) IBM's 6.0 Toolkit comes out for real (we can't get 
> the test environment/simulator to work reliably at all) or 2) we get 
> RDCs working on a Nuance platform, for which there are free 
> development environments readily available.  The latter will make a 
> great wiki addition once we get it working.

It will be a great addition now :-) Really, if you're thinking about it, I 
suggest you go right ahead. You have the RDCs with the simpler grammars 
going on that dev platform, you can write using those examples. That way 
anyone interested in trying out RDCs using free dev environments will have 
a how-to page. I've created a TryingOut item at the end of the RDC 
tutorials list here [ 
http://wiki.apache.org/jakarta-taglibs/ReusableDialogComponents/Tutorials 
]. I think thats a good place on the wiki to put your tutorial whenever 
you're ready.

> As for using different resource bundles to support different platform 
> grammars, will that work well if we also have separate grammars for 
> internationalization?

Yes, grammar URIs are localized resources (so are prompts, so are xml:lang 
attributes).

-Rahul

Re: RDC: Plan B for getting Nuance to work with RDCs

Posted by Stu Robertson <sr...@nvisia.com>.
I would really like to find out more about Steve's success with the  
grammar listed in his post.  Whenever I try using CDATA in a tag, I  
get a compile error in the grammar, including when I use the grammar  
he mentioned worked for him.  This is in the current development  
environment of both community.voxeo.com and also cafe.bevocal.com.

I'm certainly at a dead end with this for now, so I guess I'll give  
the group a few days to see what they can turn up.  I won't redo the  
grammars unless we need to, but I was really hoping to be able to get  
past the compatibility issues by now.  We are still unable to test  
anything until 1) IBM's 6.0 Toolkit comes out for real (we can't get  
the test environment/simulator to work reliably at all) or 2) we get  
RDCs working on a Nuance platform, for which there are free  
development environments readily available.  The latter will make a  
great wiki addition once we get it working.

As for deployment plans, we have both IBM's voice response/server and  
a Nortel platform in house.  Nortel uses Nuance grammars.

As for using different resource bundles to support different platform  
grammars, will that work well if we also have separate grammars for  
internationalization?  I need to look at the RDC implementation a bit  
more, but that's the first question that comes to mind.

G'night  :-)

Stu
On Jun 13, 2005, at 4:23 PM, Rahul P Akolkar wrote:

> <detour>Steve, if you're listening, can you give Stu some details  
> about
> your Nuance setup?</detour>
>
> Stu Robertson <sr...@nvisia.com> wrote on 06/13/2005 04:23:03 PM:
>
>> Hmm.  I'm starting to suspect that nuance folks mainly use GSL.  I'm
>> still hoping for some help from the newsgroup posts I've made to
>> voxeo and bevocal, but I'm not counting on it.
>>
>
> Give that a day or two Stu. I dug up what Steve was saying here [
> http://marc.theaimsgroup.com/?l=taglibs- 
> dev&m=111530442607124&w=2 ], and
> whatever variant of the Nuance platform he was using seems to  
> process the
> SI correctly. Are you sure the test environment you're using is upto
> speed? How long will you be deploying on this setup in the future? I
> suspect at some time, you'll move to an in-house arrangement? If so, I
> wouldn't spend too much time on re-doing the grammars, I'd save the
> efforts for the real deal. Just my two cents worth (but, based on  
> personal
> experience).
>
>
>> If we're likely to have separate grammars I'm considering just using
>> GSL for nuance.  RDCs still abstract the app from the grammars, and
>> hopefully longer term we can just use SRGS for both.  It's a pain
>> though, since we'll need to have internationalization for RDCs to be
>> widely adopted, and GSL would double that work.
>>
>
> Agreed, cross-products are no joy. Thankfully, this is search  
> replace type
> of authoring, if it comes to that.
>
>
>> I agree it'd be fine to have the grammar-type/platform specified in
>> an init parm.  The next question is where to put the grammars.  What
>> about creating two sub dirs under .grammar, one for srgs and one for
>> gsl?  The servlet would use the init parm to figure out which to
>> use.  There's the issue of file name suffixes of course.  If you
>> think this is a reasonable approach, I'll take a stab at the
>> necessary changes.
>>
>
> Sure, new directory is a good idea. But the directory structure or  
> suffix
> has nothing to do with what grammar is picked up, it will be the  
> resource
> bundle that dictates this. The directory or suffix will really be  
> just a
> visual cue for developers.
>
> For example, RDCs pick up prompts and grammars for en_US locale  
> from here
> [
> http://cvs.apache.org/viewcvs.cgi/jakarta-taglibs-sandbox/rdc/src/ 
> org/apache/taglibs/rdc/resources/RDCBundle_en_US.properties? 
> view=markup
> ]. Lets have a locale variant called Nuance, and have that resource  
> bundle
> point to the correct grammars (AFAIK, variants can be made up). A  
> brief
> read on the current internationalization support in RDCs is here [
> http://wiki.apache.org/jakarta-taglibs/ReusableDialogComponents/ 
> Tutorials/I18N
> ].
>
>
>> Hopefully somebody will help us get nuance srgs to work and make the
>> GSL part unnecessary...though we'd still probably need the subdirs
>> for grammars.
>>
>
> Works for me, got nothing against arranging resources  
> systematically ;-)
>
> -Rahul
>

---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org


Re: RDC: Plan B for getting Nuance to work with RDCs

Posted by Rahul P Akolkar <ak...@us.ibm.com>.
<detour>Steve, if you're listening, can you give Stu some details about 
your Nuance setup?</detour>

Stu Robertson <sr...@nvisia.com> wrote on 06/13/2005 04:23:03 PM:
> Hmm.  I'm starting to suspect that nuance folks mainly use GSL.  I'm 
> still hoping for some help from the newsgroup posts I've made to 
> voxeo and bevocal, but I'm not counting on it.

Give that a day or two Stu. I dug up what Steve was saying here [ 
http://marc.theaimsgroup.com/?l=taglibs-dev&m=111530442607124&w=2 ], and 
whatever variant of the Nuance platform he was using seems to process the 
SI correctly. Are you sure the test environment you're using is upto 
speed? How long will you be deploying on this setup in the future? I 
suspect at some time, you'll move to an in-house arrangement? If so, I 
wouldn't spend too much time on re-doing the grammars, I'd save the 
efforts for the real deal. Just my two cents worth (but, based on personal 
experience).

> If we're likely to have separate grammars I'm considering just using 
> GSL for nuance.  RDCs still abstract the app from the grammars, and 
> hopefully longer term we can just use SRGS for both.  It's a pain 
> though, since we'll need to have internationalization for RDCs to be 
> widely adopted, and GSL would double that work.

Agreed, cross-products are no joy. Thankfully, this is search replace type 
of authoring, if it comes to that.
 
> I agree it'd be fine to have the grammar-type/platform specified in 
> an init parm.  The next question is where to put the grammars.  What 
> about creating two sub dirs under .grammar, one for srgs and one for 
> gsl?  The servlet would use the init parm to figure out which to 
> use.  There's the issue of file name suffixes of course.  If you 
> think this is a reasonable approach, I'll take a stab at the 
> necessary changes.

Sure, new directory is a good idea. But the directory structure or suffix 
has nothing to do with what grammar is picked up, it will be the resource 
bundle that dictates this. The directory or suffix will really be just a 
visual cue for developers.

For example, RDCs pick up prompts and grammars for en_US locale from here 
[ 
http://cvs.apache.org/viewcvs.cgi/jakarta-taglibs-sandbox/rdc/src/org/apache/taglibs/rdc/resources/RDCBundle_en_US.properties?view=markup 
]. Lets have a locale variant called Nuance, and have that resource bundle 
point to the correct grammars (AFAIK, variants can be made up). A brief 
read on the current internationalization support in RDCs is here [ 
http://wiki.apache.org/jakarta-taglibs/ReusableDialogComponents/Tutorials/I18N 
].
 
> Hopefully somebody will help us get nuance srgs to work and make the 
> GSL part unnecessary...though we'd still probably need the subdirs 
> for grammars.

Works for me, got nothing against arranging resources systematically ;-)

-Rahul