wintermute-devel team mailing list archive
-
wintermute-devel team
-
Mailing list archive
-
Message #00476
Re: [Bug 897991] Re: Messaging API lacks definition
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>
--
You received this bug notification because you are a member of
Wintermute Developers, which is subscribed to Wintermute.
https://bugs.launchpad.net/bugs/897991
Title:
Messaging API lacks definition
Status in Wintermute:
Confirmed
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/wintermute/+bug/897991/+subscriptions
References