Z3986 Issues

Status:   Resolved (Future Direction)   Issue Type:   Specification

Issue Description:
In the NCX file, the dtb:maxPageNumber and dtb:totalPageCount metadata is required. They refer to the value attribute of pageTarget element. However, this value attribute is not required. In addition, ZedVal can only validate books that use the value attribute. Books that do not include the optional value attribute on the pageTarget element fail validation even though they they are valid. I suggest that either ZedVal be modified to validate such books or that the spec be updated to require the value attribute. Since this is either a spec or ZedVal issue, I am cross-posting it to the ZedVal tracker.

Resolution Description:
Clarify this in the next version of the standard since it would probably require extensive redesign. Markus summarized that this is a very messy part of the spec in terms of trying to build ZedVal and interpret exactly what is intended.

Status:   Resolved (Future Direction)   December 3, 2007   Issue Type:   Specification

Issue Description:
Introduce a block element named separator into DTBook. The separator can for example be used to separate two paragraphs from each other when there is a line (or something similar) between them in a printed book.

Resolution Description:
Entered as Future Requirement #25

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=25

Status:   Resolved (Future Direction)   June 4, 2008   Issue Type:   Other Documentation   Assigned To:   Kathy Kahl

Issue Description:
This is a follow-up to issue 155. Image: When the final XML viewed either in Internet Explorer 6.0 or in Book Wizard Reader 1.1.1.0, the images are not displayed correctly. List: Only bullets are appearing instead of styles like numeric, alpha and arabic defined in the XML file. Table: The final table alignment in the output is not looking good though the tagging is correct according to the specification. http://www.daisy.org/dtbook/misc/dtbook-css-compat.html css should be rewritten. Kathy to re-write it.

