> But, if fType = WILDCARD_OTHER, this implies any namespace other than
> targetNamespace. Then there is no need to keep a list of namespaces for
this
> case, as mentioned in the w3c schema structures.
>
> Can you explain why you have done this?.
4 reasons:
1. If we use a list for WILDCARD_LIST, and a string for WILDCARD_OTHER,
then we'd have to have 2 fields. That means at least one field is wasted
for each wildcard declaration.
2. In schema, "##other" means "has a namespace which is not the target
namespace". So it's really
uri != targetNamespace && uri != emptyNamespace
Having a list to store both targetNamespace and emptyNamespace will save
this hardcoded behavior.
3. I (vaguely) remember that there was a request in schema to specify
"other" than a list of namespaces (instead of just the target namespace).
So a list can serve this (possible) new feature.
4. Other kinds of schema languages (RelaxNG) supports "other" than a list.
There is always a possibility for Xerces to support them, so we'd better
leave some space for them.
Hope it's clear now.
Sandy Gao
Software Developer, IBM Canada
(1-416) 448-3255
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
