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.

Sign up for GitHub

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

Jump to bottom

Add support for properties of a Link Object #4

Closed
HadrienGardeur opened this issue Dec 7, 2016 · 0 comments
Closed

Add support for properties of a Link Object #4

HadrienGardeur opened this issue Dec 7, 2016 · 0 comments
Assignees
@banux @HadrienGardeur

Comments

@HadrienGardeur
Copy link

HadrienGardeur commented Dec 7, 2016 •
edited
Loading

Currently, the properties of either a spine or a manifest item are ignored during the parsing.

Instead of this behavior we'd like to:

  • turn a number of these properties into rel values, for instance for the cover or the ToC
  • express the rest of them in a more consistent way, for example properties such as mathml or svg could instead be expressed as "contains": ["mathml", "svg"]

Additional work on the Web Publication Manifest will have to be done in parallel in order to improve how properties are expressed in our publication model.
banux pushed a commit that referenced this issue Feb 2, 2017
related #4 handle spine and manifest item properties
0c3caaa
banux pushed a commit that referenced this issue Feb 2, 2017
related #4, handle rendition in meta
0c30734
@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
Assignees

@banux banux

@HadrienGardeur HadrienGardeur

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@banux @HadrienGardeur