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 2005

ZNG January 2005

Subject:

Re: context set for gis

From:

Mike Taylor <[log in to unmask]>

Reply-To:

Z39.50 Next-Generation Initiative

Date:

Tue, 11 Jan 2005 12:15:40 GMT

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (52 lines)

> Date: Tue, 11 Jan 2005 10:53:28 +0000
> From: Dr Robert Sanderson <[log in to unmask]>
>
> > I believe that Mike Taylor has concerns about mapping multiple
> > index names to the same semantics, though apparently that is
> > considered OK in the case of "author/creator" and is also OK if
> > the index names are in different context sets. In GILS, we do have
> > a few instances where multiple names are needed for the same
> > abstract concept.
>
> For the record, I agree with Mike's concerns.  It would be better if
> you just picked one name for each index, as then there's no decision
> to be made by people using the context set as to which name(s) to
> support.  Nor requiring clients to try and support all of the
> different names.

Also for the record (thank, Rob!) Eliot is incorrect in supposing that
I think it's OK for CQL indexes in different context sets to have
different names.  Far from it: as a matter of Good CQL Citizenship,
anyone defining a new context set should take pains to ensure that
they do not duplicate the semantics of an index already defined
elsewhere.  This is why, for example, the Bath Profile for SRW at
        http://zing.z3950.org/srw/bath/2.0/
does not define a "title" element in its "bath" context set, but
instead describes how "dc.title" should be used.

(Note that a specific server interpretation may, due to inadequacies
of its data model, end up interpreting multiple indexes in the same
way; but that is not the same thing as the indexes being _defined_
identically.  To take a topical example, a server might well implement
cql.serverChoice and cql.anywhere using the same internal index, but
that doesn't change the fact that in principle they are defined
differently.)

Finally, the case of author/creator is regrettable, but I don't think
there is any point in trying to hold back the tide on that one.  The
whole world uses these index names interchangably, and we must either
acquiesce or spend our lives fielding "bug reports" from uses who want
to know why our servers don't support author-searching.

 _/|_    _______________________________________________________________
/o ) \/  Mike Taylor  <[log in to unmask]>  http://www.miketaylor.org.uk
)_v__/\  "If Microsoft Word had been around 400 years ago, Martin
         Luther would never have got around to nailing his thesis
         to the church door.  He'd have spent the evening messing
         around with the font size and found out the next day that the
         Reformation had broken out without him" -- Andrew Rilstone.

--
Listen to free demos of soundtrack music for film, TV and radio
        http://www.pipedreaming.org.uk/soundtrack/

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