Lev Walkin writes: > Pawel wrote: > > Hallo group members. > > > > I am trying to understand the following asn1 notation: > > > > http://www.itu.int/ITU-T/asn1/database/itu-t/h/h450.1/1998/Remote-Operations-Apdus.html > > > > I am familiar with basic notations, like: Choice, Sequence, SequenceOf, > > constraints, tagging, but those braces: > > ROS{InvokeId:InvokeIdSet, OPERATION:Invokable, OPERATION:Returnable} > > > > .. and parenthesis, like: > > invokeId > > InvokeId(InvokeIdSet) > > (CONSTRAINED BY {-- must be unambiguous -- } ! > > RejectProblem:invoke-duplicateInvocation), > > > > look dangerous to me:) > > Could You tell me where to look for description on these two notations? > > These are parameterization, constraints and exceptions. > > The first parameterizes the ROS with InvokeIdSet (first argument), > Invokable (second argument) and Returnable (third argument). They are > used in the ROS type in some places. Parameterization alters the > name space for ROS. > > Constraints are things that make the type to be more restrictive > than the original type. You may choose to ignore the CONSTRAINED BY{} > notation, as it does not alters the encoding or decoding. If you don't > ignore it, then if constraint fails, the exceptions come into play: > > Exceptions allow your code to detect constraint violations and invoke > some named procedures, such as invoke-duplicateInvocation. The precise > way of invoking them depends on the ASN.1 compiler in question. > > -- > Lev Walkin > [EMAIL PROTECTED] >
Lev, thank You for the answer. Now I at least know which terms to look for in internet. Regards, Pawel _______________________________________________ Asn1 mailing list [email protected] http://lists.asn1.org/mailman/listinfo/asn1
