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

section 3.2 AVG Content Conformance clarification #857

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

section 3.2 AVG Content Conformance clarification #857

TzviyaSiegman 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

@TzviyaSiegman
Copy link
Contributor

Minor wording tweak for clarity:
"It must be an SVG document fragment valid to the constructs defined in that specification, and conform to all content conformance constraints expressed in Restrictions on SVG."
might be clearer if it said
"It must be an SVG document fragment valid to the constructs defined in the SVG specification, and conform to all content conformance constraints expressed in Restrictions on SVG."
The current text sounds like it refers to SVG document fragment spec instead of SVG spec.
@mattgarrish
Copy link
Member

Ya, that's a beefy statement. I think we can go even simpler to:

"It MUST be a valid SVG document fragment [SVG], and conform ..."

@mattgarrish mattgarrish modified the milestone: EPUB 3.1 Sep 7, 2016
@mattgarrish mattgarrish added the Topic-ContentDocs The issue affects EPUB content documents label Sep 7, 2016
mattgarrish added a commit that referenced this issue Sep 8, 2016
@mattgarrish
Fixes issues #852, #857, #856;
386e61f 
Addresses some comments from Daniel Weck about opf atttributes
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 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
2 participants
@mattgarrish @TzviyaSiegman