Resolution Description:
Add references to this (#196) and #155 to the Requirements database. Apparently this is relating to the problem of browsers not displaying images and tables correctly which is a monstrous browser problem, not specific to the DAISY Standard, nor is the CSS part of the Standard. There is already a future requirement to the spec to resolve distribution and rendering problems.

Status:   Resolved (Future Direction)   Issue Type:   Specification   Assigned To:   James Pritchett

Issue Description:
Section 16.1 of the spec (http://www.daisy.org/z3986/2005/z3986-2005.html#FileConform) defines a number of rules for DTB XML documents so that they can be correctly handled by non-validating XML processors. These rules include the explicit specification of attributes declared as #FIXED in the respective DTD, but does not mention #IMPLIED attributes with default values. This looks like an oversight.

Resolution Description:
If move to schema, problem would go away.

Status:   Resolved (Future Direction)   December 6, 2006   Issue Type:   Specification

Issue Description:
metadata is presumed to be document level. This is on occasion untrue. Feature request: that metadata (meta element currently) be allowed as children of lower level block elements. Suggest note, div provisionally.

Resolution Description:

The Zed committee felt that this issue should be addressed in the next issue of the spec.

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=24

Status:   Resolved (Future Direction)   November 3, 2006   Issue Type:   DTD   Assigned To:   issue triage team

Issue Description:
There is no element to capture name of the photographer or source of the table or image. Do we need to capture it as caption or need to add a element in DTD to capture the credit source?

Resolution Description:
A recommended work-around: use the element caption with a class attribute of credit.

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=23

Status:   Resolved (Future Direction)   September 22, 2006   Issue Type:   DTD   Assigned To:   George Kerscher

Issue Description:
Currently prodnote, pagenum, code, imggroup are elements which may be used either inline or as block elements. Propose that pagenum is the only viable element which rightly belongs in this class. The remainder require resolution, either by renaming for inline use, or content model change. Propose that this be addressed at the move to a schema language where we have more control over the content models.

Resolution Description:

This will be revised in the next version of the specification.

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=22

Status:   Resolved (Future Direction)   November 3, 2006   Issue Type:   DTD

Issue Description:
When adding support for namespaces in the 2005 specification, we forgot to include support for other namespaces needed by extensions to the dtbook element set. Among the places support is needed is in SMIL, to identify where reading systems will need support for different vocabularies in order to render extension content. In SMIL 2, this is done via the systemRequired attribute, which, however, is not currently a part of the dtbsmil DTD.

Resolution Description:
Resolve as a (possible) Future Direction. For now, a possible work-around is to use the type attribute rather than the systemRequired attribute.

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=21

Status:   Resolved (Future Direction)   August 2, 2006   Issue Type:   DTD   Assigned To:   DTD Team LE

Issue Description:

The 2005 DTD tries to avoid allowing nested prodnote elements. The content of prodnote is 'flow' which includes 'inlinenoprodnote', and there is a comment in the DTD saying that prodnotes should not nest. But prodnotes can be nested since 'flow' includes 'blocknoimggroup', which includes 'dtbookblocknoimggroup', which in turn allows the prodnote element.

Resolution Description:

Agreed Solution:

No change in this minor version upgrade. This issue is placed in the future direction category, and will be addressed when we move from DTDs to a schema language.

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=19

Status:   Resolved (Future Direction)   August 2, 2006   Issue Type:   DTD   Assigned To:   DTD Team

Issue Description:
By wrapping block elements in 'prodnote' or 'imggroup' elements, it is possible to put block elements in an inline context. For example, it is possible to put a table as a descendant of a heading.

Resolution Description:

Agreed Solution:

No change in this minor version upgrade. This issue is placed in the future direction category, and will be addressed when we move from DTDs to a schema language.

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=20

Status:   Resolved (Future Direction)   September 22, 2006   Issue Type:   Specification   Assigned To:   George Kerscher

Issue Description:

What kinds of change in a grammar results in a change of the namespace URI?

W3C recommends that specifications that define namespaces should explicitly state their policy with respect to changes in the names defined in that namespace [1],[2].

This policy can be published as a separate document at the zed site, and thus does not necessarily impact the spec document (nor erratas).

[1] http://www.w3.org/TR/webarch/#versioning-xmlns

[2] http://www.w3.org/2001/tag/doc/namespaceState.html

Resolution Description:

We will create a namespace URI policy with the next revision of the specification. However, it will be done sooner if required by a modular extension.

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=17

Status:   Resolved (Future Direction)   November 3, 2006   Issue Type:   Specification   Assigned To:   issue triage team

Issue Description:

One extension needed for DTBook adoption in Japan is Ruby. Suggestion that a WG be put together to look at formally adopting an extension using the Ruby module in XHTML 1.1[1], alternatively ITS [2].

[1] http://www.w3.org/TR/ruby-implementation/

[2] http://www.w3.org/TR/2006/WD-its-20060222/

Resolution Description:
Accept recommendation and consider for future direction.

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=18

Status:   Resolved (Future Direction)   November 9, 2005   Issue Type:   Specification   Assigned To:   Zed Committee

Issue Description:

I would like to propose a change to the ANSI/NISO Z39.86-2002 and -2005 standards regarding the section entitled "Audio File Formats."

I believe it is in the best interest of the DTB community for the standards to be codec agnostic. By specifying codecs, the standards lock out the use of newly developed or less expensive compression schemes that could benefit DTB producers and consumers. These include the open source Ogg family of codecs (including Vorbis and Speex) and the extremely efficient AMR-Wideband+ codec, which has won a number of codec "cook-offs" for speech sound quality and which has been chosen by the National Library Service for use with its upcoming Digital Talking Books.

In place of specifying particular codecs, we may wish to have the standard specify only a set of qualifying quality factors, such as ease of navigation. NLS has developed a list of nine quality factors that we used in making our decision to go with AMR-WB+. I would be happy to share these with the committee as a starting point for issuing this erratum.

Please let me know how we should proceed in handling this issue.

Resolution Description:
A goal for the next revision of the spec is to adopt a more flexible mechanism for identifying suitable codecs.

Resolution Area:
http://www.daisy.org/z3986/requirements/detail.shtml?i=16