- From: Martin Duerst <duerst@w3.org>
- Date: Wed, 05 Jun 2002 16:38:32 +0900
- To: noah_mendelsohn@us.ibm.com, Misha.Wolf@reuters.com
- Cc: Tim Bray <tbray@textuality.com>, w3c-i18n-ig@w3.org, www-tag@w3.org
Hello Noah, At 22:33 02/06/04 -0400, noah_mendelsohn@us.ibm.com wrote: >Misha Wolf writes: > > >> Reasons to be careful include that the decisions taken on these >matters: > >> - will be with us for a long time :-) > >> - will affect URI matching in XML Namespaces > >> - will affect URI matching in RDF > >That bit about namespace matching makes me nervous. Last time >namespace matching came up I think we generated 3000+ emails, >and only barely eked out consensus. > >Seriously: I think we should approach changes to namespace >matching with great trepidation, if at all. As far as I know, namespace matching is done 'character-by-character', i.e. 'http://www.w3.org/XML', 'http://www.w3.org/XM%4c', and 'http://www.w3.org/XM%4C' are all considered as different namespaces. This was the main reason why I was so careful to not press more directly for what Tim Bray called the 'obviously correct' solution. >As an implementor, I >can confirm that namespaces are already a very serious impediment >to truly high performance XML processing. Any further changes >(or even clarifications) to matching rules should be evaluated >with great care. The performance considerations for namespace >matching (and perhaps for RDF as well) are not necessarily the >same as when URIs are used for resource retrievals. I think that for RDF, the main consideration is that it is based on namespaces, so it doesn't want to do anything different from namespaces. Regards, Martin. >------------------------------------------------------------------ >Noah Mendelsohn Voice: 1-617-693-4036 >IBM Corporation Fax: 1-617-693-8676 >One Rogers Street >Cambridge, MA 02142 >------------------------------------------------------------------
Received on Wednesday, 5 June 2002 03:39:04 UTC