Matt Garrish

> UtilMessage_LocalizationTest.ensureDefault:23 Default constructor should use the (host) default locale. expected:`` but was:`` > UtilMessage_LocalizationTest.ensureNullIsDefault:32 Null locale should use (host) default locale. expected:`` but was:`` Looks like this is related...

This would have to be a change to the core spec, as external references are strictly forbidden from DTDs per https://www.w3.org/publishing/epub3/epub-spec.html#confreq-xml-extmarkupdecl It was put in at least in part for...

> The security implications seem non-trivial: Ya, but the solution in epub tends to be. Reading systems should be the ones not resolving external entity references. There's not much value...

Epubcheck gets its schemas from validator.nu, so you should probably [open this request there](https://github.com/validator/validator/issues).

> If the author uses a URL starting with `/`, I would assume the intent is to resolve that relative to the root of the container. Ya, a path starting...

Path absolute URL string are not recommended in 3.3, so I'm going to add the 3.3 label to this issue rather than start another. See https://github.com/w3c/epub-specs/issues/1681

This restriction has now been broadened and made more restrictive. `file:` URLs are not allowed anywhere in an epub publication. See https://github.com/w3c/epub-specs/issues/2324

Epubcheck can't test what happens at runtime so as far as it can detect you don't have any remote resources references in the document. That's why it's warning you that...

I think this has been raised before. Epubcheck isn't telling you what you did wrong, as it only knows the pattern doesn't match. It's telling you what it expects: a...

Trying to make NCName human readable definitely seems to focus people on the comma being the issue. Could it say "must be a valid ID reference (IDREF)", or is this...