Lists Home |
Date Index |
The best practice is not to design your XML in such a boneheaded manner
in the first place not coming up with overcomplicated rules of how to
PITHY WORDS OF WISDOM
Freebees will only arrive at work on your days off.
This posting is provided "AS IS" with no warranties, and confers no
> -----Original Message-----
> From: Simon St.Laurent [mailto:firstname.lastname@example.org]
> Sent: Monday, December 16, 2002 6:50 AM
> To: email@example.com
> I'm well aware that there _are_ ways to process these things.
> (In SAX, all things are possible, or most things, anyway.)
> My question is the relationship between can and should. We
> seem to be short of a few best practices in this zone, and I
> worry that a lot of people take this kind of thing for granted.
> If there's an area of namespace practice that needs further
> exploration, it's most likely how best to mix and mingle
> parts from different namespaces in widely-distributed
> vocabularies, not just how to process particular minglings in
> particular environments.
> firstname.lastname@example.org (Dare Obasanjo) writes:
> >I'm sorry but I can't see what problem it is you are
> stating. If I was
> >processing your latter XML document and needed only elements
> from the
> >"http://example.com/a" namespace I'd write
> ><xsl:stylesheet version="1.0"
> ><xsl:template match="//*[namespace-uri()='http://example.com/b']">
> > <xsl:value-of select="name()" /> <xsl:apply-templates />
> >declare namespace a = "http://example.com/a"
> > let $i := document("container.xml")
> > return for $a in $i//a:*
> > return name($a)
> >substituting the call to name() with whatever processing code was
> Simon St.Laurent
> Ring around the content, a pocket full of brackets Errors,
> errors, all fall down!
> http://simonstl.com -- http://monasticxml.org
> The xml-dev list is sponsored by XML.org
> <http://www.xml.org>, an initiative of OASIS
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>