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  May 2002

ZNG May 2002

Subject:

Re: Betr.: Ralph's Premises

From:

Theo van Veen <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Fri, 17 May 2002 10:24:00 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (38 lines)

Although I already mentioned, that I agreed with Mike's suggestion and intended to be quiet on this subject as it seems to be agreed not to mandate prefixes, I give one more reaction.

On 16 May 02, at 16:46, Ray Denenberg wrote:

> "LeVan,Ralph" wrote:
>
> > Sorry, but the ZIG has spent the last five or six years recovering from the
> > problems caused when we originally did that. Clients would sent me an
> > Author search. I didn't have an Author index, but I did have a Names index.
> > So I turned the Author search into a Name search because bad results are
> > better than no results.
> >
> > The ZIG played with the idea of semantic switches that would permit or
> > forbid that kind of stuff and we have finally settled on flat forbidding it.
> > Let's not recapitulate that process in SRW!
>
> That's convincing enough for me, and I retract my earlier acceptance of the idea
> of a non-prefixed list. I would go so far as to support the idea that a prefix
> need not be mandated by the cql syntax, but is encouraged, and that we give no
> guidance whatever about what to do if there is none, and that we don't define a
> list of non-prefixed indexes.
>
> --Ray

Ralph's example does not apply on the prefix discussion. If a server finds that it should call its name-index a name-index and not the author-index, it has its reasons for it and it is up to the server to
determine if its name-index is to be considered identical to an author-index or not. When the client doesn't know, the use of prefixes does not solve this problem. CQL does not allow the client
to say "I don't care whether it is bath or dc or whatever, just give me the author".

I never considered attributesets as mechanisms to modify the meaning of access points but more as a mapping of numbers and access points. And I also did not consider profiles as a mechanism
to modify the meaning of an access point but more as an agreement on which attributes are to be supported by all partners supporting a certain profile. Mixing prefixes for namespaces(dc), profiles(bath) and attributesets(Bib1) in access points is in my view in cross domain searching not the solution of a problem but the introduction of a interoperability problem. Clients and servers have to be aware of other new introduced prefixes to be able to determine whether access points are identical or not. When the prefix is needed to modify the meaning of the index name than - in most cases - the index name wasn't a good choice.

I think it is agreed that prefixes are not mandated and all the risc of ambiguity is at the client side when it does not add prefixes. I can live wiith that and will become quiet on this subject now.

PS.
There is one suggestion to be made with respect to future functionality on this issue. As soon as we introduce "scan", it would be nice when a search for an unprefixed term could OPTIONALLY return the index names for which a search term is available. It is then up to the user to decide how to proceed and he becomes aware of access points that were previously unknown to him but could be very helpfull.

Theo

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
https://listserv.loc.gov/cgi-bin/wa?A2=ind0205&L=ZNG&D=0&P=79393&F=P
listserv.loc.gov
CC-MAIN-2023-23
52221
application/http; msgtype=response
sha1:ZQJ3JBMAUZ2Z7W3SNML6NMBDJIMECGN2
<urn:uuid:374152fd-d2be-46ba-ac1d-af15003ee31e>
2023-05-28T11:06:01Z
104.16.55.16
text/html
sha1:APHXBCDKYKGU45BH5SBZEF3433MHRF7R
<urn:uuid:0a4334f3-3d41-4137-bbf5-b417c2b2c82a>
https://listserv.loc.gov/cgi-bin/wa?A2=ind0205&L=ZNG&D=0&P=79393&F=P
response
<urn:uuid:23a62e1d-8e72-4d9f-a5c1-de65e5d6354c>
isPartOf: CC-MAIN-2023-23
publisher: Common Crawl
description: Wide crawl of the web for May/June 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-247
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.4-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/