Hi Sanjaya, "//" [1] is a short form for the descendant or self axis, meaning it selects any descendants which match the following part of the expression not just the immediate children. It doesn't make a difference for the example you posted because every "book" is an immediate child of "bookstore", but if the document had been:
<bookstore> <someotherelement> <book> <title lang="eng">Harry Potter</title> <price>29.99</price> </book>> </someotherelement> </bookstore> only the bookstore//book expression would select the "book" element. The bookstore/book expression would not select anything in this document since there is no "book" child immediately under "bookstore". Hope that makes sense. If you have more general questions about XPath the XSL Mulberry mailing list [2] is a very good resource and would encourage you to join it and also have a look in its archives. Thanks. [1] http://www.zvon.org/xxl/XSLTreference/Output/axis_descendant-or-self.html [2] http://www.mulberrytech.com/xsl/xsl-list/ Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [email protected] E-mail: [email protected] Sanjaya Liyanage <[email protected]> wrote on 03/09/2010 04:24:43 AM: > Hi Michael, > First of all thank you very much for your reply and it > really encouraged me.I already began to go through the Xpath as > Xpointer is also built on xpath expressions.I refer w3school site( > http://www.w3schools.com/xpath/default.asp) for gaining knowledge on > xpath.But I came across a doubt about the expressions ' / ' and ' > // ' .What is the difference between these two expressions. > The example they use is, > <?xml version="1.0" encoding="ISO-8859-1"?> > > <bookstore> > > <book> > <title lang="eng">Harry Potter</title> > <price>29.99</price> > </book> > > <book> > <title lang="eng">Learning XML</title> > <price>39.95</price> > </book> > > </bookstore>. > > As they mention> > > expression Result> > > bookstore/book > > Selects all book elements that are children of bookstore > > bookstore//book > > Selects all book elements that are descendant of the bookstore > element, no matter where they are under the bookstore element > > Can you please give me the idea? > > thank you > sanjaya > > On Tue, Mar 9, 2010 at 10:20 AM, Michael Glavassevich <[email protected] > > wrote: > Hi Sanjaya, > > Welcome to the mailing list and thanks for your interest in Xerces. > > The XPointer project on the idea list from last year is still open > if you'd like to work on it. Aside from becoming familiar with the > relevant specifications I'd recommend taking a look at the existing > XInclude / XPointer implementation in Xerces as well as the XPath > support that is already in place. > > Feel free to ask questions here if you have any. > > Thanks. > > Michael Glavassevich > XML Parser Development > IBM Toronto Lab > E-mail: [email protected] > E-mail: [email protected] > > Sanjaya Liyanage <[email protected]> wrote on 03/03/2010 11:33:38 PM: > > > > Hi, > > I am so much interested about the project "Implement a > > streamable subset of the XPointer xpointer() scheme for XInclude" > > with subject id "xerces-xinclude-xpointer-enhancements" @ Gsoc > > 2009 idea list.I had a determination to develop a xml parser by my > > own when I use libxml for one of my projects(When I tried to create > > a plug-in to Anjuta) and I think this Gsoc project will be a great > > chance to gain a knowledge which may be helpful to achieve my > > determination one day. > > In these days I am paying my > > attention to XPointer Framework and XPointer element() to have an > > idea about how the Xinclude requirement are satisfied present > > time.I hope this project idea will remain for Gsoc 2010 and please > > let me know if you know anything that can be helpful me to create a > > proper background knowledge before the projects are really getting > > started.Thank you all. > > > > regards > > Sanjaya Liyanage.
