|
@Doitsu Thanks, both are good questions.
1. epub:type in EPUB2 — you're right, this is a real gap on my side. EPUB2's content model shouldn't accept the OPS namespace at all, so epub:type should be flagged there. I've confirmed the cause in the code; I want to match exactly what epubcheck reports (message ID + severity) before I ship the fix, so I won't rush it.
2. USAGE messages — yes, on the roadmap. Right now those findings exist but are folded under INFO. The plan is to split out a proper USAGE level and suppress it by default with an opt-in flag, the same way epubcheck does. Not done yet.
I'm looking into both. I'll post here with the concrete details — what will change and what won't — once I've worked through it. A fairly large piece of work has landed on my plate, so please bear with the timing.
|