- From: Robert Waldstein <wald@library.ho.lucent.com>
- Date: Wed, 15 Nov 2000 08:23:25 -0500
- To: www-zig@w3.org
> CCLInfo: > Used to map CCL field names to attribute lists. "fields" can be > searched and/or scanned. We also support an extension to CCL > ... > > I think this category is essential in order to properly support > web forms or CCL queries with Z39.50. It gives a very simple structure If this is really needed to be done outside the "standard" set I would say we did really poorly in designing explain - since this is pretty basic; is actually one of primary reasons I require explain in my implementation. So two answers to how I do it - what I really do and what I do in the hope of one day supporting interoperability... What I really do is use "retrievalRecordDetails" - using the fact that in my set up, for the most part, field tags and attributes tags are the same. Now given this I use "PerElementDetails" to send: - a primary field name - recordTag. A number I use as an USE attribute - alternate names (e.g. 245, ti, title, mainTitle) - generic names I also, in an attempt to support clients, do "AttributeSetInfo" - it can carry an attribute primaryName and number - so I send that. Unfortunately not alternative and generic names. But think this should be enough for CCL - though haven't thoroughly understood all you sent yet... bob -- Robert K. Waldstein Email: wald@lucent.com Bell Laboratories, Room 3D-591 Phone: (908) 582-6171 600 Mountain Avenue Murray Hill, New Jersey 07974
Received on Wednesday, 15 November 2000 08:23:32 UTC