- From: Nicolaides,F <F.Nicolaides@lse.ac.uk>
- Date: Wed, 9 Jul 2003 08:55:53 +0100
- To: <www-zig@w3.org>
- Cc: "Gilby,J" <J.Gilby@lse.ac.uk>
No, Ashley, I heard the same thing!! ____________________________ Fraser Nicolaides, Projects Officer M25 Systems Team Rm. R302, Library London School of Economics 10 Portugal Street London WC2A 2HD Tel.: 020 7955 6454 E.: f.nicolaides@lse.ac.uk ____________________________ -----Original Message----- From: Ashley Sanders [mailto:zzaascs@IRWELL.MIMAS.AC.UK] Sent: 08 July 2003 14:27 To: www-zig@w3.org Subject: Re: The imprecision of Z39.50 Mike Taylor wrote: > > Type 2: Search type. Just 11 values defined in this -- the > > search types numbered 1 to 11 above. > > Aha-haha! That's very cute :-) > > Unfortunately, this approach can't work for the Bath profile, Oh yes it can! > whose job is very much to codify and add rigour to existing practice. You should have been at the Bath Profile meeting yesterday where it was suggested that something like the Bath Profile was needed that was technology independent. Someone please correct me if I've got this wrong, but I think it went something like this: Strip out the z39.50 specific bits of Bath and leave just the definitions of the types of search and index browsing that real users want to do. The resulting meta-Profile can then be used to derive specific technology dependent profiles -- so a z39.50 version, a Web Services version, etc, etc. Rather like the relationship between your ZOOM abstract API and the specific language bindings of it. Rather a good idea I thought. But maybe there were some eddies in the space-time continuum around my chair and I heard it all differently. > Interestingly pragmatic approach, though. Thanks! Ashley. -- Ashley Sanders a.sanders@mcc.ac.uk COPAC: A public bibliographic database from MIMAS, funded by JISC http://copac.ac.uk/ - copac@mimas.ac.uk
Received on Wednesday, 9 July 2003 03:55:59 UTC