NS: PeteB, reply to your email queries? sent 2 queries to RichS "characteristics of device" and Rob at FreeSci "Expert handler and device attribute negotiation" on 21 July 2008
PB: Freedom Scientific thinks that it is a worthy effort, but doesn't have anyone to contribute to
JS: GW-Micro accepted idea at CSUN2008
NS: vendors reluctant why? technical issues?
PB: details of device AT uses - any other way to do it?
NS: currently ask for text and separate call for braille; when do that, AT has 2 additional things it is aware of and can pass info about devices through
NS: calls very device specific
PB: on each call or device configuration
NS: would be possible via a COM interface by setting state (braille device 40 chars) call would set to 40 char support; done for synchronized highlighting
GJR: localization -= AT should know what devices are known to it and available to it
NS: devices talking to sending out generic interface
JS: particular parameters AT would not know or do we need to push parameters upstream to handler?
NS: push upstream to handler - pushed in on handler specific calls, or is there a generic means of requesting information needed; callback interface to get more info for each specific device
PB: trying to think why AT would have problem handling query - going to be providing info one way or another
NS: conception of control - AT does not want to give up control because may not get it back
NS: give focus away, need means to get back
PB: will discuss callback with Glenn of Freedom Scientific
NS: cleanest solution
PB: what to ask for - tts, braille, how long braille display is -- strictly API?
NS: 2 answers: should just care about API (SAPI or SSML); would be nice to know engine (may not support all features of SAPI or SSML); don't envision happening
PB: invite Glenn to call?
NS: good thing to do - get info straight from the horse's mouth
PB: loosing focus - need to summarize where we are at?
NS: matter of available cycles
GJR: Requirements document as next step? help collate issues and form a roadmap for expert handlers
JS: logical next step
GJR: will start on a wiki page -- just like the Unified Use Cases development, which began as brainstorming page - not just requirements but identification of whom we need to query about requirements
ACTION GJR: set up Expert Handlers requirements wiki page
NS: attendance for next week?
PB: will miss next monday
JS: will be traveling to minnesota within the next 2 months but should be able to attend
NS: cancel 4 August 2008 call; no call 1 September 2008 (labor day)