Quote:
Originally Posted by KevinH
I have opened the following issue in epubcheck explaining the situation. Hopefully they will modify a future version of epubcheck to do "the right thing" whatever that is.
|
FYI: when you run EPUCheck with the optional
-u/--usage parameter, it'll output the following message:
USAGE(OPF-088): C:/Users/user/Downloads/backlink.epub/OEBPS/Text/Section0001.xhtml(12,116): Unrecognized epub:type value "backlink".
In JSON mode, it'll be:
Code:
"messages" : [ {
"ID" : "OPF-088",
"severity" : "USAGE",
"message" : "Unrecognized epub:type value \"backlink\".",
"additionalLocations" : 0,
"locations" : [ {
"url" : {
"opaque" : false,
"hierarchical" : true
}
(Since it's neither a warning nor an error
I mapped it to an INFO message in Sigil.)
If you hear back from the EPUBCheck devs, they'll probably want to know the message code, which is "OPF-088."
Since this message, which is neither a warning nor an error, is only shown if the optional
-u/--usage parameter is specified hardly anybody will ever see it anyway.
EDIT: I've just found
this 2016(!) post:
Quote:
|
Originally Posted by Matt Garrish
There was a draft property named referrer, but was changed to backlink during the process of creating the DPUB-ARIA vocabulary.
The change has to be made to the edupub spec, too, but as that work is on hiatus at the moment we haven't had an opportunity to do it.
Epubcheck won't validate backlink until it gets updated to reflect the changes made during the 3.1 revision. It is the correct term to be using moving forward, though.
|
(Emphasis mine)