- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 04 Feb 2010 16:44:56 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8207 --- Comment #8 from Julian Reschke <julian.reschke@gmx.de> 2010-02-04 16:44:55 --- (In reply to comment #6) > 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). It's just prose. You do not need a MUST to define how something is done. I realize you disagree with that, but trying to impose a specific specification style on others doesn't seem to be productive. > 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. It would be helpful if you could elaborate what's wrong; maybe by adding an example (I totally believe that something might be wrong, but it's unproductive to do just handwaving). -- 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 Thursday, 4 February 2010 16:44:57 UTC