Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.w3.org/2007/08/mmi-arch/topics.html below:

List of issues and requirements raised during the workshop

Note. Each section heading has a format of:
"Category of the issues [Experts who are interested in the issues]"

• How to coordinate specifications — Primer doc for authors?
  • Authoring Note? or something else? (e.g. glossary)
  • not only "(X)HTML and VoiceXML" but also "SVG and InkML"
• Modality component specific grammar
• How to author applications (need more standards)
• Synchronization of multiple modality (using EMMA?)
• Error handling
• Possible use case: ATM in foreign countries

• Latency caused by serverside Interaction Management
• How to integreate additional functionalities to browsers
• Fusion/fission of data from multiple modalities
• How to handle device capability information
  • Publishing device capability by each modality component e.g. PlayAudio
  • Device capability e.g. DCCI
  • Ontology of device capability
• Standard name for Input/Output e.g. motion
• Higer level language than SCXML
• Encapsulation and tight/loose coupling

• APIs for the Architecture
  • life-cycle events+EMMA?
  • light weight APIs?
  • or something more/other than above two?
• Integrating InkML into MMI Architecture

• Accessibility: usability depending on user, environment; timeout
  • caused by Authoring issue?
• Latency caused by serverside Interaction Management
• Error handling
• User information/app cotext: how to store/query
• Multiple users

• Current IM is too big... What the role of IM should be then?
• Application specific management
• Message routing
• Direct communication between Modality Components

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.3