> "negativeInteger" is *not* a primitive type. It's derived from "integer", > which is in turn derived from "decimal". And "decimal" is a primitive. But > you are right in that, to determine whether a type is derived from > negativeInteger, one needs to call getBaseType recursively. > getPrimitiveType won't help here, because it would return "decimal".
If one wants to build up the set of all facets defined in user-derived types, do you have to recursively trek through the base types or are they collected into the attribute type? An earlier response having to do with complex types led me to think they might be (collected), so perhaps I should verify that answer, as well. Does the content model/particle of a complex type incorporate the net of all the base complex types, or does one have to recursively construct the net model? Or is this the wrong question? I see the validator casts the XSComplexTypeDeclaration to an XSComplexTypeDecl in order to call getContentModel(). Is it the content model that is aggregated, while the particle(s) only reflect the current type? Sorry to belabor these points, but even though "XSSimpleTypeDefinition is preferred over XSSimpleTypeDecl" it is really not obvious when one must use an "implementation type" in order to avoid re-doing work the parser has already done. Thanks. Bob Foster --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
