- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Sat, 30 Jun 2007 06:44:16 +0200
- To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Cc: www-archive@w3.org
* Lachlan Hunt wrote:
><foo xmlns:a="http://example.org/a">
> <namespace>
> @namespace a "http://example.org/b";
> </namespace>
> <select value="a|x"/>
></foo>
>Since it is FooML that has allowed the use of both mechanisms to declare
>namespace prefixes for selectors, it is up to the FooML specification to
>define the conflict resolution algorithm.
Which is why the specification should not say "The case sensitivity of
namespace prefixes in selectors depends on the mechanism used to declare
them"--you have to consult the "conflict resolution algorithm" instead.
>You are describing a hypothetical problem that has absolutely nothing
>to do with the case sensitivity of the prefix, but rather a general
>conflict between 2 mechanisms.
Case-sensitivity of strings controls when two strings are equivalent.
The concern is not how to map the prefixes in "x|E" and "X|E" to name-
space names, but whether the two are syntactically the same selector.
If you have
Mechanism A: Namespace prefixes in selectors are case-sensitive.
Mechanism B: Namespace prefixes in selectors are case-insensitive.
you end up saying ("x|E" == "X|E") && ("x|E" != "X|E") is true, which
is not possible.
--
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 Saturday, 30 June 2007 04:44:29 UTC