Garth Conboy

Note that I updated the initial description of this bug to remove `version="1.1"` which was technically wrong for including "rel" inside an SVG nested "a" element. No change in behavior......

Another example of a similar issue is this error: ``` ERROR(RSC-005): target.epub/OEBPS/page_22.xhtml(11,81921): Error while parsing file: attribute "fill" not allowed here; expected attribute "aria-activedescendant", "aria-atomic", "aria-autocomplete", "aria-busy", "aria-checked", "aria-colcount", "aria-colindex",...

Pretty hard to offline this content too. I don't think we should bite this off for 3.2.

And, as folks would expect me to say... I think we need to be very wary of specifying UA/RS features. It seems we should specify data, and generally leave it...

Yes, we use, and are dependent upon, these error codes. These form the basis of our ingestion whitelisting system. The existence of these codes and their immutability makes integration of...

We do not support, and as far as I know have never seen one in the wild.

No traction as far as I know.

We don't implement Previews, and don't think we've ever seen any content marked up that way.

Sad but true. It was good stuff.

We support the HTML markup, of course, but don't do anything special (user facing) with all the various indexing epub:type's.