Reading systems should have some means to navigate multiple files

[wfree-aph]

Use case #11 suggests splitting the text into multiple files. If that is the case, then reading systems will benefit from functionality that allows them to navigate multiple files when performing tasks such as Find or Go to Page. This will also aid in use case #9 since a link may point to a location within a different file inside the bundle.

Detail
If the text is split into multiple files, reading systems and their users will benefit from a means to navigate those files as though they are a single entity. This will mean that the reading system will be able to open the next file when the previous file is concluded, navigate to the correct page even if it is located in a different file than the one that is currently open when using a feature like Go to Page (a feature that navigates directly to the page indicated by the user), or benefit a feature like Find, which looks for markup or text indicated by the user, even if what the user is searching for appears in a different file than the one currently open.

Proposal
Reading systems that intend to support eBraille should be developed to navigate or search across multiple files as seamlessly as possible. They should maximize their use of metadata and any included manifest and spine included in the eBraille bundle to this end.

[wfree-aph]

Since we're basing eBraille on the EPUB packaging format, which includes both a manifest and a spine, this feature is complete. It will depend on reading systems properly implementing the features available but that should be relatively easy since the specification is based on an existing format.