I've come across the following situation and I am not sure whether this is a language issue or a problem with the tools or a consequence of my lack of experience with ASN.1.
I have defined:
- an ALGORITHM information object class and an AlgorithmIdentifier type (at the bottom of the module, see below)
- an information object xxx and an (extensible) information object set AlgoSet
- a parameterized seqence type Algo with the parameter defining a component relation constraint
I now want to define a value of type Algo (algo1 and algo2 in the module) and this is where my intuition fails because I expected that the values supplied for the second parameter would be checked against the given type and flagged as out of range but this does not happen either in asnp or the OSS syntax checker.
Please note that Asnp is a **syntax** checker and, as such, it only checks syntax, that is, it checks that your module conforms to the grammar of the ASN.1 notation as defined in the ASN.1 set of standards. What you want to check is semantics.
Note that, despite they call it a "syntax checker", OSS free tool is a syntax & semantics checker.
--
Olivier DUBUISSON
France Telecom
Recherche & Developpement
R&D/MAPS/AMS - 22307 Lannion Cedex - France
t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/
_______________________________________________ ASN1 mailing list [email protected] http://lists.asn1.org/mailman/listinfo/asn1
