Well, that's tricky. Because perceptual processing is data-intensive, using standard but bloated representations like SUO-KIF or XML (yes I know the former is semantic whereas the latter is syntactic, but both tend to be bloated) is a bad idea for real-time interlinking btw perceptual and cognitive subsystems. I'd say we need an object-oriented structure wherein, to integrate the sensory system with a cognitive system, one creates a special subclass of some "sensory-cognitive I/O" object, which inputs/outputs knowledge in a format that's natural for the cognitive system in question.
Ease of integration with Windows programs isn't at the forefront of my own mind since Novamente is a Linux system ;-) ben > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Yan King Yin > Sent: Friday, October 15, 2004 3:51 AM > To: [EMAIL PROTECTED] > Subject: RE: [agi] Sensory Front-End: which API? > > > > I forgot to ask: what would be a good programming interface to > use? I mean for the visual module to communicate with the AGI > module? > > I can code in Visual C++ or C#, but I want to make the frontend > the easiest to integrate with other programs (mainly for Windows). > I think Linux and others will be handled separately. > > YKY > > -- > _______________________________________________ > Find what you are looking for with the Lycos Yellow Pages > http://r.lycos.com/r/yp_emailfooter/http://yellowpages.lycos.com/d > efault.asp?SRC=lycos10 > > ------- > To unsubscribe, change your address, or temporarily deactivate > your subscription, > please go to http://v2.listbox.com/member/[EMAIL PROTECTED] > > ------- To unsubscribe, change your address, or temporarily deactivate your subscription, please go to http://v2.listbox.com/member/[EMAIL PROTECTED]
