This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Re: XSL-List Digest V3 #1158


Hi Avani,
see the prefix is a place-holder for the uri.It is provided so that you 
dont have to write lengthy node names.
you use the prefix to identify a node like this :

<xsl:value-of select = "xyz:nodename"/>
if you use the uri then the uri contains characters which have special 
meaning in XPath. for e.g.. <</>> identifies root node.


Manu
>Thank You Manu,
>
>    Now suppose that I have a namspace xmlns:xyz="www.xyz.com"
>
>  I can use the prefix xyz to give -:    child::xyz:name   (this is the node
>test prefix:name)
>but
>  giving  an XPATH like -:      child::"www.xyz.com":name   (is this what
>URI:name  mean?) gives an error in many XSLT processors.
>
>Please send an example  for illustration.
>
>Avani
>
>----- Original Message -----
>From: XSL-List Digest <owner-xsl-list-digest@lists.mulberrytech.com>
>To: <xsl-list-digest@lists.mulberrytech.com>
>Sent: Tuesday, October 09, 2001 12:00 PM
>Subject: XSL-List Digest V3 #1158
>
>
> > XSL-List Digest       Tuesday, October 9 2001       Volume 03 : Number
>1158
> >
> >
> >
> > In this issue:
> >
> >      [xsl] THE NODE TEST URI:name
> >      Re: [xsl] THE NODE TEST URI:name
> >      Re: [xsl] Frames
> >      [xsl] Problem with not() function.
> >      RE: [xsl] Frames
> >
> > ----------------------------------------------------------------------
> >
> > Date: Tue, 9 Oct 2001 11:05:24 +0530
> > From: "Avani Goel" <avani_goel@persistent.co.in>
> > Subject: [xsl] THE NODE TEST URI:name
> >
> > I have not been able to understand what does this node test  URI:name
> > imply.
> >
> > I saw it in the  XSLT and XPATH Quick Reference at Mulberrytech.com
> >
> > Please can somebody elicit upon this.
> >
> >
> >
> >
> >  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> >
> > ------------------------------
> >
> > Date: Tue, 09 Oct 2001 11:31:13 +0530
> > From: Manu KY <manu_kry@yahoo.com>
> > Subject: Re: [xsl] THE NODE TEST URI:name
> >
> > Hi Avani,
> > the node test means test for a node whose name matches the name
> > "URINamespace:name".
> > the test for a node in an expression is given in following syntax:
> >
> > AxisSpecifier  NodeTest(Name OR Type)  Predicates
> >
> > check XSLT programmer's reference.. By Michael Kay ,Wrox  Publications for
> > more.
> > Its the BEST book on XSLT.
> >
> > Manu
> > >I have not been able to understand what does this node test  URI:name
> > >imply.
> > >
> > >I saw it in the  XSLT and XPATH Quick Reference at Mulberrytech.com
> > >
> > >Please can somebody elicit upon this.
> > >
> > >
> > >
> > >
> > >  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> >
> >
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> >
> >
> >  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> >
> > ------------------------------
> >
> > Date: Tue, 9 Oct 2001 13:51:40 +0800
> > From: "Rafael 'Dido' Sevilla" <sevillar@team.ph.inter.net>
> > Subject: Re: [xsl] Frames
> >
> > On Mon, Oct 08, 2001 at 06:18:24PM -0700, Lakshmi Anantharaman wrote:
> > > How to use get xml that shall display a frame containing two other xmls
> >
> > You'll need to use some non-standard extensions to do this.  If I
> > understand correctly, what you want to do is with two XML source
> > files come up with an HTML frameset that contains the same information
> > in the XML sources.  This means you have to get data from your two XML
> > source files and generate three output HTML files, one the framing file,
> > the other two, your formatted HTML that should appear in the frames.
> >
> > To do the first part, you need to use the document() function, see
> > Section 12.1 of the XSLT Recommendation.  To do the second part, you
> > need to use either the non-standard extensions in your XSLT processor
> > (e.g. Xalandirect), or the <xsl:document/> construction in the XSLT 1.1
> > Working Draft if your XSLT processor supports it (Saxon does, I
> > believe, anyone have any info on the status of this feature in other
> > XSLT engines?).  See Section 16.5 of the XSLT 1.1 Working Draft for more
> > information on how that works.  The example given in that section of how
> > to use <xsl:document/> is also very similar to what your problem looks
> > like.
> >
> > - --
> > Rafael R. Sevilla <sevillar@team.ph.inter.net>   +63(2)   8177746 ext.
>8311
> > Programmer, Inter.Net Philippines                +63(917) 4458925
> > http://dido.engr.internet.org.ph/                OpenPGP Key ID:
>0x5CDA17D8
> >
> >  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> >
> > ------------------------------
> >
> > Date: Tue,  9 Oct 2001 13:51:49 +0800
> > From: Ling Kok Choon  <kokchoon@brel.com>
> > Subject: [xsl] Problem with not() function.
> >
> > Hi,
> >
> >    I meet a problem when use not function in the xsl. I use not function
>in the select statement
> > to filter out some node.
> >
> >    The code is :
> >
> > ...
> > ...
> > <xsl:template match="sub-title">
> >    <xsl:apply-templates select="*[not(self::para[1]) and not(self::title)
>and
> > not(self::graphic[1])]" />
> > </xsl:template>
> > ...
> > ...
> >
> > i need to filter out the para[1] node , the title node and the graphic[1]
>node.
> >
> > the xml is :
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> >
> > <Document>
> > ...
> > ...
> > <sub-title>
> > <title>"Bluetooth" Wireless Home Control Center</title>
> > <para>Some text here 1.</para>
> > <para>some text here 2.</para>
> > <para>some text here 3.</para>
> >
> > <graphic>
> > <title/>
> > <pic><para>pic/eln/bluetooth01.jpg</para></pic>
> > </graphic>
> > </sub-title>
> > ...
> > ...
> > </Document>
> >
> >
> > What i am not sure is the title and graphic[1] is filter out form the
>select statement, but the
> > para[1] filter out all the <para> and not the first <para>.
> >
> > Do u have any idea ?
> >
> >
> > Thank you.
> >
> >
> >
> > Regards,
> >
> > Kok Choon.
> > - --------------------------------------------------------
> > Name: Ling Kok Choon
> > E-mail: Ling Kok Choon <kokchoon@brel.com>
> > Date: 10/09/01
> > Time: 13:51:49
> >
> > This message was sent by Z-Mail Pro - from NetManage
> > NetManage - delivers Standards Based IntraNet Solutions
> > - --------------------------------------------------------
> >
> >
> >  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> >
> > ------------------------------
> >
> > Date: Tue, 9 Oct 2001 09:19:20 +0300
> > From: Jarno.Elovirta@nokia.com
> > Subject: RE: [xsl] Frames
> >
> > > (e.g. Xalandirect), or the <xsl:document/> construction in
> > > the XSLT 1.1
> > > Working Draft if your XSLT processor supports it (Saxon does, I
> > > believe, anyone have any info on the status of this feature in other
> > > XSLT engines?).
> >
> > jd.xslt <http://www.aztecrider.com/xslt/> implements XSLT 1.1 WD.
> >
> > Jarno
> >
> >  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> >
> > ------------------------------
> >
> > End of XSL-List Digest V3 #1158
> > *******************************
> >
> >
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]