Lists Home |
Date Index |
- From: MURATA Makoto <email@example.com>
- To: "firstname.lastname@example.org" <email@example.com>
- Date: Fri, 03 Jul 1998 12:42:04 +0900
james anderson wrote:
> text the uri is correct.
> if one wishes to resolve a name in the dynamic context of a document or of an
> element, the prefix, in addition to the uri, would be correct.
> although this (the prefix qualification), in any case, is not something an
> application should have to do (therefore the concern for an opaque object,
> which question still stands), it is something which a specification which is
> part of an encoded document would need to express. within the document itself
> it would be wrong ( i won't say 'dead wrong', but it would be more cumbersome)
> to specify relations among symbols and or namespace regions according to uri,
> particularly given that there are already prefix bindings in effect in that
> dynamic context. which is where the prefixes come in.
> in global context, one shouldn't be worrying about qualification any more, the
> tokens which the parser generates whould be globally unique. (the opaque
> objects again...)
I strongly disagree. The whole point of the namespace extension is to
allow applications to tell which namespace a name belongs to. A qualified
name is not an opaque object. Application programs should and will care
the attached URI. On the other hand, prefixes should (ideally) be completely
hidden from applications.
Fuji Xerox Information Systems
Tel: +81-44-812-7230 Fax: +81-44-812-7231
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)