What's the use case?  I seem to remember sitting in Hotel bar in the
Hague with you, Rob and I think Matthew, and concluding that this was
a red herring.

(Also: is that really how the bibliographic searching profile ended
up?  Oh dear.  But I'm not going to get involved in that.)

 _/|_	 ___________________________________________________________________
/o ) \/  Mike Taylor    <[log in to unmask]>    http://www.miketaylor.org.uk
)_v__/\  "I have heard the Big Music and I'll never be the same" --
	 The Waterboys, "The Big Music"



Ray Denenberg, Library of Congress writes:

 > Part of the SRU bibliographic profile work we're talking about
 > would address searching on OpenURL keys.  There is an initial set
 > of keys for consideration at
 > http://www.loc.gov/standards/sru/openurlkeys.html and from that set
 > we want to determine a subset of keys that we really want to search
 > on.  Then we want to map indexes from the bib set to these keys,
 > defining additional modifiers if necessary.
 > 
 > So for example say you want to search on 'aulast' (authors last name).
 > 
 > First, note that the way to search on author is suggested by the
 > example in the bib set proposal,
 > http://www.loc.gov/standards/sru/cql-bibliographic-searching.html
 > 
 > bib.NamePersonal=/bib.role=author/bib.roleAuthority=marcrelator "George
 > Orwell"
 > 
 > So to search on authors last name, we could add another modifier.
 > Let's call it (for example sake) sap.namepart=last (where 'sap' is
 > for San Antonio Profile - the last time we talked about this we
 > used openurl as the prefix but Herbert suggested sap instead).
 > 
 > Thus:
 > 
 > bib.NamePersonal=/bib.role=author/bib.roleAuthority=marcrelator/sap.namepart
 > =last  "Orwell"
 > 
 > I'd like comments and ideas on this approach.
 > 
 > --Ray