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 guess it depends on how many files you are willing to hand correct and how fussy your vendors are. Our distributor is using 3.0RC-2, and catching errors that 3.0b5 is missing (the validator built in to the Oxygen editor). Our files are produced by our typesetting vendors, and I don't have time to correct every one. I need to make sure our files aren't rejected by the distributor. So that means I have to hold my suppliers to the strictest standards.