Alan Hudson wrote:
>> Yes, very good point.
>>
>> It should be possible to extend the SchemaProcessor to have a methods
>> to obtain two Map<QName, QName> for elements and attributes that maps
>> an element/attribute to a QName of a simple data type or a list of
>> simple data type (so it is easy to support arrays).
>>
> This is likely too simple to handle nested duplicate names. ie
> Customer.Address_at_zip and Vendor.Address_at_zip where zip is a String in one
> and an int in another. Something that indexes xpath expressions to a
> datatype is likely needed.
>
I am not sure i understand.
I would have thought the namespace name and local name should be enough
to identify the type, as it is unlikely when using schema to get a clash
(and if so i am not quite sure what the rules for validation are).
>> I did have a quick look at the XSOM API to determine if an
>> element/attribute declaration corresponds to a simple type or a list
>> of simple type, but it is not obvious because some schema can have one
>> or more levels of indirection.
>>
> xerces had some facilities for this. I need to relook at my XSBC code
> to see what I did for that. Never got it totally working. When walking
> a document you could get back the datatype of the current
> element/attribute in traversal.
>
OK.
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109