Article View: comp.protocols.iso
Article #15Re: ASN1 specification - clarification
From: Bancroft Scott
Date: Thu, 29 Oct 1992 22:38
Date: Thu, 29 Oct 1992 22:38
21 lines
1292 bytes
1292 bytes
huitema@mitsou.inria.fr (Christian Huitema) writes:
>In article <86010005@hpcndaw.CND.HP.COM>, mds@hpcndaw.CND.HP.COM (Mark Smith) writes:
[...]
>May I suggest that we introduce an explicit AND operator in the constraint
>notation? After all, are we absolutely sure that we will never have to enter a
>constraint like:
>
> IA5String (((FROM("A"|"B"))&(SIZE(10))|
> ((FROM("C"|"D"))&(SIZE(20))))
The ISO DIS 8824 (1992) has an explicit AND operator. Unfortunately (IMHO),
it is called "INTERSECTION" and not simply '&' or "AND". '&' as you suggest
above is a natural, but it is already used in the definition of Information
Object Classes and it was thought best to not reuse it to indicate the
intersection of two sets of constraints.
FYI, there is also an "EXCEPT" and "ALL EXCEPT" in the DIS 8824.
Bancroft Scott
Technical Details
Message-ID:
<Oct.29.17.38.40.1992.24956@caip.rutgers.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!dziuxsolim.rutgers.edu!caip.rutgers.edu!baosReferences:
<578@vercors.frec.bull.fr> <86010005@hpcndaw.CND.HP.COM> <32707@sophia.inria.fr>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!dziuxsolim.rutgers.edu!caip.rutgers.edu!baos From: baos@caip.rutgers.edu (Bancroft Scott) Newsgroups: comp.protocols.iso Subject: Re: ASN1 specification - clarification Message-ID: <Oct.29.17.38.40.1992.24956@caip.rutgers.edu> Date: 29 Oct 92 22:38:41 GMT References: <578@vercors.frec.bull.fr> <86010005@hpcndaw.CND.HP.COM> <32707@sophia.inria.fr> Organization: Rutgers Univ., New Brunswick, N.J. Lines: 21