http://www.w3.org/Bugs/Public/show_bug.cgi?id=8207 Ian 'Hixie' Hickson <ian@hixie.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |NEEDSINFO --- Comment #6 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-01-04 08:08:04 --- That text is woefully vague. For example the only conformance criteria in the definition of "resolve" is "these parsed components may then be recombined", which isn't even a requirement (it's a may, not a must). I'm looking for something which is unambiguous, absolutely clear, precise, and explicit about how two incoming Unicode strings and a character encoding are turned into a single Unicode string. Currently this simply isn't present in the detail needed to interoperably implement URL resolution in the face of erroneous URLs. Ideally this would mean a set of steps introduced with a MUST requirement, which can be blindly implemented with little thought, with no interpretation needed. -- 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 Monday, 4 January 2010 08:08:06 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 4 January 2010 08:08:06 GMT