You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The epub: prefix is used on attributes in the element definitions without a
mapping. The only mapping to the ops namespace is given in the informative
examples.
Either a mapping section is needed, or the mapping should be made explicit at
the start of the element definitions.
Original issue reported on code.google.com by mgarrish on 15 Sep 2013 at 5:01
The text was updated successfully, but these errors were encountered:
So I see epub:prefix, epub:type and epub:textref as the attributes with an
epub: prefix.
Do you think it would suffice to add a section like "Namespace Prefix Mapping"
in Content Docs:
http://www.idpf.org/epub/30/spec/epub30-contentdocs.html#sec-overview-nspfx
Or should we also incorporate a "Namespace" heading by the attribute
definition, such as is seen here:
http://www.idpf.org/epub/30/spec/epub30-contentdocs.html#sec-xhtml-content-type-
attribute
Original comment by marisa.d...@gmail.com on 25 Sep 2013 at 8:55
I'd vote to add a namespace prefix mapping section. It'll be easy to adapt
the Content Docs section for MO, and simplifies things if there are other
mappings in the future.
The problem with the attribute definition model is that these aren't
standalone attributes, so we'd have to write the namespace into their text
definitions. I think it's simpler just to add the mapping table.
Original comment by mgarrish on 26 Sep 2013 at 1:52
Original issue reported on code.google.com by
mgarrish
on 15 Sep 2013 at 5:01The text was updated successfully, but these errors were encountered: