Cart
|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: UBL 2, W3C Schema extensibility, and multiple
> >> > Does ##other imply ##local or does ##other require there be a
> >> >target namespace that is different in the particle? If ##other
> >> >implies ##local then Xerces is wrong
My interpretation of this is:
Section 3.10.2 describes the translation from the schema document syntax
into schema components:
The {namespace constraint} for a wildcard if ##other is specified is:
a pair of not and the .actual value. of the targetNamespace [attribute] of
the <schema> ancestor element information item if present, otherwise
.absent..
which I think one has to read as
a pair of not and (the .actual value. of the targetNamespace [attribute] of
the <schema> ancestor element information item if present, otherwise
.absent.).
(since .absent. is the name used in the schema spec to refer to what some of
us misguidedly like to call "the null namespace").
The relevant validation rule is:
Validation Rule: Wildcard allows Namespace Name
For a value which is either a namespace name or .absent. to be .valid. with
respect to a wildcard constraint (the value of a {namespace constraint}) one
of the following must be true:
1 (not relevant)
2 All of the following must be true:
2.1 The constraint is a pair of not and a namespace name or .absent.
([Definition:] call this the namespace test).
2.2 The value must not be identical to the .namespace test..
2.3 The value must not be .absent..
3 (not relevant)
Clause 2.3 means that the null namespace (.absent.) does not match ##other.
##local matches names that are not namespace-qualified (i.e. names in the
null namespace).
Michael Kay
http://www.saxonica.com/
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! 
Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||
