ZedDist Interactivity
From zedwiki
This is the landing page for the ZedDist Interactivity subgroup.
- Interactivity was identified as a requirement for ZedNext: ZedNext_Requirements_Taxonomy#Interactivity
- By November 9th, this subgroup will have defined what interactivity means and what its scope is for the ZedNext distribution format.
- Working group members: Marisa, Dennis, Josh, Kenny, Keith Creasy, Larry Skutchan, Boris
The group may ask the original contributors to the ZedNext requirements for additional input or clarification.
Among the first tasks for the group will be to analyze use cases (existing as well as new) and look at which features target which users. Then a reasonable set of features can be proposed for inclusion in the specification.
Contents |
Requirements
Forms and input
- Require these form controls TODO
- Submission/response mechanism needs to be defined OR hooks for inserting your own model need to be defined
- Need to support submission/response mechanism on all zeddist profile targets that the type of content is intended for.
- Accept the following types of user input (dependent on the playback environment):
- text
- audio
- video
- math equation
Annotations
- Annotations are: notes about a point or range in the book
- Annotations are: a list of global navigation points
- Export annotations
- Publish annotations
- Subscribe to someone else's annotations
General
- Fallback behavior for players that don't understand interactive content. Multiple output formats of ZedDist will let us be more selective about the intended device/environment for the content, but still we can expect some requirements for fallbacks.
- It should be possible to give the user feedback right away (immediately or after a section). This can be good for coaching.
- Extensible interactivity: send parts of the document (e.g. a math equation) to user agent plug-ins
Defining interactivity
Interactivity means ...
- Forms and responses
- User input
- Navigation
- Annotation
New ideas
Generic interactive navigation
- is it possible?
- what are the ways in which i can move around this structure
- what is the overall context?
- what operations are permitted on my current item?
By defining such a mechanism, we can extend interactivity to many different types of content.
However, it is possible that not all content will conform to this model. Is it better not to try and define an "API" for interactivity and instead set guidelines for interactive content extensions? E.g., if a publication has elements that will change based on user input, and that fall out of the scope of DAISY-defined interactivity, the user should be notified about the changing content using accessibility-compliant approach A, B, or C. The user should also be presented with their choices in a certain way. And, the user should be able to focus on only one option at a time. Etc etc .. probably reference WCAG.
Use cases
Math
- View an equation
- Hear the entire thing
- Hear each component
- Move by previous/next component
- Move into a component and expore its subcomponents
- Manipulate an equation
- Move a component from the left side to the right side or vice versa, via an operation (divide, subtract, etc)
- Enter a value for a variable
- Take the result from one equation and use it to substitute a component of another.
- Manipulate again (make a series of steps towards solving the equation)
- Use an equation or a component as a query string. E.g.:
- Graph the equation
- Look up a reference for the equation or component
End-user annotations
- Make a note (text, audio, video)
- The note should correspond to a point in the publication (a single point or a range)
- View the notes inline with the publication content
- View only the notes
- Organize the notes from many publications
- Link to the publication from a note
- Publish notes to a server
- Subscribe to someone else's notes
XForms/QTI Controls
ZedDist_Interactivity_XForms_/_QTI_Controls
Teleconference minutes
ZedDist_Interactivity_Telecon20091028
ZedDist_Interactivity_Telecon20091015
