Note: This meeting has not yet been held.
ACTION ITEMS ASSIGNED AT THE 2009/01/19 CALL:
Talking Points & Resources:
JS said that FlowML seems to be dead.
JS said MusicXML is a good candidate for an expert handler. It is being used across scoring apps. It seems very complete.
NS asked whether "play" is an action that needs to be considered in addition to navigation, speech, and braille.
JS and JT felt that isn't the province of the EH, but is the app's responsibility.
JT felt that navigation and level of detail were particularly difficult/interesting with music. How are interactions with the ML going to be indicated.
NS said that MathPlayer uses numbers to indicate where it is for synchronizing speech with display. This works because MathPlayer generates and interprets the ML and numbers.
JT felt that maintaining a separation between the EH and the app and communicating the position between them would be the hard part for the requirements.
NS said that an ML can be parsed and linearized in a standard fashion, and that number can be passed, or a pointer to the tree can be referenced.
JT felt that having a DOM is essential for navigation/interaction.
NS suggested maybe focusing on browser DOMs would be a good way to focus and start a discussion.
Action Item: NS to do his action item from the last meeting (see agenda)
JS said that as far as she could see, MusicXML is used only for file storage. It isn't embedded in web pages, etc.