valid-relative-container-URL-with-fragment string in EPUB 3.3 · Issue #2076 · w3c/epub-specs · GitHub
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

valid-relative-container-URL-with-fragment string in EPUB 3.3 #2076

Closed
murata2makoto opened this issue Mar 12, 2022 · 4 comments · Fixed by #2081
Closed

valid-relative-container-URL-with-fragment string in EPUB 3.3 #2076

murata2makoto opened this issue Mar 12, 2022 · 4 comments · Fixed by #2081
Labels
EPUB33 Issues addressed in the EPUB 3.3 revision Spec-EPUB3 The issue affects the core EPUB 3.3 Recommendation Topic-OCF The issue affects the OCF section of the core EPUB 3 specification Type-Editorial The issue does not affect conformance

Comments

@murata2makoto
Copy link
Contributor

The term "valid-relative-container-URL-with-fragment string" appears in 6.1.5 in EPUB 3.3. I did not immediately realize that this term is specific to EPUB. I think that adding "ocf" somewhere in this term will make this point clearer.
@iherman
Copy link
Member

iherman commented Mar 12, 2022

Would "ocf-relative-container-URL-with-fragment string" work? @rdeltour ?

@rdeltour
Copy link
Member

Would "ocf-relative-container-URL-with-fragment string" work?

It sounds slightly redundant as "ocf" and "container" kinda mean the same thing. What about s/container/ocf/ in the current term, which would become: "valid-relative-ocf-URL-with-fragment string"?

@iherman
Copy link
Member

iherman commented Mar 12, 2022

Would "ocf-relative-container-URL-with-fragment string" work?

It sounds slightly redundant as "ocf" and "container" kinda mean the same thing. What about s/container/ocf/ in the current term, which would become: "valid-relative-ocf-URL-with-fragment string"?

That works for me.

@mattgarrish mattgarrish added the Topic-OCF The issue affects the OCF section of the core EPUB 3 specification label Mar 12, 2022
@iherman iherman mentioned this issue Mar 14, 2022
Merged
@iherman
Copy link
Member

iherman commented Mar 14, 2022

@murata2makoto can you look at #2081 to see if it answers your issue?

@iherman iherman added the Type-Editorial The issue does not affect conformance label Mar 14, 2022
@mattgarrish mattgarrish added the EPUB33 Issues addressed in the EPUB 3.3 revision label Mar 18, 2022
@mattgarrish mattgarrish added the Spec-EPUB3 The issue affects the core EPUB 3.3 Recommendation label Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
EPUB33 Issues addressed in the EPUB 3.3 revision Spec-EPUB3 The issue affects the core EPUB 3.3 Recommendation Topic-OCF The issue affects the OCF section of the core EPUB 3 specification Type-Editorial The issue does not affect conformance
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Renamed the valid-relative-container-URL-with-fragment term w3c/epub-specs
4 participants
@iherman @rdeltour @mattgarrish @murata2makoto