ZedNext Requirements Taxonomy

From zedwiki

Contents 1 Notes 2 Pre-existing categories 3 Requirements Taxonomy Ideas Beyond the Categories that pre-exist in the Database 3.1 Supporting New Representations -- sign language and symbols 3.2 Use of and Support for Video 3.3 Interactivity 3.4 Potential to be Braille Related 3.5 Requests related to Paragraphs 3.6 Further Ease of Production from Single Source File 3.7 Use Cases that May Require Little or No Change to DAISY Standard 3.8 Use Cases that Might Make Good Reference Implementations 3.9 Establish a Single File Type 4 Requirements that should have notes or supplemental documents attached to them 4.1 NCX-related 4.2 Cataloguing and Metadata 4.3 Implementation of Role Attribute 4.4 Block and Inline 4.5 Issues with Nesting 4.6 Internationalization 4.7 Images and Their Descriptions 4.8 CSS-related 4.9 Highlighting 4.10 Namespaces 4.11 Compound Documents

Notes

• May 21, 2008 Version 3, Slight mods made in reviewing for preparation to send to GK
• April 7, 2008 Version 2, links updated for non-admin area KK
• April 1, 2008 J. Sutton, Version 1
• Notes about items that I apparently still need to enter as requirements:
  • I Need to enter additional Requirement Related to DOI.
  • Also, updates GK sent via email regarding outstanding issues have not been made, yet.
  • Also, I have some note about a requirement being needed about lists not being implemented correctly, but I will need to figure out who can help with that as I don't know where my note came from.
• KK: Need to do an analysis of ratings?
  • Generate a list, once items moved over to Wiki, based on most important to least?
  • Give a short paragraph or two summary as to how much rating was done so we can know how seriously submitters took it?

Pre-existing categories

• Audio
  • Consider adopting CSS and Aural CSS as components of DAISY fileset
    • This should also be here since it talks about Aural CSS, not just presentational. Database was not designed to provide for multiple categories.
• Content Types
• Navigation
• Other
• Presentation
• Usability

Requirements Taxonomy Ideas Beyond the Categories that pre-exist in the Database

Supporting New Representations -- sign language and symbols

• Support of Sign Language
• Video in DAISY in order to play back synchronised text and Sign Language
• Symbolic languages and DAISY

Use of and Support for Video

• Support of Sign Language
• Video in DAISY in order to play back synchronised text and Sign Language
• support video as content type
• modelling Interactive training material for disaster preparedness, video self
  • disabled as inappropriate, but might be a useful use case for demo/reference implementation

Interactivity

• • Possible need to retrieve details from Discussion on Tech-Dev. generally between March 27 -- April 1, 2008.
• Develop Methods to Provide Interactive books (workbooks)
• QTI (Question & Test Interoperability) Standard implementation
• Consider AJAX as an Approach to Support Content Interactivity
• modelling Interactive training material for disaster preparedness, video self
  • disabled as inappropriate, but might be a useful use case for demo/reference implementation
• Use the SMIL 3 DAISY Profile in the next DAISY Standard
• Support data entry forms

Potential to be Braille Related

• • Maybe this should be a sublist related to furthering ease of production from single source file.
  • Cross-check these against items that Matt Garrish submitted as most of his would relate to braille, and I cannot display by commenter in the current database, as far as I know.
• Streamline Braille production from DAISY as the Single Source
• Expand DTBook to Enrich the Content Model for the Table of Contents
• Textbox element needed
• Devise a Method to Handle Ambiguous Characters
• Implement a flexible solution for creating different output formats from DTBook

Requests related to Paragraphs

• Support for different types of paragraphs
• Introduce a separator element into DTBook

Further Ease of Production from Single Source File

• Implement a flexible solution for creating different output formats from DTBook
• Expand DTBook to Enrich the Content Model for the Table of Contents
• Textbox element needed
• Devise a Method to Handle Ambiguous Characters

Use Cases that May Require Little or No Change to DAISY Standard

Training in how to produce content and/or use production tools is what is required here. Usability Issue that is producer-dependent

• Provide Reliable Methods to Support Turning to a Page
  • worth noting even though it is disabled as inappropriate
• Change naming of Levels to specific navigation elements
  • I believe that this is a producer issue, but is there something to be done to make it easier for producers to add this kind of functionality if they wish?

Use Cases that Might Make Good Reference Implementations

• Interactive training material for disaster preparedness, video self-modeling
  • disabled as inappropriate, but might be a useful use case for demo/reference implementation

Establish a Single File Type

• • Possible need to retrieve discussion from Tech-Dev list
  • Two Requirements (and a third that is disabled) somewhat duplicate
• A single recognized DAISY file type
  • disabled as duplicate
• ZIP archive as directly supported DTB package format
• Single file distribution

Requirements that should have notes or supplemental documents attached to them

• • It may not be possible to make the supplemental docs publicly viewable on the Wiki.
• Add DTD Functionality to Support Production of Magazines, Leaflets, and Personal information
• Revision of DAISY DTBook DTD
• Make DAISY Specification Codec Agnostic

NCX-related

• • These two items are documented as related in R68.
• Separate NCX from Digital Talking Book spec
• Make NCX context and content agnostic

Cataloguing and Metadata

• Modify Content Model to Allow Sub-document Level Metadata
• Functional and extensible metadata
  • DOI Requirement, once I get it entered.

Implementation of Role Attribute

• • Note that this is documented in R59.
• Implement Role attribute to refine semantic meaning of elements
• Consider adopting ideas from XHTML 2
• keyword element
  • A possible use case for R59

Block and Inline

• Remove the Possibility of Having Block Elements in Inline Context
• Separate Block And Inline Elements

Issues with Nesting

• Address Potentially Obsolete Implementation of Nested Levels in DTBook
• Remove the Possibility of Nested Prodnotes

Internationalization

• Vertical text
• Consider adopting W3C ITS

Images and Their Descriptions

• Establish Clear and Consistent Methods for Including Image descriptions
• Devise a method to skip over image descriptions
• Freeze image while text scrolls
• Long Description

CSS-related

• Preserve Spatial Information of word positioning
• Consider adopting CSS and Aural CSS as components of DAISY fileset
• User controlled styling
• Textbox element needed
  • If defined, how would its appearance be controlled?
• Introduce a separator element into DTBook
  • If defined, how to control presentation?
• Control display/format needs
• Runtime customization of presentation

Highlighting

• Control Highlighting Display for End Users While They are Viewing the Book On Screen
• Support fluency through highlighting
• Word level highlighting

Namespaces

• Expand namespace support for extensions
• Establish a Namespace URI Change Policy
• Compound documents (multiple namespaces) for text content

Compound Documents

• A better way to define compound documents
• Compound documents (multiple namespaces) for text content