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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  December 2006

ZNG December 2006

Subject:

More ZINGing on the simple model for element of retrieval

From:

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

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Fri, 8 Dec 2006 11:46:37 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (92 lines)

Partitioning:

Let me see if I can make the point a bit easier.

In searching for a query there are the records matching the specification and
the coordinates of the match within the records in the document space.

Each of these "hit" coordinates is somewhere within the document tree.

With a named path one can identify the ancestor in the tree of a hit.

(using the Shakespeare XML again)
<PLAY>
  ...
 <ACT>
   ...
     <SCENE>
       ...
        <SPEECH>
          <SPEAKER>LADY MACBETH</SPEAKER>
            <LINE>Out, damned spot! out, I say!--One: two: why,</LINE>
            <LINE>then, 'tis time to do't.--Hell is murky!--Fie, my</LINE>
            <LINE>lord, fie! a soldier, and afeard? What need we</LINE>
            <LINE>fear who knows it, when none can call our power to</LINE>
            <LINE>account?--Yet who would have thought the old man</LINE>
            <LINE>to have had so much blood in him.</LINE>
        </SPEECH>
  ...
</PLAY>

The "spot" in line is in "LINE" (PLAY\ACT\SCENE\SPEECH\LINE). The line
is "Out, damned spot! out, I say!--One: two: why,". Its in a speech
the speech is the above fragment. Its in a scene, its content is the set
of all speeches in that scene including this one where "out" and "spot"
was said in the same line. etc. etc. etc.

At any point going up the tree from one of my hit coordinates I may also
ask for the content of any of the descendants of a named ancestor, to the
extent that it has any children. LINE, for instance, is a final leaf and
has none.

The ancestor SPEECH of my hit "spot" in the "out" and "spot" in the same
LINE is the above speech. Its LINE descendants are the LINES above. Not
just the one line but all 6 of them. The SPEAKER descendant is the content
of "SPEAKER" and that's LADY MACBETH.

We may also map these coordinates to offsets of storage of the document as
a serial object on the disk, viz. the "document order". This mapping lets
us order the list of these coordinates as per the document order to give
us next and previous among the siblings.

By selecting a path for ancestor and a path of a descendant of that ancestor
of a hit (node) and with an order of hits (previous/next) we have, I suggest,
an easy to express and sufficient model of search segmentation for the concept
of unit of retrieval for "result".

Since we no longer have the restriction of OIDs for element retrieval we
can encode this within the named element retrieval as string.

In RSS search if I'm interested in items (which I am) and not feeds as my
element of retrieval then if I want to get an Ancestor ITEM (as ..\channel\item)
and to follow the link to the story I want that ancestor's LINK and TITLE
descendant elements. For a brief summary I maybe want the DESCRIPTION element
of the particular ITEM etc.

If my search query matched say some text in the TITLE element of a CHANNEL
and not any item then I don't have an ITEM for that hit. But I have, should
the user request it, a channel.

This makes sense since I may ask questions like? What news stories has BBC
currently in their top feed in contrast to what news stories are currently
talking about BBC. The questions are different (why we have contextual search)
but also the intended element of retrieval is different.

Its so simple to express and yet delivers, I think, exactly what we want, resp.
need.

Counter-examples anyone?




--
--
Edward C. Zimmermann, Basis Systeme netzwerk, Munich
Office Leo (R&D):
   Leopoldstrasse 53-55, D-80802 Munich,
   Federal Republic of Germany
Telephone: Voice:= +49 (89) 385-47074 Corp.Fax:= +49 (89) 692-8150
 Nomadic (SMS/MMS/Fax):= +49 (176) 100-360-55 Alt.Mobile:= +49 (179) 205-0539
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