Lists Home |
Date Index |
- From: David Brownell <firstname.lastname@example.org>
- To: Tim Bray <email@example.com>
- Date: Wed, 05 Jan 2000 12:01:54 -0800
Tim Bray wrote:
> At 11:41 AM 1/5/00 -0800, David Brownell wrote:
> >To be clearer, the cases correspond to these XML documents:
> > - undeclared prefix (error for namespace, but legal XML)
> > <prefix:EXAMPLE />
> In SAX2, if namespace processing is turned on (the default) this clearly
> has to be handled as an error.
And the proposal was that it'd be nonfatal, so that applications
will be seeing such data when they continue after nonfatal errors.
One issue was how it'd be represented ... given an API that provides
a namespace URI with every name, what it would provide there.
> > - default namespace (per namespace spec, sections 2, 5.2)
> > <root xmlns="http://foo">
> > <EXAMPLE xmlns:prefix="" />
> > </root>
> Likewise. xmlns:prefix="" is always an error per the namespace spec.
> Er, did you mean <EXAMPLE xmlns="">? If so, it's correct and EXAMPLE is
> not in any namespace.
The ":prefix" was a typo, yes. I used the phrase "default
namespace" incorrectly. This was to be "good" input.
> > - Some URI
> > <prefix:EXAMPLE xmlns:prefix="http://foo" />
> What's the problem here?
There was none. The second and third cases were intended to be legal
both from the XML and the namespaces perspective; only the first was
to be problematic.
> >That is, there's a distinction between "declaration needed and missing"
> >and "default namespace".
> Indeed. The first is an error, the second is legal. I'm feeling stupid,
> because I think I'm missing your point.
How to expose the first case through the API, given that like any
validity constraint it's not fatal.
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 unsubscribe, 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)