[
Lists Home |
Date Index |
Thread Index
]
At 05:24 PM 5/29/2003 -0700, Joe English wrote:
> > There are people who argue that you could just borrow someone else's pain
> > and use an off-the-shelf parser with a standard API,
>
>But _are_ there any toolkits that handle namespaces sanely?
>I haven't found any yet. (SXML comes pretty close though).
Ah. That depends on your definition of sane. SAX2 used to feel sane to me,
but I see you're looking for far more sanity than that.
>The initial namespace processing seems like the easy part
>to me. It's working with the output of that process that
>I find painful, for exactly the reasons listed below:
>
> > It seems like namespaces aimed at diambiguation with the "let's create big
> > long names" approach, and then had to abbreviate the big long names to keep
> > the language usable. Since then, we've had datamodels that are big (pairs
> > and triples), complex (scoped), and infectious (QNames in attribute and
> > element values).
I've decided to keep all context available all the time, subject only to
namespace declaration overrides. While that still means I have to look in
multiple places for information that used to seem simple, at least I have
my choice of coping mechanisms.
>Another model is to just use the big long names; that's
>what JDOM and SXML do. This isn't any more appealing
>to me than pairs or triples, though, and the scoping
>problems remain.
Yep. Bill de hÓra's recent piece ("Pay no attention...") tells that story
nicely.
|
