- From: Phil Archer <phil@philarcher.org>
- Date: Mon, 26 Jan 2009 14:27:47 +0000
- To: Jo Rabin <jrabin@mtld.mobi>
- CC: Public POWDER <public-powderwg@w3.org>
Jo, I'm working through all our comments, making sure that everything has been closed off and answered. I realised that I'd not publicly answered this point you raised a while back for which I must apologise. We did discuss it and resolved that no, we wouldn't introduce an option to make path matching case-insensitive. Yes, www.w3.org/tr/ redirects to /TR/ but, well, it's a redirect, not a case-insensitivity. Given that, and the fact it's easy enough to include both tr and TR (and, obviously analogous cases) thus <includepathstartswith<tr TR </includepathstartswith> And, finally, that paths are specified as being case sensitive, we decided to stick with protocol in this regard. Cheers Phil. Phil Archer wrote: > > As you might guess, I'm loading up the comments tracker. Here's one I > had from Jo: > > Referring to the Grouping Doc, he suggests that we consider allowing > case-insensitive match on the path. As evidence, www.w3.org/TR/ and > www.w3.org/tr/ both work... (tr redirects to TR) > > Phil. > > -- Phil Archer w. http://philarcher.org/
Received on Monday, 26 January 2009 14:28:27 UTC