This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
I suggest rewriting the definition of "absolute URL" in the spec to explicitly state that it can optionally contain a fragment: — An absolute URL must be a scheme, followed by ":", followed by either a scheme-relative URL, if scheme is a relative scheme, or scheme data otherwise, optionally followed by "?" and a query, *optionally followed by "#" and a fragment*. And similarly for "relative URL". Then change the definition of "URL" to just: — A URL must be written as either a relative URL or an absolute URL. That is, remove from there the part that says 'optionally followed by "#" and a fragment' (because it's moved instead to the definitions of "absolute URL" and "relative URL". Rationale: I want to directly reference just the definition of "absolute URL" from the spec, but if I do that now I end up with something that can't contain a fragment. (So right now I'd have to instead reference the spec by saying something like, "A URL that is an absolute URL.")
That would no longer match https://tools.ietf.org/html/rfc3986#section-4.3 Though the current definition for relative URL does not match relative-ref either so maybe it doesn't matter. Depends a bit on the dependencies...
(In reply to Anne from comment #1) > That would no longer match https://tools.ietf.org/html/rfc3986#section-4.3 Ah, OK. I guess there much be some reason for it having been defined that way previously. > Though the current definition for relative URL does not match relative-ref > either so maybe it doesn't matter. Depends a bit on the dependencies... I guess for "absolute URL" we shouldn't violate the previous definition unless there's a good reason to. I can't say that I personally know of any really compelling reasons to change it.
I guess once there's a dependency that shows this is needed we can revisit this.