Speech - SASDK

[BrewskiAtBellSouth]

Is it my imagination or is the stuff in the SASDK overly complex? For
example, let's say I'd like to have a one page web application where I enter
a name into a text box and have the application read the name back to me when
I click a button on the page ("Hello World" for SASDK). Seems like the prompt
control would be ideal for this ... except that the <InlineContent> tag is
ReadOnly. ReadOnly?!? Am I expected to build a grammar dynamically or
construct an HTML stream on the fly just to have a page say, "Hi, Bob"?
Imagine if humans had to speak "ReadOnly" ...

[W.G. Ryan MVP]

Actually, I don't think it's that complex in and of itself to get running -
but building large scale speech enabled apps can be.

Your right about the ReadOnly property but I don't think a grammar is the
way to go about doing it. Are you going to use Speech Server as the back end
or are you just using the SALT tags?
"BrewskiAtBellSouth" <Br****************@discussions.microsoft.com> wrote in
message news:46**********************************@microsof t.com...

Is it my imagination or is the stuff in the SASDK overly complex? For
example, let's say I'd like to have a one page web application where I
enter
a name into a text box and have the application read the name back to me
when
I click a button on the page ("Hello World" for SASDK). Seems like the
prompt
control would be ideal for this ... except that the <InlineContent> tag is
ReadOnly. ReadOnly?!? Am I expected to build a grammar dynamically or
construct an HTML stream on the fly just to have a page say, "Hi, Bob"?
Imagine if humans had to speak "ReadOnly" ...

[BrewskiAtBellSouth]

I can imagine growing into something of a SpeechServer app. But initially I'd
simply like to use the controls provided with the SASDK (which are just
wrappers for SALT, after all) to make a web application more personable; "Hi
Bob" or "Hi Mary" instead of "Hi Human". The implication being that I would
need to build the <InlineContent> contents <grin> "on-the-fly". If the only
thing the Prompt control/tag in SASDK can do is read back pre-defined
verbage, that's a serious limitation IHMO. -BK

"W.G. Ryan MVP" wrote:

Actually, I don't think it's that complex in and of itself to get running -
but building large scale speech enabled apps can be.

Your right about the ReadOnly property but I don't think a grammar is the
way to go about doing it. Are you going to use Speech Server as the back end
or are you just using the SALT tags?
"BrewskiAtBellSouth" <Br****************@discussions.microsoft.com> wrote in
message news:46**********************************@microsof t.com...

Is it my imagination or is the stuff in the SASDK overly complex? For
example, let's say I'd like to have a one page web application where I
enter
a name into a text box and have the application read the name back to me
when
I click a button on the page ("Hello World" for SASDK). Seems like the
prompt
control would be ideal for this ... except that the <InlineContent> tag is
ReadOnly. ReadOnly?!? Am I expected to build a grammar dynamically or
construct an HTML stream on the fly just to have a page say, "Hi, Bob"?
Imagine if humans had to speak "ReadOnly" ...

[W.G. Ryan MVP]

I'm a lot more familair with Speech Server than just using the tags, but
AFAIK, the prompt won't let you do what you want. There is a speech
server/speech sdk newsgroup though (let me find the link and hopefully
someone can point you in the right direction using just the tags) and you
may want to run this by casey chesnut at www.brains-n-brawn.com ... he's one
of the more impressive minds in this area.
"BrewskiAtBellSouth" <Br****************@discussions.microsoft.com> wrote in
message news:3C**********************************@microsof t.com...

I can imagine growing into something of a SpeechServer app. But initially
I'd
simply like to use the controls provided with the SASDK (which are just
wrappers for SALT, after all) to make a web application more personable;
"Hi
Bob" or "Hi Mary" instead of "Hi Human". The implication being that I
would
need to build the <InlineContent> contents <grin> "on-the-fly". If the
only
thing the Prompt control/tag in SASDK can do is read back pre-defined
verbage, that's a serious limitation IHMO. -BK

"W.G. Ryan MVP" wrote:

Actually, I don't think it's that complex in and of itself to get
running -
but building large scale speech enabled apps can be.

Your right about the ReadOnly property but I don't think a grammar is the
way to go about doing it. Are you going to use Speech Server as the back
end
or are you just using the SALT tags?
"BrewskiAtBellSouth" <Br****************@discussions.microsoft.com> wrote
in
message news:46**********************************@microsof t.com...

> Is it my imagination or is the stuff in the SASDK overly complex? For
> example, let's say I'd like to have a one page web application where I
> enter
> a name into a text box and have the application read the name back to
> me
> when
> I click a button on the page ("Hello World" for SASDK). Seems like the
> prompt
> control would be ideal for this ... except that the <InlineContent> tag
> is
> ReadOnly. ReadOnly?!? Am I expected to build a grammar dynamically or
> construct an HTML stream on the fly just to have a page say, "Hi, Bob"?
> Imagine if humans had to speak "ReadOnly" ...

[BrewskiAtBellSouth]

Thx!

"W.G. Ryan MVP" wrote:

I'm a lot more familair with Speech Server than just using the tags, but
AFAIK, the prompt won't let you do what you want. There is a speech
server/speech sdk newsgroup though (let me find the link and hopefully
someone can point you in the right direction using just the tags) and you
may want to run this by casey chesnut at www.brains-n-brawn.com ... he's one
of the more impressive minds in this area.
"BrewskiAtBellSouth" <Br****************@discussions.microsoft.com> wrote in
message news:3C**********************************@microsof t.com...

I can imagine growing into something of a SpeechServer app. But initially
I'd
simply like to use the controls provided with the SASDK (which are just
wrappers for SALT, after all) to make a web application more personable;
"Hi
Bob" or "Hi Mary" instead of "Hi Human". The implication being that I
would
need to build the <InlineContent> contents <grin> "on-the-fly". If the
only
thing the Prompt control/tag in SASDK can do is read back pre-defined
verbage, that's a serious limitation IHMO. -BK

"W.G. Ryan MVP" wrote:

Actually, I don't think it's that complex in and of itself to get
running -
but building large scale speech enabled apps can be.

Your right about the ReadOnly property but I don't think a grammar is the
way to go about doing it. Are you going to use Speech Server as the back
end
or are you just using the SALT tags?
"BrewskiAtBellSouth" <Br****************@discussions.microsoft.com> wrote
in
message news:46**********************************@microsof t.com...
> Is it my imagination or is the stuff in the SASDK overly complex? For
> example, let's say I'd like to have a one page web application where I
> enter
> a name into a text box and have the application read the name back to
> me
> when
> I click a button on the page ("Hello World" for SASDK). Seems like the
> prompt
> control would be ideal for this ... except that the <InlineContent> tag
> is
> ReadOnly. ReadOnly?!? Am I expected to build a grammar dynamically or
> construct an HTML stream on the fly just to have a page say, "Hi, Bob"?
> Imagine if humans had to speak "ReadOnly" ...