Romain Deltour

> Such custom elements seem only to appear in the working draft HTML5.3 - do they apply to XHTML syntax as well? > Until this is not a recommendation, this...

> The sample EPUB from shashikumar1 does not contain a script at all, therefore no 'definition' of the custom element, therefore even using the working draft 5.3 for checking it...

@murata2makoto said in #1244 > I understand that this newly-added check ensures what has been required by the EPUB3 MO specification. This requirement is stated as "The ordering of these...

I think it's reasonable to preemptively demote MED_015 to a warning in the next maintenance release, if it happens before fully implementing EPUB 3.3.

EPUBCheck v4.2.6 now reports `MED-015` as a `USAGE`. I'm keeping this issue open until we decide if we want to totally prune the feature and related code when we implement...

Thanks for the report, good question! As far as I can see this is allowed by the spec, but I may be wrong. What do you think @mattgarrish? In any...

> This is certainly doable. We can also change the reference to the new spec, as this is in an informative section. ok. Another possibly relevant ref is the [WHATWG...

> For me, the requirement for reading systems to ignore the tag makes any concerns moot. We'd have to return to the tag in the future, at the very least,...

It is absolutely essential to provide a way to navigate deep in the content, like with a heavily nested toc. Could you do that with the BFF JSON? If not,...

> I do find it quite amusing that you're concerned about nesting slightly more the JSON document, but forcing a short story or basic novel to duplicate information and create...