RE: Search engine

Thanks Michael for the help

I am trying to get saxon ... I will get back to you with more questions
... Currently I am looking at the documentation you put on
http://saxon.sourceforge.net/ on 1st of Oct, 2003

Cheers,

-----Original Message-----
From: Michael Kay [mailto:mhk@xxxxxxxxx] 
Sent: 12 November 2003 15:17
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE:  Search engine


XQuery is actually off-topic for this list, though I personally think it
would be a good idea to bring it on-topic. Any views, anyone?

There's a large number of XQuery implementations in various states of
completeness advertised on the Query home page at www.w3.org. If you
want something that searches terabytes of data then you're going to have
to buy a serious database product such as my own company's Tamino. If
you just want to search a single XML document, which is what your
example does, then any of the XQuery processors should handle it. In
Saxon you just do

java net.sf.saxon.Query query.xq

after putting the below query into file query.xq, in the same directory
as bib.xml.

Michael Kay



> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> SHEIKH Sajjad
> Sent: 12 November 2003 13:47
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  Search engine
> 
> 
> I have no idea how I can link my xml doc with xquery together
> or get the desired results
> 
> Any suggestion?
> 
> For example
> 
> My xml is as following
> 
> Here is my Xquery
> 
> <author_list>
>   {
>     FOR $a IN distinct(document("bib.xml")//author)
>     RETURN
>         <author>
>             <name>{ $a/text() }</name>
>                {
>                 FOR $b IN document("bib.xml")//book[author = $a]
>                 RETURN $b/title
>                } 
>         </author>
>   }
> </author_list>
> 
> 
> -----Original Message-----
> From: Michael Kay [mailto:mhk@xxxxxxxxx]
> Sent: 12 November 2003 12:26
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: RE:  Search engine
> 
> 
> XIndice is a piece of software, XQuery is a language.
> 
> If you can't tell the difference between a product and a
> language, I don't know where to start explaining.
> 
> Michael Kay
> 
> 
> > -----Original Message-----
> > From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of SHEIKH 
> > Sajjad
> > Sent: 12 November 2003 11:04
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: RE:  Search engine
> > 
> > 
> > 	Xindice vs XQuery
> > So far I am unable to find any difference.
> > 
> > I simply want a search engine like yahoo or google etc.  It will
> > search all the xml documents and return the desired node.
> > 
> > Any suggestion?
> > 
> > 
> > -----Original Message-----
> > From: Jim Fuller [mailto:jim.fuller@xxxxxxxxxxxxxxxxxx]
> > Sent: 11 November 2003 16:06
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject: RE:  Search engine
> > 
> > 
> > if your requirements are flexible, why not look into an xml
> database
> > like xindice ? It will give you XPATH querying capability
> across sets
> > of xml documents...and you can still access via webdav or http url,
> > just a thought.
> > 
> > gl, Jim Fuller
> > 
> > -----Original Message-----
> > From: SHEIKH Sajjad [mailto:Sajjad.SHEIKH@xxxxxxxxxxx]
> > Sent: 11 November 2003 14:55
> > To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> > Subject:  Search engine
> > 
> > 
> > Hi all,
> > 
> > Scenario:	
> > There are plenty of xml documents.  They are linked (href)
> with each
> > other if there is any relation. For example, first page shows 5
> > folders named f1, f2, f3, f4, f5.  Then f1 has folders and 
> files and
> > so on.
> > 
> > Objective:
> > 
> > An engine which will take user input and will return some results.
> > For example, we search for a folder f51 or we search for a document.
> > 
> > Do any of you have any idea/suggestion?
> > 
> > Thanks,
> > 
> > /s
> >  
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >  XSL-List info and archive:
> http://www.mulberrytech.com/xsl/xsl-list
> > 
> > 
> >  XSL-List
> info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> > 
> > 
> > ______________________________________________________________
> > This message has been scanned for all viruses by BTnet VirusScreen.
> > The service is delivered in partnership with MessageLabs.
> > 
> > This service does not scan any password protected or encrypted
> > attachments.
> > 
> > If you are interested in finding out more about the service, please
> > visit our website at 
> > http://www.btignite.com/internetservices/btnet/products_viruss
> creen.htm
> ==============================================================
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 
> 
> ______________________________________________________________
> This message has been scanned for all viruses by BTnet
> VirusScreen. The service is delivered in partnership with MessageLabs.
> 
> This service does not scan any password protected or
> encrypted attachments.  
> 
> If you are interested in finding out more about the service,
> please visit our website at 
> http://www.btignite.com/internetservices/btnet/products_viruss
creen.htm ==============================================================

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


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


______________________________________________________________
This message has been scanned for all viruses by BTnet VirusScreen. The
service is delivered in partnership with MessageLabs.

This service does not scan any password protected or encrypted
attachments.  

If you are interested in finding out more about the service, please
visit our website at
http://www.btignite.com/internetservices/btnet/products_virusscreen.htm
==============================================================

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