On Friday, May 10, 2002, at 09:02 AM, [EMAIL PROTECTED] wrote:
We could use one class for all data/time types. It can have a bunch of
getter methods to get different portions of the value (year, month, day,
etc.) and one method to get the type of the value (date, gYear, duration,
etc.).
I'd rather
As requested, i have reviewed the interfaces.
they look pretty good. nothing leaps out at me as being missing.
you guys have come up with what appears to be a pretty good interface.
of course, the true test is putting them to work!
i look forward to trying out the implementation.
On Fri, 10 Ma
I've updated the interfaces for problems I encountered when trying to
implement them. I would definitely appreciate more comments from folks.
Hopefully I'll check them into CVS, and implement them soon. But we can
always come back and revisit them, if problems are found.
1. Interface name changes:
Fabio, Thanks for your reply.
> > 1. Annotation
> > ...
> > How can we expose *information items*, in what form?
>
> Isn't Xerces capable of generating XNI/SAX events from a DOM?
Is it? :-) Are you suggesting that we store DOM sub-trees in XSAnnotation,
and SAX users generate SAX events from the
> I wouldn't want to start a religious war, but - IMHO - it would be
> better to stick to a single naming convention, either Decl or
> Declaration and use it consistently everywhere.
I completely agree.
> Otherwise we'll always
> be wondering if we're typing things correctly...
This would be mor
AIL PROTECTED] cc:
Subject: [Xerces2] Please
review: schema component API
05/03/2002
12:16 PM
Please respond
to
xerces-j-dev
Hi all,
The attached is the schema componen
@xml.apache.org
[EMAIL PROTECTED] cc:
Subject: [Xerces2] Please review:
schema component API
