![]() String-based page numbers should be compared in lowercase. Our earlier Scribe 1 books may have Roman Numeral pages marked. The page numbers may be either numeric or a string (e.g. When the page numbers are available they may be referenced with: The image stack can also contain images which should not be considered for access (e.g. a completely blank page may face a figure page, both of which are inserted between consecutively numbered pages). In addition, certain pages are not numbered at all (e.g. These two are equivalent and would be remapped to the canonical order:įor a book with a set of numbered camera images we do not always have a mapping between these images and the page numbers (as printed in the book). Specifying display options (zoom level, 2-page view) If a reader implementation does not understand a given key-value pair, it should be ignored.īookreader URLs support the following functionality: The purpose for the remapping to canonical order is to reduce the number of URLs "out there" on the net that point to the same resource. by redirecting, so it appears in the address bar). A user supplied URL will be remapped to the canonical order when given back to the user (e.g. ![]() We specify a canonical order in which the key-value pairs should occur but accept the key-value pairs in whatever order the user-agent specifies. The keys and values are separated by '/'. Minimal/sufficient features - keep the supported feature set small yet sufficient for core tasksīookreader URLs are composed of key-value pairs. ![]() Resilience - display and other options should be accepted in any order "translucency" - while not being fully descriptive, BookReader URLs should give some indication to a human what they point to Bookreader URLs have the following goals:Ĭompactness - short enough to be printed on the cover of a book or included in an academic paper
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |