<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"> 
<channel>
<title>DAISY Requirements Gathering Feed for posts, reviews and comments</title>
<description>Ordered by most recent comments</description>
<link>http://www.daisy.org/z3986/requirements/</link>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=3</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=3</guid>
<title>(R3) Develop Methods to Provide Interactive books (workbooks)</title>
<pubDate>2008-10-01 05:02:56</pubDate>
<description>This requirement is very important for our (The Open University) students in Higher Education; the ability to &#039;copy and paste&#039; from documents considerably improves the accessiblity of our &#039;supported open learning&#039; teaching method ie, it helps students outside the spectrum of print-disability by facilitating writing for students who have difficulty in using a keyboard or pen etc.

By way of background, during the last 10 years, we have provided course materials to our students in the form of an DTB product (called &#039;ReadOut&#039;)that we developed in-house. ReadOut provides the copy and paste feature and losing this option for students is something that concerns us in our current migration to DAISY.</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=89</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=89</guid>
<title>(R89) Functional and extensible metadata</title>
<pubDate>2008-04-21 21:08:40</pubDate>
<description>During the April, 2008 Z3986 f-t-f Committee meeting in Palo Alto, there was a side discussion about Onix.  No decision about whether it has immediate relevance to DAISY was made; however, I document the reference link here for possible future reference:

 http://www.editeur.org/onixfiles2.1/prodinf%202.1.html</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=18</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=18</guid>
<title>(R18) Implement Ruby Annotations via an Extension</title>
<pubDate>2008-04-15 23:11:12</pubDate>
<description>Offical textbooks for compulsory education in print has vertically written text with Ruby in Japan. There are students with Dyslexia who require exact same visual presentation of the textbooks on screen with synchronized narration. They are looking forward to the support for Ruby in DAISY Next.</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=81</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=81</guid>
<title>(R81) Video in DAISY in order to play back synchronised text and Sign Language</title>
<pubDate>2008-04-15 22:51:18</pubDate>
<description>I fully endorse Patric&#039;s proposal and recommend to establish a close collaboration link between DAISY, Swedish SIT and other interested parties to clearly identify use cases and solutions to support video captions and sign languages for DAISY next with special attention to DAISY Profile of SMIL 3.0</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=47</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=47</guid>
<title>(R47) Support of Sign Language</title>
<pubDate>2008-04-15 22:36:41</pubDate>
<description>First of all, reading difficulty issues of conventional printed books among deaf and hearing impaired people need to be recognized. I believe that deaf community requires sign language support of DAISY books.
Secondly, in the ageing society, there are increasing number of deaf-blind people who require equal access to information, knowledge and communications. Just think about an evacuation manual for fire, flood and Tsunami. Access to those manual is crucial for active social life with security, safety and dignity. Evacuation scenario need to be developed with full participation of people with disabilities including deaf, blind and deaf-blind individuals in the community. 
Thirdly, both Braille and tactile sign languages need to be promoted to support deaf-blind people. Since vision loss and hearing loss are in many cases age concerned, current blind people as well as deaf people are threatened by far higher potential to become deaf-blind. On the other hand, we are finding the best c</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=2</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=2</guid>
<title>(R2) References to Bible Verses</title>
<pubDate>2008-04-13 19:15:40</pubDate>
<description>Note this reference that was cited in an essay distributed to the ATHEN mailing list by Bob Martinengo.

See:

http://www.bibletechnologies.net/

The site indicates that:
"The Open Scripture Information Standard (OSIS) is an XML schema for marking up scripture
and related text, part of an "open scripture" initiative composed of translators,
publishers, scholars, software manufacturers, and technical experts who are coordinated
by the Bible Technologies Group."</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=39</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=39</guid>
<title>(R39) Add ranges to navigation nodes</title>
<pubDate>2008-04-13 13:31:09</pubDate>
<description>If we use semantics (e.g. the "role" attribute) on SMIL time containers, then what you suggested is a good approach.  Otherwise you couldn&#039;t be sure that the enclosing seq was a section.</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=82</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=82</guid>
<title>(R82) Consider AJAX as an Approach to Support Content Interactivity</title>
<pubDate>2008-04-08 18:10:49</pubDate>
<description>While the Committee may not choose to focus on Javascript, much less a specific library, I thought I&#039;d make a note of this link, in the event that this work may inform the Committee&#039;s thinking.  Here is the accessibility information on DoJo:
http://www.dojotoolkit.org/book/dojo-book-0-4/part-8-internationalization-and-accessiblity/accessibility-0</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=64</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=64</guid>
<title>(R64) Phonetic pronunciation per book</title>
<pubDate>2008-04-08 17:15:55</pubDate>
<description>There was an offline discussion regarding the idea of a "render me as" element.  The Committee may wish to consider this idea.

More specifically, the "render me as" element could address, for example, abbreviations, such as "St." - is it Street or Saint, "Dr." is it doctor or drive?

It may possibly be used for words that are for example homonyms or homophones if context might affect how the sentence is rendered.

This would basically be an element that gives direction for the way in which words should be rendered with synthetic speech.</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
<item>
<link>http://www.daisy.org/z3986/requirements/detail.php?i=82</link>
<guid isPermaLink="true">http://www.daisy.org/z3986/requirements/detail.php?i=82</guid>
<title>(R82) Consider AJAX as an Approach to Support Content Interactivity</title>
<pubDate>2008-04-04 01:42:24</pubDate>
<description>Note also that SMIL 3.0 has a new State module (see http://www.w3.org/TR/2008/CR-SMIL3-20080115/smil-state.html) that can be used to bring interactivity in a more declarative way. This State functionality is also included in the SMIL 3.0 DAISY Profile (see http://www.w3.org/TR/2008/CR-SMIL3-20080115/smil-daisy-profile.html)</description>
<comments>http://www.daisy.org/z3986/requirements/detail.php?i=#Comments</comments>
</item>
</channel>
</rss>