W3C home > Mailing lists > Public > www-zig@w3.org > February 2002

Re: Z39.50 on the web (and in print)

From: Robert Sanderson <azaroth@liverpool.ac.uk>
Date: Fri, 22 Feb 2002 23:09:00 +0000 (GMT)
To: Sebastian Hammer <quinn@indexdata.dk>
cc: Mike Taylor <mike@tecc.co.uk>, <www-zig@w3.org>
Message-ID: <Pine.LNX.4.33.0202222256520.29731-100000@gondolin.hist.liv.ac.uk>

> So is the assumption that this model would be used both for servers 
> describing themselves and for Friends & Neighbours? My exhuberant comment 

I would expect that only the <serverdetails> would be wanted for friends 
and neighbours.

> to Mike was intended to yield a F&N scheme first. Yours seems more 
> Explain-oriented (but in a good way).

Right, the thread has split many ways from Sunday.  This is definitely 
more Explain than F&N.



> >   <indexdetails>
> >      <index search="true" scan="true" sort="true" id="ghlau-mailarchive-1">
> >        <name>author</name>
> >        <title lang="en" primary="true">Author</title>
> >        <type>author</type>
> >        <map attributeset="BIB-1" primary="true">
> >           <use>1</use><posit>3</posit> <struct>6</struct>
> >        </map>
> >      </index>


> kind of description "dumbing down" to the level where it just asserts that 
> this and this and this attribute (combination) is valid on the server, and 
> leave the client to figure out what they are. What I'm after, I guess, is a 
> record that can be simple enough that it can be produced from the outside 
> using automated probing or manual testing...

Certainly.  Making name, title and type optional in the schema would be a 
good start.  Name could probably be thrown out completely even. Type is 
just a convenient way for me to group similarly inclined records together 
automatically. 

Title could be looked up in a Long List of attribute combinations and 
would be right most of the time I guess.

ID, like type, is just a convenient way of locating them in a federated 
database, and would probably be assigned by the federator.

Title and Type are in there for when you -can't- look them up, for example
with attribute architectured searches against databases of collectable
card game cards.

So a minimal version might be:

<indexdetails search="true">
  <map attributeset="BIB1">
    <use>1</use>
  </map>
</indexdetails>



Rob

-- 
      ,'/:.          Rob Sanderson (azaroth@liverpool.ac.uk)
    ,'-/::::.        http://www.o-r-g.org/~azaroth/
  ,'--/::(@)::.      Special Collections and Archives, extension 3142
,'---/::::::::::.    Twin Cathedrals:  telnet: liverpool.o-r-g.org 7777
____/:::::::::::::.              WWW:  http://liverpool.o-r-g.org:8000/
I L L U M I N A T I
Received on Friday, 22 February 2002 18:12:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:27 UTC