On Friday, May 3, 2002, at 09:16 AM, [EMAIL PROTECTED] wrote:
> 1. Annotation
>
> An "annotation" contains:
> {application information}: A sequence of element information items.
> {user information}: A sequence of element information items.
> {attributes}: A sequence of attribute information items.
>
> How can we expose *information items*, in what form?
Isn't Xerces capable of generating XNI/SAX events from a DOM?
> 2. getName()/getNamespace()
> ...
> What do you think?
Aesthetic considerations aside, they can simply be implemented by a
{ return null; } where they don't apply, making things simpler.
> 3. Actual values
>
> How to expose actual values? Do we want to define interfaces to
> represent
> the actual values (date/time types especially)? After we have such
> interfaces, we can return "Object" from related methods.
I think that date and time objects need to be wrapped to associate
appropriate methods to all the different variants (i.e. date vs
duration, etc.).
The others can probably do with a simple Object representation
containing the actual value, this would slightly complicate things for
comparison but would keep memory occupancy to acceptable levels (adding
a wrapper would imply adding quite a bit of overhead to the memory
footprint).
Another solution could be to have an XSObject, XSBoolean, XSDecimal,
etc. kind of hierarchy where equality and ordered can be defined
appropriately in the base XSObject (vs relying on Object), without
incurring in too much additional wrapper overhead. This route could also
provide a simple way of obtaining the normalized value from the XSObject
and keeping the original lexical representation separately.
> 4. Get global type definitions
> ...
> What do you think?
I'd vote for the second approach.
> 5. min/max occurrence values
>
> On XSParticle interface, getMin/MaxOccurs returns *int*. Is this enough.
> The spec says nonNegtiveInteger (0~+inf). Should we return BigInteger?
> Would *long* make it better? (*long* doesn't solve the problem, just it
> allows more values than *int*).
Considering that these are occurrences, a normal int looks like a pretty
large number to me, I cannot easily imagine an application that has more
than 2G occurrences of something in a single document. Of course 640K of
RAM are enough for most people too ;)
Thanks,
- Fabio
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
