It seems like simply finalizing SAX 1.1 extensions is not a sufficient
change for JAXP 1.3 to fully support XML 1.1.
An erratum for the Namespaces in XML recommendation put namespace
declaration attributes in the namespace "http://www.w3.org/2000/xmlns/";.
SAX2 does not accept this change so conforming parsers must report that
these attributes have no namespace. I'm not here to rekindle a debate on
that, however the Namespaces in XML 1.1 recommendation clearly  binds
these attributes to the namespace "http://www.w3.org/2000/xmlns/";. Whether
you agree or not with the errata for 1.0, namespace declaration attributes
do have a namespace in 1.1. There is a feature
"http://xml.org/sax/features/xmlns-uris"; which when set to true would
instruct the parser to report the namespace for these attributes. It was
added to CVS after SAX 2.0.1 so it does not appear to be in any release of
SAX. In order to support Namespaces in XML 1.1, I think such a feature is
Another issue is with normalization checking . While looking over the
JAXP 1.3 draft I saw no mention of how one would go about enabling the
parser to check that a document if fully normalized. This applies to
DocumentBuilders as well. SAX has no such feature.
There are references to XML 1.0 scattered around the SAX2 docs and in at
least one place this constrains a method parameter to an XML 1.0
production. The qName parameter of ContentHandler.endElement  is
defined as a "qualified XML 1.0 name". Interfaces define behaviour so it
would appear that a processor which conforms to this interface is not
allowed to report XML 1.1 qualified names for endElement.
There may be additonal issues. Supporting XML 1.1 in SAX for JAXP isn't
as straightforward as just including Locator2.
Just my two cents.
XML Parser Development
IBM Toronto Lab