"Terje Bless" <[EMAIL PROTECTED]> writes:
> On 04.08.01 at 11:11, Jason E. Stewart <[EMAIL PROTECTED]>
> wrote:
>
> Ok, I'm building something as XML::Xerces::EM -- for lack of a better name
> -- but renaming it or munging the code in other ways shouldn't be a problem
> once something is actually implemented.
How about XML::Xerces::Catalog?
> Oh, ok. I was under the impression that DOM did not preserve order and that
> if current accessors did it was incidental to the implementation. If DOM is
> supposed to preserve order then I guess the accessors are deliberately
> written do do so too. No?
Correct. The only thing DOM does not guarantee order for is
attributes of a given element: they are inherently unordered according
to the spec.
> Well, I was going to go for a lazy recursive decent parser, but then they
> went and changed the semantics overnight (literally; from the Aug. 1st
> draft to the Aug. 2nd draft! ;D) so instead of first-match it now has
> longest-match semantics. I suspect these in combination makes a full parse
> necessary.
>
> OTOH, I'm not too worried if the first cut isn't 100% up to the spec. It's
> still a draft and they need thre interopoerable implementations from OASIS
> members before it progresses to final version. There's time to fine tune it
> -- or unbreak it :-) -- afterwards.
Right. My feeling is get something that works, even if it only covers
part of the spec, and then refine it (you'll notice how many releases
of Xerces.pm I've had in the past two months ;-)
> >I'm glad that you're working on this Terje. When we add support for this,
> >Xerces.pm is likely to be the only Perl module to have support for it.
>
> "...but no pressure, ok?" :-)
No problem, as long as you have it by tomorrow ;-)
jas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
