Messaging API lacks definition

[Jacky Alciné]

Wintermute's Messaging API needs to be fully defined for the milestone that this bug targets at. More information can be found and produced at http://www.thesii.org/wiki/Wintermute:Techbase:Projects/Messaging.

[Colby (cbrownlinux)]

I began adding goals and stuff just so we sort of have an idea of what to do, but most of what I put up there was ambiguous and generic, so if someone could look over it and help add stuff?

[Jacky Alciné (jackyalcine)]

Wow, it's very good though, but here's a few things:

--> Speech-to-speech dialog (Speech-to-text and text-to-speech plugin?)
That's handled by the Voice API, no need to worry about that.

--> Video support- Perhaps not only facial identification, but also
ability to recognize objects?
That's also handled by the Vision API, based on
https://www.github.com/jalcine/OpenTLD. When it's more stable to push
into Winty as a plug-in, I'll try (but everyone's free to try to do
so).

--> Mobile messaging API for on-the-go queries (Will need to change to
Java for Android development)

Well, here, we'd need a means of having Wintermute communicate
swiftly. Perhaps a messaging daemon of sorts for this and pass
communication information via XML-RPC?

--> Speech/voice recognition
Voice API :D

--> Ontology/Reasoning skills (POSSIBLY separate API, still being discussed)
Yeah, we wouldn't want to bloat one API and make it heavy. United we
stand, divided we stand.

--
Jacky Alcine
Blog <http://jackyalcine.co.cc/> | Launchpad<https://launchpad.net/~jackyalcine>