Lists Home |
Date Index |
- From: james anderson <James.Anderson@mecomnet.de>
- To: "firstname.lastname@example.org" <email@example.com>
- Date: Thu, 11 Feb 1999 11:13:51 +0100
> 4. An element or attribute name without a prefix is interpreted as
> belonging to the default or to no namespace if a default has not been
this one is imprecise as worded. i'll leave it to others to refine it... :)
> A solution discussed in the thread involves creating a new document
> and associated DTDs with these changes made and then doing normal XML
> I would suggest the following changes to the namespace recommendation
> to address some of these problems:
> 1. Allow a DTD to declare the namespaces and prefixes it uses.
a method to do this with pi's has been demonstrated.
it should also be possible to do this with attributes' default declarations.
in that case, similar scoping rules could be inferred from the content models.
so long as there were no contradictions implied, this would work for your 50M files.
> 2. Allow a DTD to declare its default namespace (itself). This removes
> the need to prefix elements and attributes in the DTD.
see above. given a default declaration on a "root" element, the remainder
could be inferred.
> 3. Allow a namespace declaration to optionally include a URL for a
> DTD, just as documents do.
> 4. Enhance XML validation. When an element is not in the current
> namespace, look at the namespace declaration. If it does not have an
> associated DTD, only do well-formed parsing of the element. If it does
> have an associated DTD, validate the element against the associated
> DTD with the new namespace as the default.
i don't see why this is necessary. wouldn't your 50M case would alread have dtd's?
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/ and on CD-ROM/ISBN 981-02-3594-1
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)