Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

mattgarrish
Copy link
Member

@mattgarrish mattgarrish commented Jun 4, 2025

Makes the idpf.org URL for expanding terms explicit in the document so there is no confusion about what to use now that the vocabulary is hosted under a W3C URL.

We should probably see about getting http://www.idpf.org/epub/vocab/structure/# to redirect to the new SSV location. It currently goes to the old idpf.github.io location. Even though that document has an obsolete message attached to it, it doesn't need to be accessible anymore.

A simple fix would be to temporarily unarchive that repository and replace that old document with a meta refresh directive so that readers are automatically bumped forward. The more complicated fix would be to get the old idpf.org htaccess file updated.

Fixes #2733


Preview | Diff

@mickael-menu
Copy link

Thank you @mattgarrish, this is helpful.

I have one question regarding the presence of www in the URL. Are they expected? I saw different versions online, but this document references an URL without www:

https://idpf.github.io/epub-vocabs/package/meta/#sec-ref

Properties without a prefix are referenceable using the base IRI http://idpf.org/epub/vocab/package/#.

@mattgarrish
Copy link
Member Author

mattgarrish commented Jun 4, 2025

I have one question regarding the presence of www in the URL. Are they expected?

Ya, it looks like we've flipped between having www and not having it with the vocabularies. Even searching in 3.4 specification I can find some vocabulary URLs that have it and others that don't.

I'm inclined to standardize them all without www. in them.

It has no effect on the authoring side, so the only impact is on tools that want to expand the values to full URLs. Doing that, and for what purpose, is at your discretion, so it's not like changing xml namespaces where the wrong URL could lead to failed rendering. I've also only heard of Readium expanding the values, so if this works for you I don't think this change will have any wider impacts.

@mickael-menu
Copy link

Yes, we went ahead and used the version without www.
It's not really used yet, but it's a way for people to access the original EPUB values in the Readium Web Publication Manifest when we don't have a native mapping. It doesn't really matter as long as we (Readium) stay consistent. However, we prefer to follow the specification accurately.

@mattgarrish
Copy link
Member Author

And I've been forgetting that we wrote an algorithm in the reading systems specification last revision on how to obtain an expanded URL from a value: https://www.w3.org/TR/epub-rs-34/#dfn-obtain-an-expanded-url

That algorithm omits www from all the vocabularies, so the inconsistency is only in the authoring specification. Changing the references in the authoring document to match is more justifiable given that parsing expectation. (I really like it when changes are not seen as arbitrary!)

Thanks again for pointing this out.

@mattgarrish
Copy link
Member Author

Merging this one, as well, as it's a minor and obvious clarification.

@mattgarrish mattgarrish merged commit 27d9b7f into main Jun 9, 2025
2 checks passed
@mattgarrish mattgarrish deleted the fix/issue-2733 branch June 9, 2025 15:36
@github-project-automation github-project-automation bot moved this from In review to Done in PM/EPUB issues Jun 9, 2025
@iherman iherman removed this from PM/EPUB issues Jul 14, 2025
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

Successfully merging this pull request may close these issues.

Prefix URL for the structure vocab is not listed

3 participants