- From: Sebastian Hammer <quinn@indexdata.dk>
- Date: Mon, 26 Apr 2004 23:09:43 +0200
- To: Adam Dickmeiss <adam@indexdata.dk>, www-zig@w3.org
- Cc: ZIG <www-zig@w3.org>
It doesn't work there because Term is a CHOICE type, which can't be
IMPLICITly tagged, of course.
--Sebastian
At 23:05 26-04-2004 +0200, Adam Dickmeiss wrote:
>Is it really true that IMPLICIT could not be handled by snacc? There are
>everywhere in the core Z39.50v3 spec..
>
>-- Adam
>
>Ray Denenberg, Library of Congress wrote:
>
>>Alan -- I've fixed these errors
>>(http://www.loc.gov/z3950/agency/defns/term-2.html)
>>
>>Thanks.
>>
>>--Ray
>>
>>
>>----- Original Message ----- From: "Alan Kent" <ajk@mds.rmit.edu.au>
>>To: "ZIG" <www-zig@w3.org>
>>Sent: Tuesday, April 20, 2004 2:46 AM
>>Subject: MultipleSearchTerms-2 ASN.1 error?
>>
>>
>>
>>
>>>Hi all,
>>>
>>>Has anyone implemented MultipleSearchTerms-2? We support
>>>MultipleSearchTerms-1 but I had not noticed there was a -2
>>>form around. So I was having a look. See
>>>http://lcweb.loc.gov/z3950/agency/agree/range.html
>>>
>>>I got the ASN.1 and fed it through 'snacc', but it reported errors.
>>>
>>>On the site it says
>>>
>>>SEQUENCE OF SEQUENCE{
>>> term (1) IMPLICIT TERM,
>>> flag (2) IMPLICIT BOOLEAN OPTIONAL}
>>>
>>>I made the following changes to get snacc to compile it:
>>>- there were round brackets around the tag numbers instead of square
>>> brackets (I assume that was a typo)
>>>- I changed "TERM" to "Term"
>>>- I removed the IMPLICIT in front of Term to make snacc happy
>>>
>>>This results in
>>>
>>>SEQUENCE OF SEQUENCE{
>>> term [1] Term,
>>> flag [2] IMPLICIT BOOLEAN OPTIONAL}
>>>
>>>Are the above changes correct/compatible with what other people
>>>
>>have?
>>
>>
>>>Thanks,
>>>Alan
>>>
>>>
>>
>>
>>
--
Sebastian Hammer, Index Data <http://www.indexdata.dk/>
Ph: +45 3341 0100, Fax: +45 3341 0101
Received on Monday, 26 April 2004 17:10:54 UTC