- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Sun, 29 Jun 2008 11:37:42 +0200
- To: Robert J Burns <rob@robburns.com>
- CC: Justin James <j_james@mindspring.com>, 'Smylers' <Smylers@stripey.com>, 'HTML WG' <public-html@w3.org>
Robert J Burns wrote: > I still haven't seen a use case or problem statement for why HTML5 > cannot use the existing URL/URI/IRI specifications. It would be a poor > design decision to diverge from the existing specification son that > without a clear problem statement as to why we need to do so. Specifying > document conformance criteria for URLs, URIs, and IRIs along with HTML5 > UA conformance for handling and error recovery do not constitute a > change in the existing definitions. If we require such a divergence from > existing definitions, what problem are we trying to address? What use > cases cannot be met by the existing specifications? So it seems very > premature to be searching for a new term or word for a definition that > we have not yet developed the need for. > ... Robert, IRI does not allow spaces. Pages use them. Does that answer your question? BR, Julian
Received on Sunday, 29 June 2008 09:38:26 UTC