[Bug 8207] Change definition of URL to normative reference to IRIBIS


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |NEEDSINFO

--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch>  2009-12-16 02:45:15 ---
I looked at doing this, but the IRIbis draft isn't yet in a state where I can
really do this. There's no algorithm that defines how to resolve an arbitrary
string against an absolute base URL, as far as I can tell; in particular,
nothing seems to take into account the HRef-charset so as to encode characters
differently in different parts of the string. There's no definition of "valid
URL" that I can refer to (that takes into account the "HRef-charset"). The
parsing algorithm is destructive (e.g. the <path> of "http://example.com/%X"
is, as far as I can tell, 5 characters long ("/%25X"), not three as required by
Web compat ("/%X"). There's no definition of "absolute URL" that I can use
(mostly because the current parsing algorithms are destructive).

This is all assuming that the split should be as it is now; this may not be a
good assumption. If we should move the interface a bit, that may change
matters. For example, it seems to me we probably what the "HRef-charset"
definition in HTML5, rather than in the IRI spec.

Please advise on how I should proceed.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 16 December 2009 02:45:17 UTC