[alicebot-archcomm] RE: [alicebot-general] 3D FACEs

[Conan Callen]

Yea, I agree, what I brought up in my orginal post is implementation specific.
Sometimes I get confused about when people are discussing AIML or the
implementation of program B. Being that I have a few c++ implementations
of Aiml intrepreters, I tend to get focused on the spec and where
its going rather then a specific implementation.

Conan

> Conan Callen
wrote: >
> > I agree with Kims idea below.
> >
> > The AIML spec should define how different
> > systems like facial sythesis can be access via a consistant interface and
> > how the client can inform the server of its requirements & capibilities.
> > The reference model (Alice) would then implement these interfaces and the
> > drivers for a selection of facial experession engines, to demonstrate how
> > to build new drivers (integrate a new engine).
>
> The ALICE portion should just define the text in, text out and that's it.  If everything else is event driven or
> plugable it should work in *some* type of API fashion.  Lets say even if it is tag based (<event>) or something
> that works internally only telling you that an event has been passed, it would work for many things (Serial,
> TTS, whatever).
>
> You can then assign it by saying that there are SpeechEvents, SerialEvents, PluginEvents, etc, etc.  In ALICE
> per se its either you are returning something or returning nothing.  Very simple.  If we can add a return
> nothing, but really do something (much like how <think> works) it should work.  Its wierd some people post AIML
> but rarely use <think> and in my thinking you should or seem to have 1 <think> per category anyways.
>
> - Jon
>
> _______________________________________________
> alicebot-archcomm mailing list
> alicebot-archcomm@list.alicebot.org
> http://list.alicebot.org/mailman/listinfo.cgi/alicebot-archcomm
>