Originally Posted by DiapDealer
What makes more sense:
Incorporating an epub3 validator in an app that still primarily produces epub2 books?
Or continue to use an epub2 validator and make allowances for the handful of epub3 features that some retailers are cherry-picking?
I for one believe that it makes absolutely no sense to incorporate an epub3 validator into a primarily epub2 system. It's not like xhtml or css where using a stricter spec won't really hurt. You're talking apples and oranges. Most everything would fail validation miserably employing epub3 rules.
You are completely missing the point.
I agree that epub3 is immature and I have no intention of making any epub3s any time soon.
Epubcheck 3 is a more accurate validator for epub2 than whatever Sigil uses now. It is also what distributors will be using. Its no good telling Apple (for instance), when they reject your book, that their validation procedure is wrong and your epub is right because it passed the lame validation in Sigil.
And FYI this has already happened to me.
So don't tell me that it doesn't make sense, tell the distros that are already using epubckeck3.