- From: <bugzilla@jessica.w3.org>
- Date: Wed, 10 Aug 2011 17:15:15 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13750
Summary: Prefixes for defaulted attributes
Product: XML Schema
Version: 1.1 only
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Structures: XSD Part 1
AssignedTo: David_E3@VERIFONE.com
ReportedBy: mike@saxonica.com
QAContact: www-xml-schema-comments@w3.org
CC: cmsmcq@blackmesatech.com
In Part 1 section 3.4.5.1, it is stated:
<quote>
[prefix]
If the {attribute declaration} has a ˇnon-absentˇ {target namespace} N, then a
namespace prefix bound to N in the [in-scope namespaces] property of the
element information item in the ˇpost-schema-validation infosetˇ. If the
{attribute declaration}'s {target namespace} is ˇabsentˇ, then ˇabsentˇ.
If more than one prefix is bound to N in the [in-scope namespaces], it is
ˇimplementation-dependentˇ which of those prefixes is used.
</quote>
There is a case this does not cover, namely when the attribute declaration has
a non-absent target namespace, and no prefix is bound to N in the in-scope
namespaces of the instance, either because the target namespace is not declared
in the instance, or because it is the default namespace in the instance. In
this case I believe the correct action is for an implementation-dependent
prefix to be used.
This issue is currently being discussed in the JDOM community; when Xerces is
used as the schema processor, it generates an Infoset (in the form of a stream
of SAX events) in which the attribute information item has a namespace URI but
no prefix, and this crashes JDOM (I think it would also crash Saxon).
The (lengthy) JDOM thread can be found here:
http://markmail.org/message/ufye27danv4myk35
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 10 August 2011 17:15:23 UTC