The spec states "Contents within the Package MUST reference these resources via relative-URL strings [url].".
A relative-URL string cannot contain a fragment identifier.
On the other side the EPUB 3.3 OCF specification states that "Files within the OCF Abstract Container MUST reference each other via relative-URL-with-fragment strings."
We should certainly allow fragment ids in relative URLs. To be validated.
Warning: A relative-URL string can be a path-absolute-URL string. We need to define how path absolute URLs are dereferenced. Same problem as in EPUB 3.3.
The spec states "Contents within the Package MUST reference these resources via relative-URL strings [url].". A relative-URL string cannot contain a fragment identifier.
On the other side the EPUB 3.3 OCF specification states that "Files within the OCF Abstract Container MUST reference each other via relative-URL-with-fragment strings."
See relative-URL-with-fragment strings
We should certainly allow fragment ids in relative URLs. To be validated.
Warning: A relative-URL string can be a path-absolute-URL string. We need to define how path absolute URLs are dereferenced. Same problem as in EPUB 3.3.