|
Well, but you guys are missing one important point here: the standard specifications are for machine readability, a check for formal correctness. They too define how a device manufacturer should render the defined constructs, but of course they can't force them to react on constructs according to the standard, they can't provide implementations for every combination of constructs, and they even leave some decisions up to the implementor (such as footnote rendering in EPUB3), which is perfectly fine. There is other reading software than the renderer software in e-reading devices, such as webservers and processing tools, which might have a completely different rendering or no rendering at all, and as devices change over time, the standard definition serves as common protocol about how information should be encoded, so that software and devices of the future might access the encoded information in the best possible way.
@odedta:
There are many features of EPUB3 which aren't supported by even one single implementation, and it will stay this way for a while, because EPUB3 is far ahead of its time, while at the same time it is closely connected what's happening with HTML5 in the browser area, so it somehow tracks the progress made in modern web technology.
|