Brady Duga

I am not an svg expert, but I am concerned that it will be difficult to validate svg in the era of living standards. An svg 1.1 validator should reject...

The question seems to be, is an iframe which references a non-local URL allowed per the spec. Resource Locations seems to address this: https://w3c.github.io/epub-specs/epub33/core/#sec-resource-locations Reading that seems to say no,...

> Just to be clear, in current distribution systems, large EPUBs are not allowed, and thus embedded video is not being done. Add to this that two codecs are embedded,...

More similar cases can be found in the following tests: * pkg-spine-duplicate-item-hyperlink * pkg-spine-duplicate-item-rendering * pkg-spine-duplicate-item-ui

> Doesn't this lead us into defining what it meas to reject content: won't load the publication into the user's library; won't open the publication; won't open the offending document;...

Having read this, now I am not sure I like having it at all. For instance, does this mean if you support side loading you can't reject due to epub...

I am not sure what the best way to specify this content is, I have seen multiple different approaches now and they all seem to have some issues. I agree...

Speaking with one of the authors for the RFC (J. Alakuijala), I have confirmed that the changes to the spec during transition to RFC are editorial in nature and should...

> `rendition:flow` remains a preference and not something that the RS or the user are forced to follow. That's perfectly fine for reflowable publications, but it would very much break...

Non-technical comment - the term Webtoon is trademarked in multiple jurisdictions, so we should avoid using it generically. I have seen the term Webcomic used to sometimes refer to similarly...