Re: Requesting XML records via Z39.50

Ray Denenberg wrote:
> From: Adam Dickmeiss [mailto:adam@indexdata.dk] 
>   
>> It's also been our assumption that it would be practical to use same schema
>>     
> identifiers for both SRU and Z39.50. Why have two registries? 
>
>
> Well the problem is that you have to use the OID form if you are supplying
> the schema identifier in the schema field in compspec. 
Well. the way I read amendment 5, the schema OID became optional.
http://www.loc.gov/z3950/agency/amend/am5.html
A string , member uri, may be given instead.

The CompSpec has recordSyntax in it and that is required.  But that's 
not a schema.. So using Amendment 5 we have a way to specify a string 
based schema.. Now all this is probably not of interest to many since 
it's not widely used, AFAIK.

The element set way.. Page
http://www.loc.gov/z3950/agency/agree/request-xml.html
mentions schema identifiers.. This page even has link to the SRU record 
schema identifers.. Although the link no longer works.

My only hope was both that both SRU and Z39.50 would use the same schema 
identifiers for XML. Z39.50 has OID based syntax and of course SRU has 
recordPacking (but that doesn't affect the schema identifiers).

> You don't have any
> choice there because it's typed as asn.1 OBJECT IDENTIFIER. True, you could
> (technically) use the URI form when supplying it within the element set name
> parameter (because it has no such restriction).  So one way or the other you
> end up with two different identfiers: either (a) different for SRU and
> Z39.50, or (b) different for the two ways within Z39.50. And in the second
> case, one of the two will be inconsistent with SRU.  So (a) would be the
> lesser of the evils, wouldn't it?
>
> (Or are you suggesting that we use OIDs instead or URIs in SRU. I hope not.)
>   
Of course not.

/ Adam
> --Ray
>
>
>
>
>
>

Received on Thursday, 29 January 2009 08:12:00 UTC