- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Thu, 24 Apr 2008 00:15:42 +0200
- To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Cc: public-webapi <public-webapi@w3.org>
* Lachlan Hunt wrote: >The changes required to the spec would not be too difficult. It would >basically just require removing all NSResolver related sections and >examples, and requiring implementations to throw NAMESPACE_ERR if a >namespace prefix is used. This approach would be forwards compatible >with a future version of the spec that defined the NSResolver. It might be wise to keep the optional second argument, recommend against specifying it in scripts, and require implementations to support it, and throw if it is specified and not null. This would avoid confusion around how to handle more-than-expected arguments and ensure that implementers don't come back later and say they can't add another argument. Further, it seems a bad idea to use NAMESPACE_ERR, you would either use SYNTAX_ERR because you don't recognize namespaces at all, or use NOT_- SUPPORTED_ERR because while namespaces are recognized, using them inside selectors is not supported. This would ensure that NAMESPACE_ERR is used only if something is incorrect with respect to namespaces. I think the primary reason for omitting this feature from the document would be to ensure that is consistent with the XPath APIs and probably have most of it defined in the specification for those. I suggested as much from the beginning... -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Wednesday, 23 April 2008 22:16:14 UTC