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  July 2003

ZNG July 2003

Subject:

Re: 1.1: Scan

From:

Robert Sanderson <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Tue, 29 Jul 2003 22:39:38 +0100

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (136 lines)

On Tue, 29 Jul 2003, LeVan,Ralph wrote:

> But, the discussion (at the link) points out the need to separate the term
> and the index, rather than confuse things with the full CQL term, including
> relation.  But, the relation implies the structure.  So, we'll need that
> somehow.

Yes.  Trawling through the previous discussion, it came down to:

Matthew originally proposing use of searchClause.
Rob starting with index and term, then switching to searchClause, but
wondering what the other relations were to be interpreted as.
Ralph suggesting that the only meaningful distinction was keyword vs
string.
Rob suggesting that stem was a valid relation modifier but not being very
sure about it.

What happens about the indexes of dimensioned terms (range/area/volume)
and scan?  For example the geo searches?  I think we'll need Mike's term
describing relation qualifiers so that the server knows how to interpret
the term at all?

> Now, the real question is; what is the "clause" in your ScanRequest, Rob?

A search clause string in cql.  xClause being XCQL.


I'm not very sure about the TermReference structure... I think the idea
was that the database would be an SRW database that respected Mike's ZThes
indexSet... but are people happy with that restriction, otherwise we need
to give a full search clause (which in my mind is too heavy to attach to
every single term)?

The other option suggested was that the server URL etc should be in the
Explain record in a named <link> ... that would cut out having to repeat
it ad nauseum on every response.

Rob


> > -----Original Message-----
> > From: Robert Sanderson [mailto:[log in to unmask]]
> > Sent: Tuesday, July 29, 2003 12:09 PM
> > To: [log in to unmask]
> > Subject: 1.1: Scan
> >
> >
> > To refresh, what we were thinking on Scan:
> >
> > http://listserv.loc.gov/cgi-bin/wa?A2=ind0301&L=zng&F=&S=&X=49
> > 9A0A17B318735D41&[log in to unmask]&P=1930
> >
> > and subsequent.
> >
> >
> > Issues I can find that are outstanding:
> >
> > > Things which would be useful which Theo (IIRC) brought up:
> > Some sort of
> > > marker for where the term would be if it's not present, or
> > that the term
> > > is the one used from the request.
> >
> > Which would also fill:
> >
> > > If we were to contemplate something equivalent to step size, I
> > > would propose a collapsed element and leave the server to
> > interpret its
> > > meaning.
> >
> > and:
> >
> > > 241  Scan: Beginning or end of term list
> > > Is 241 a surrogate diagnostic? If so, should we have some
> > facility for
> > > including a marker for the beginning/end of the list as well as the
> > > supplied term?
> >
> > Either, we can have a list of mixed object types (Please No, this will
> > play hell with implementations, I fear) or we need to allow
> > some sort of
> > diagnostic to be attached to the term structure as a surrogate term.
> >
> > eg:
> >
> > <term>
> >   <diagnostics>
> >     <diagnostic>
> >        <code>150</code>
> >        <details>Start of TermList</details>
> >     </diagnostic>
> >   </diagnostics>
> > </term>
> >
> > Then the list of surrogate diagnostics for scan would be:
> >   Start of TermList, End of TermList, Requested Term Position.
> >
> > This means that all of the parameters for <term> need to be
> > optional, but
> > our prose says 'you must return at least one of value and diagnostics'
> >
> >
> > My current structure (without the above per term diagnostics):
> >
> > ScanRequest:
> >   clause             String
> >   xClause            xcql:SearchClause type
> >   numberOfEntries    Integer
> >   responsePosition   Integer
> >
> >
> > ScanResponse:
> >   terms              List of ScanTerm type
> >   diagnostics        Diagnostic type
> >   echoedRequest      ScanRequest type  (for SRU)
> >
> > ScanTerm:
> >   value              String       (value of the term)
> >   frequency          Integer      (number of occurences)
> >   displayTerm        String       (term to display instead of value)
> >   references         List of TermReference type (pointers to thesauri)
> >
> > TermReference:
> >   thesaurus          String   (name.. eg 'lcsh' 'unesco')
> >   server             String   (URI to SRW/U server)
> >   useTerm            String   (term to use in search if different)


--
      ,'/:.          Dr Robert Sanderson ([log in to unmask])
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Nebmedes:  telnet: nebmedes.o-r-g.org 7777
____/:::::::::::::.                WWW: http://nebmedes.o-r-g.org:8000/
I L L U M I N A T I

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