Re: Encoding OPTIONAL canonically

So what I conclude is that any specification which uses OPTIONAL SEQUENCE or
SET elements and fails to specify a meaning for when it is empty or missing
cannot expect a canonical encoding even if it uses DER.  I further conclude
that an application for which a missing or empty set (sequence) is semantically
identical but wants a canonical encoding should perhaps avoid use of the
OPTIONAL and expect to see the empty set encoded.

Have I got it now ?

John