[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: nested namespaces
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. dareo@m... (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" >xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> > ><xsl:template match="//*[namespace-uri()='http://example.com/b']"> > <xsl:value-of select="name()" /> <xsl:apply-templates /> ></xsl:template> > ></xsl:stylesheet> > >or > >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 >needed. -- Simon St.Laurent Ring around the content, a pocket full of brackets Errors, errors, all fall down! http://simonstl.com -- http://monasticxml.org
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|