Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

flat vs nested nav elements in the Navigation Document #69

Closed
GoogleCodeExporter opened this issue Mar 24, 2015 · 5 comments
Closed

flat vs nested nav elements in the Navigation Document #69

GoogleCodeExporter opened this issue Mar 24, 2015 · 5 comments
Labels
Priority-Medium

Comments

@GoogleCodeExporter
Copy link 

Issue raised by Daniel Weck:

The current EPUB Navigation Document definition allows all <nav> elements to 
include nested structures. Is there a reason to restrict this, so that only the 
'toc' <nav> allows nesting? This would echo restrictions in the "original" NCX 
grammar (the single navMap vs multiple navLists).

Original issue reported on code.google.com by markus.g...@gmail.com on 26 Jan 2011 at 11:14
@GoogleCodeExporter
Copy link
Author

Original comment by markus.g...@gmail.com on 27 Jan 2011 at 1:02

  • Added labels: Type-SpecIssue
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author 

Related discussion:

http://groups.google.com/group/epub-21-working-group/browse_thread/thread/631624
1e8427e7db#

Original comment by daniel.weck on 14 Mar 2011 at 10:53

@GoogleCodeExporter
Copy link
Author 

The updated specification includes a "SHOULD" conformance requirement for 
page-lists to be flat. Validation schema up to date. Other nav structures can 
be hierarchical, and nested lists can be used for grouping purposes (there is a 
new "span" element allowed as an alternative to "a", for non-linking list 
headings):

http://epub-revision.googlecode.com/svn/trunk/build/spec/epub30-contentdocs.html
#sec-xhtml-nav-def-types-pagelist

Original comment by daniel.weck on 23 Mar 2011 at 10:00

@GoogleCodeExporter
Copy link
Author

Original comment by daniel.weck on 28 Mar 2011 at 9:10

@GoogleCodeExporter
Copy link
Author 

Proposed fix approved on Wednesday 30 March 2011 at the all-group conference 
call.

Original comment by daniel.weck on 30 Mar 2011 at 10:10

  • Changed state: Verified

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority-Medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter