- From: Frank Ellermann <nobody@xyzzy.claranet.de>
- Date: Mon, 23 Jan 2006 15:13:24 +0100
- To: public-iri@w3.org
Bjoern Hoehrmann wrote: > I'm not sure what the actual requirement might be. Perhaps > RFC 3987 defines this by now though. You lost me here. 3987 explains how to transform an IRI into an URI. Something like (legacy ->) NFC -> UTF-8 followed by further processing for the "authority" part using IDNA. But it does not say "any URI with %C0 is invalid, because %C0 can't be UTF-8". > I would appreciate if a proposal is made to change the ABNF > to fully express the constraints. There are no constraints on general URIs in addition to STD 66, anything more depends on the scheme. A scheme could restrict e.g. the path to "MUST be percent-encoded UTF-8", and then any %C0 is an error. I don't see how a 3987bis DS could do more than it does now. Did I drop a ball or miss a clue somewhere ? > e.g. in the Markup Validator at <http://validator.w3.org>. That attracted my attention as "validator-fan" (wannabe). Bye
Received on Monday, 23 January 2006 14:51:56 UTC