Skip to main content.
home | support | download

Back to List Archive


From: Roy Tennant <roy.tennant(at)>
Date: Thu Nov 16 2000 - 20:42:30 GMT
To me, the problem with SWISH-E and XML is not the searching, but the 
results. What you would get back is that a given file matches your 
search, *not* each XML segment that matches and the URL of the file 
from which it was extracted (which is more like what I want). So 
that's why I'm looking at other things to search XML content (like 
sgrep) rather than use SWISH-E. To make SWISH-E really work the way I 
want it to, there would need to be a module that could extract 
relevant segments from files that match.

At 11:28 AM -0800 11/16/00, wrote:
>Some people have asked me for improving XML indexing.
>I am not an expert of XML, so I would like to hear from all of you.
>This what XML does now in 2.1.x:
>it index thinks like:
><element> some data </element>
>and also
><element1> some data <element2> other data </element2>
>even more data</element1>
>You can search both element1=other and element2=other
>This is what I think it is easy to do:
>- Index comments <!- -> ignoring the rest of <!..>
>- Ignore <? ..>
>- Index properties:
><element1 prop1="some data"> other data</element1>
>In this case you can search for element1=some and prop1=some
>- Ignore empty elements: <element/> but index its properties:
><element1 prop1="some data" />
>In this case you can search for element1=some and prop1=some
>- Sorry, no DTDs
>Am I in the right way?
Received on Thu Nov 16 20:44:07 2000