This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
xquery F&O gives http://www.w3.org/2005/xpath-functions as a namespace, but when I go there, I get redirected to http://www.w3.org/2005/xpath-functions/ where it says... Each function and operator is uniquely identified with a URI of the form: http://www.w3.org/2005/xpath-functions/#name What is the full URI of fn:starts-with ?
The specification is clear, I believe, the full URI for fn:starts-with is http://www.w3.org/2005/xpath-functions#starts-with
Norm will fix when preparing next round of publication.
But I want it left open until it's fixed :-)
This will be fixed in the 8 June publication round.
We failed to fix this because of constraints in the web server configuration
Proposed solution: rename the collation URI to /2006/xpath-collations/codepoint
I don't think I see the logic why changing the collation URI should have any bearing on this problem. And please could we not change the collation URI at this stage without very strong justification. Any change will be very disruptive.
It's an ugly practical detail in web server administration. I thought changing the collation URI would be less painful than changing the xpath-functions URI :-) If you do a GET onthe xpath-functions namespace, you want "/2006/xpath-functions" to appear in the browser. (Because people are going to cut-and-paste it and "/2006/xpath-functions/" is a different URI for namespace purposes.) But if a directory named /2006/xpath-functions exists, a request for /2006/xpath-functions is always redirected to /2006/xpath-functions/ And because we have another URI named /xpath-functions/collations/..., we can't remove the xpath-functions directory. Rock. Hard place. Between. :-(
And because we have another URI named /xpath-functions/collations/..., we can't remove the xpath-functions directory. Norm, cant you remove the directory (so trailing slashes dont get added) but still keep the URI /xpath-functions/collations/ by silently rewriting URLs of that form it to serve files from somewhere else? David
I don't think silent rewriting will work, though it might. Henry Thompson also suggested to me yesterday that using ScriptAlias and just taking over the entire tree might do it. I'm experimenting. With luck, this issue will silently close itself again today :-)
Indeed, David, you're right. RewriteRules will do the trick. I'll get webreq to install them and then close this again. Whew!