[deleted comment]

[deleted comment]

Argh!  Corrected URL to web-public version of the document:

                  https://docs.google.com/document/pub?id=1dyFcIHNhLnYZVLugsuD1MYfDW1jwRGexNqyLi5MaUC4

Sorry!  I don't see how to change the original issue.

This is really important. By taking a side in a very active debate, washing 
hands and calling it done, by hanging up curtains over the whole nasty episode, 
the IDPF does itself a disfavour and makes the cost of entry for new Reading 
Systems (eg, from the open source community) astronomical.

I understand that as a rendering engine, WebKit seems the most promising right 
now. In many cases, new Reading Systems can base off it, and have Apple/Google 
foot the codec bill. I think this is short-sighted. Instances like this of 
implicit assumptions about WebKit in the specs need to be carefully reviewed.

I am asking Garth and King-Wai to prepare a more detailed solution breakdown 
for this. 

An analysis document is available at 
https://spreadsheets.google.com/ccc?key=0AnXE8s9XoOz3dFhLWHJzTEgyUUlNU2pEZlRBajc
0dGc&hl=en&pli=1#gid=0

It is only visible to the members of epub-working-group@googlegroups.com

The sharing setting of the aforementioned document has been changed to 
accessible to anyone who uses the following link

https://spreadsheets.google.com/ccc?key=0AnXE8s9XoOz3dFhLWHJzTEgyUUlNU2pEZlRBajc
0dGc&hl=en&authkey=CI2eu_QB

WG has adopted a solution with no video Core Media Types, and no RS 
requirements re support for codecs. Informative recommendations may be added on 
top of this.