Meeting minutes
interfaces
dirk: any questions about interfaces?
debbie: will look for typos
… then I can sent to mailing list
jim: should also send personal messages to colleagues
debbie: first send to mailing list, then to other colleagues after publication
Architecture v. 3 and requirements publication
dirk: publish requirements first and then update Architecture
jim: leave "voice or text"
3.1.11 need to clarify
dirk: could shift components to other layers, like having TTS on the client
dirk: let's move that up under "architecture" because it's more general than client
debbie: remove 3.1.3.8
… not a requirement
3.2.3.5 Core Data provider?
dirk: has been removed
dirk: just remove "core" from data provider
debbie: we can finalize this next week
possible reference implementation, need to restructure repository
dirk: should have one folder for each document
debbie: should make a folder for requirements
dirk: we have to update
… the links
dirk: debbie to change requirements and dirk to take care of the rest
debbie: will change the home page
dirk: will make a folder for code
… what language?
dirk: javascript or C++? Could create wrappers for, e.g. Python
… javascript for client, but Java for server
jim: ask people in industry to offer opinions
jim: ask SpeechTEK people to offer opinions
debbie: post on Linked in
jim: Project Voice
debbie: need to offer pros and cons of different languages
jim: need to get more people to know about this effort
… need some kind of marketing person