-
Notifications
You must be signed in to change notification settings - Fork 1
Vendors catalog don't use Schema.org #4
Comments
Sorry, comment removed. |
Correct. The idea discussed in the Working Group is that frontend platforms digest EPUBs and extract Schema.org information directly from the file. However, there are some case studies where this is not possible, for example for lending platforms that do not have the file, but only the ONIX metadata, and that require the file from the digital distributor ONLY when the user requests it. |
@gregoriopellegrino even for the first use case where front end platforms ingest EPUB files, do we know which ones don't receive any ONIX feeds ? Also, as EPUB has nothing on commercial information, and minimal on bibliographic metadata, how do these build their catalog entries? |
You're right, I think we need to have an open discussion at the next call about this document. If Charles agrees, I would invite you to attend. |
I totally agree lets bring this up in the next call. We will discuss this one June 19'th call |
in the section "Exposing EPUB Accessibility Metadata to Search Engines":
The Implementation sub-section expose Schema.org only, but vendors use ONIX feeds from publishers to ingest titles in their catalogs, not schema.org.
The text was updated successfully, but these errors were encountered: