Matt Garrish

The schemas already enforce xsd:language constraints: > opf.dc.language = element dc:language { opf.id.attr? & datatype.languagecode } > datatype.languagecode = datatype.BCP47 > datatype.BCP47 = xsd:language { pattern = "[a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})*" } But...

We had a long discussion about well-formed v. valid for web publications and the resulting consensus was that there is little value in enforcing validity. Reading systems will react or...

> Also, I'm not familiar with the state of custom elements in EPUB Ya, that's interesting now. They used to be not allowed because they were defined in separate W3C...

The restrictions were undone, but it appears that epubcheck already restricts where remote resources can be referenced. Remote audio and video, at least, are only allowed from `audio` and `video`...

It looks like fonts are also restricted. If I use a stylesheet link declaration or import rule for a Google font, I also get the message about the resource having...

Yes, it's valid, but the schemas don't fully support svg2. I've opened an issue against the nu validator to add: https://github.com/validator/validator/issues/1008

> Are we using ... some sort of hybrid validator? That's what I understand is done for the nu validator based on [this discussion](https://github.com/validator/validator/issues/564) I found. For epubcheck, my understanding...

While I'm fine if the EPUB specs ultimately do not require validity for conformance, it would greatly reduce the usefulness of epubcheck if we stop checking the validity of SVG...

I tried to incorporate the commented-out test for this but am still getting the error.

Looking closer at the test, the rdf element is disallowed when the svg is embedded in an xhtml document, but if I split it off into an svg doc the...