View Single Post
Old 04-27-2009, 05:52 PM   #46
netseeker
sleepless reader
netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.netseeker ought to be getting tired of karma fortunes by now.
 
netseeker's Avatar
 
Posts: 4,763
Karma: 615547
Join Date: Jan 2008
Location: Germany, near Stuttgart
Device: Sony PRS-505, PB 360° & 302, nook wi-fi, Kindle 3
Quote:
Originally Posted by Valloric View Post
And yet you cannot pigeonhole the standard to 2007 and set arbitrary limits on content files. Ten years from now (probably a lot sooner) even embedded devices will have more than enough resources to parse any kind of epub file, so such limitations would be a hindrance.
Sorry if i'm interfering but nobody says that they should include limitations. Though they could make clear what is the expected handling on devices with low resources. Sax and StAX, HTTP 1.1, MIME and a lot other specifications provide implicit solutions for low-resource devices. Why should a format specification like ePub doesn't take care of such concerns?

From the OPS specification:
Quote:
The specification is intended to give content providers (e.g. publishers, authors, and others who have content to be displayed) and publication tool providers, minimal and common guidelines that ensure fidelity, accuracy, accessibility, and adequate presentation of electronic content over various Reading Systems.
netseeker is offline   Reply With Quote