LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  January 2007

ZNG January 2007

Subject:

Re: SRU Version 1.2 draft specification

From:

"Edward C. Zimmermann" <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Thu, 25 Jan 2007 14:35:35 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (77 lines)

Quoting Mike Taylor <[log in to unmask]>:

> 
> What was the motivation for CQL change 7?

I hope reason and .. :-)

> 
> 	Proximity. Defaults are now server defined, not standard
> 	defined. Hence "prox" can be anything the server wants to do
> 	proximately, not necessarily with a default of adjacency.
> 
> I think I missed that discussion.

But you were there :-)

What is:

search prox//20 engine. For a text such as

<project>Geospatial Search</project>
<program>IB Engine 3.x</name>

Its a messy bit. Engine and Search are not in the same container in this
model. In another model, since we don't have an order explicitly in XML
(recall my mail a month or two back) we can't even talk about (in a
non "do it the way I want to" manner) the distance between (to use football
as in your taste)

<item>Manchester United</item>
<item>Arsenal</item>
<item>Tottenham Hotspur</item>
<item>Liverpool</item>
<item>Aston Villa</item>

How far is Arsenal from Tottenham Hotspur (beyond the distance between their
stadiums in town) when we have no warrants that the data is so marked up or
can (at this stage) call to document order or for that matter, define a
model transcendent of systems for a document order or even an encoding (we
can't and don't demand that its marked up as XML or ...)?

And adj? Is United (keeping even to document order) adjacent to Arsenal?

Should proximity be only restricted to a single contextual container or
envelope? Then we'd not have the idea of paragraph, sentence, line, chapter
etc. which are models to cover a document and transcend perhaps the markup.
Recall a line may contain one or more (or not even one) sentences. A sentence
may cover multiple lines. 

I also wrote about the issue of "word". What's word metrics? In some systems
it can make sense but in many it can't. If we don't know that we're talking
about the same thing then we might as well just let people talk the why they
think is best and makes the most sense and hope that some form of communication
takes place.  

At this stage its best really to let the server make their own policies.

--- and in 2.0 my interest is to talk about the model of ancestor and
descendants of a match (hit) within a document (makes quite a lot of sense
in the OASIS context) to break away from our current fixed (pre-defined)
record model to a search directed model (recall my suggestion a few months
back). Again, I've already implemented this and so its not just dry
theory. I can show in praxis how this works.. and what kinds of problems
it "solves". Its the kind of functionality, I think, looking at the talk
of Xquery (which has shown itself to be terribly insufficient for drawing
up a model for "fulltext XML search") that could make SRU/W blow away the
rest of the "generic search protocol" playing field. 


-- 
-- 
Edward C. Zimmermann, Basis Systeme netzwerk, Munich
Office Leo (R&D):
   Leopoldstrasse 53-55, D-80802 Munich,
   Federal Republic of Germany
http://www.nonmonotonic.net

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager