- From: Phillips, Addison <addison@amazon.com>
- Date: Tue, 16 Sep 2008 19:16:55 -0700
- To: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
- CC: John Cowan <cowan@ccil.org>, "Roy T. Fielding" <fielding@gbiv.com>, Mark Nottingham <mnot@mnot.net>, URI <uri@w3.org>, Joe Gregorio <joe@bitworking.org>, David Orchard <orchard@pacificspirit.com>, Marc Hadley <Marc.Hadley@Sun.COM>
>
> Similarly, if the template processor relies on user input, it
> should be
> subjected to NFC per RFC 3987, while if it's a machine value, the
> NFC
> form should have been used in the first place.
... which effectively means that the template processor does not apply any form of normalization. NFC should have been used early; if it wasn’t, for some reason, IRI doesn't impose it.
Note the point, though, about include-normalization. Consider:
http://example.org/{boo}{moo}
Let 'boo' = 'e'
Let 'moo' = '\u0301' (a combining mark)
The resulting URI is not NFC, even though each of the parts is.
Addison
Received on Wednesday, 17 September 2008 02:17:52 UTC