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

what are "discouraged" constructs? #855

Closed
mattgarrish opened this issue Sep 7, 2016 · 1 comment
Closed

what are "discouraged" constructs? #855

mattgarrish opened this issue Sep 7, 2016 · 1 comment
Labels
EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification Topic-ContentDocs The issue affects EPUB content documents
Milestone
EPUB 3.1

Comments

@mattgarrish
Copy link
Member

The section on rp doesn't contain any normative requirements, so it should have an informative label.

The section on embed says its use is "discouraged" but then normatively says you should use object. If this is informative guidance, authors should only be encouraged to use an alternative. If it's normative, it needs a "should not" on use of embed not "discouraged"?

These also should be separate subsections, but use bridgeheads in the source, so they don't appear in the table of contents.
@mattgarrish mattgarrish added the Topic-ContentDocs The issue affects EPUB content documents label Sep 7, 2016
@mattgarrish mattgarrish added this to the EPUB 3.1 milestone Sep 7, 2016
@mattgarrish
Copy link
Member Author

Proposed Solution

  • Change "Authors should use the object element instead." to "Authors are encouraged to use the object element instead, as it provides an intrinsic fallback mechanism."
  • Add a "This section is informative." label.
  • Mark up the two sections so that they appear in the table of contents.

@mattgarrish mattgarrish added the Status-Proposed Solution A proposed solution has been included in the issue for working group review label Sep 7, 2016
mattgarrish added a commit that referenced this issue Sep 14, 2016
@mattgarrish
Fixes for the following issues:
ec2c32b 
#870 - clarify white space in epub:type
#866 - clarify hyperlinks outside container do no get listed in manifest
#855 - remove normative keyword from informative discouraged constructs
#853 - separate/clarify rdfa and microdata usage and support
#847 - improve media overlays purpose and scope description
#844 - remove "user" as a defined term
#842 - clarify meaning of element "value" as text content
#834 - remove html processing model from relationship description

Also include minor wording clarifications suggested as part of the content documents review in issues #880, #879, #878, #877, #876, #875, #874, #868, #867, #864, #863, #860, #857, #856, #852, #849 and a few issues reported by via the mailing list.
@mattgarrish mattgarrish removed the Status-Proposed Solution A proposed solution has been included in the issue for working group review label Sep 25, 2016
@mattgarrish mattgarrish added the EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification label Aug 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
EPUB32 Issues from 3.0.1 resolved in the EPUB 3.2 specification Topic-ContentDocs The issue affects EPUB content documents
Projects
None yet
Milestone
EPUB 3.1
Development

No branches or pull requests
1 participant
@mattgarrish