Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for dc:type #7

Closed
HadrienGardeur opened this issue Jan 2, 2017 · 2 comments
Closed

Add support for dc:type #7

HadrienGardeur opened this issue Jan 2, 2017 · 2 comments

Comments

@HadrienGardeur
Copy link

HadrienGardeur commented Jan 2, 2017

In EPUB 3.0.1, dc:type is tied to an EPUB controlled vocabulary that we should attempt to store in our in memory model and in the Web Publication Manifest.

Since prior to EPUB 3.0.1 other values could be used, it's probably best to filter this and only support controlled vocabularies.

@HadrienGardeur
Copy link
Author

It's unclear at this point, how exactly this should be represented in the JSON, which is why this issue isn't in the backlog yet.

Since this is fairly specialized in EPUB, I'm tempted to group it with similar properties.

@HadrienGardeur
Copy link
Author

So far, the following metadata seems very EPUB centric and not necessarily useful elsewhere:

  • rendition properties
  • EPUB type
  • MO properties (active class, skippable elements)

These are likely candidate for an extension in the Readium Web Publication Manifest, rather than being first class citizens.

@HadrienGardeur HadrienGardeur closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant