The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Schema Question


  • Subject: Re: Schema Question
  • From: Stuart Booth
  • Date: Mon, 22 Dec 2003 23:21:00 +0000

On Mon, 22 Dec 2003 16:12:15 -0500, "Sullivan, Glenn"
<<a
href="/group/xAP_developer/post?postID=z7PxJEYnMK2jE3ev84-QWDRtdcsBvHWeQ68liVHZdEKIFEzvDv9XA2fNH3GTRpLAhEPlTam9X9BAREiRLlw">gsullivan@d...</a>>
wrote:

>I guess it just seems silly to send out two messages.

Indeed, redundant traffic.

> Can't I just create
>optional parameters in the TTS.Speak block in TTS.Basic, and then the
>"simpler" tts devices will ignore them? And then only have a
class called
>TTS.MSAgent for blocks like DefaultCharacter.Change, or Status.Request?

What sort of additional parameters were you thinking of here? My own
TTS app is incredibly basic. I don't think I've fired it up in a
looooong time so I can't even tell you what it did/does. ToDo list,
deeply lost somewhere...

Something I've been playing around with a little bit that has been
mentioned here before is that of class inheritance. I don't know what
the current thinking on this is though. These are just some ideas that
floated through my head.

Anyway, taking your example,

Class = TTS.Basic

TTS.Speak
{
Text=Speak these words of ultimate wisdom
}

Then 'derive' from this class and add further specialisation:

Class = TTS.Basic.MSAgent

TTS.Speak
{
Text=Words
}
TTS.Agent
{
Character=Trudy
}

A TTS.Basic capable app can pick out the things it knows and ignore
the rest. A MSAgent equipped app can cope with the additional data
that the basic app skipped over.

Or as even wilder alternative, how about inheriting the message block
too:

Class = TTS.Basic.MSAgent

TTS.Speak.Agent
{
Text=Words
Character=Trudy
}

There's quite an overhead in processing this kind of stuff on low
power devices however! So it's just a couple of alternatives to
consider.

Going back to your original plan, if the additional bits of optional
data are general enough, then why not stick them in your TTS.Basic as
you suggest. Are we thinking about different voices here? There are
several examples of additional optional data in basic level schema
that are often ignored.

S
--
Stuart Booth <<a
href="/group/xAP_developer/post?postID=jU4GGnqj5oK5uV7UMx3BgEN53Uer389QhmwXkeT0T7Y7oH_5U3V69rOXTkc4aMHnjMItnloFMuSL9gRNcCqiWg">stuart@x...</a>>
xAPFramework.net - a xAP software development framework for .net

<a href="http://www.xapautomation.org/";>http://www.xapautomation.org/</a>
<a href="http://www.xapframework.net/";>http://www.xapframework.net/</a>





xAP_Development Main Index | xAP_Development Thread Index | xAP_Development Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.