- From: Robert Sanderson <azaroth@liverpool.ac.uk>
- Date: Sat, 20 Apr 2002 23:40:39 +0100 (BST)
- To: Sebastian Hammer <quinn@indexdata.dk>
- cc: www-zig@w3.org
> Technically, the Path Expression would have to go into the "Complex" branch
> of the attributeValue, as a single string value, thus requiring support for
Can you explain how one would say that the ComplexAttributeValue is to be
treated as an XPATH as opposed to any other string?
> model into one that is suitable to Z39.50.. either by mapping elements
> (more or less) to Bib-1 attributes, or by declaring new, flat sets of
> numerical USE attributes... in either case, a process which introduces
This is a particular issue with document fragments. For example one might
want to have records which comprise the text of an entire book. However
retrieving the entire text at once is not useful. Important functionality
is to be able to retrieve matching document fragments, whilst maintaining
the ability to search against the entire record.
For example:
Find pages matching 'Frodo' and ('Aragorn' or 'Strider') in books with the
author 'Tolkien, J.R.R.'
> It'd be useful to consider extending the Type-1 query to allow the use of
> an URI instead of an OID to denote the "attribute set". You will most
> likely want to mix and match the two type of identifiers -- there's no
> clear reason to abandon the Utility attribute set for the non-USE attributes.
I think that the recent decision to use URIs for schemas in
elementsetnames is a good first step towards this.
Perhaps we ought to rethink 12 months as the next ZIG and put it back to
6?
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 Saturday, 20 April 2002 18:46:31 UTC