Lists Home |
Date Index |
- From: james anderson <James.Anderson@mecomnet.de>
- To: XML Dev <firstname.lastname@example.org>
- Date: Mon, 25 Jan 1999 16:27:13 +0100
John Cowan wrote:
> > It suffices to permit the application to process
> > names in the parser's dynamic context. To this end it need no explicit access
> > to the prefix<->uri map, just to an interface which interns qualified names
> > given the parser's dynamic context.
> Probably sufficient; it may be, however, that there is an occasional
> need to generate a currently-correct Qname from a URI+NCName.
The only occasion to do this is when encoding the name for serialization. This
belongs not "in the application", but rather in the parsing/encoding layer.
Even if the application is an editor which serializes for presentation. I
would be surprised were editor to run around changing the effective prefixes
for qualified names each time an edit operation takes place. It is more likely
to ensure that unique prefixes are available either at the document (ie root
element) level, or introduce them into elements as required, and then permit
an encoding substrate to do its job - in which case the binding specification
will not be in the name but in the element.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)