Hi,
    I have been working on the DefinedSyntax notation and I have the following clarification rgd the clause (under sec 10.12 of X.681) w.r.t. the following ASN.1 code snippet.

MY-CLASS1 ::= CLASS
{
 &Type OPTIONAL,
 &value INTEGER OPTIONAL
}
WITH SYNTAX
{
 [ &Type ] [ &value ]
}
 
MY-CLASS2 ::= CLASS
{
 &Type1 OPTIONAL,
 &VSet1 INTEGER OPTIONAL
}
WITH SYNTAX
{
 [&Type1] [&VSet12]
}

 
    Under the section mentioned above, point b) states that - "The use of "OptionalGroup"s shall be such that at no time in the parsing process can a "Setting" appear that could potentially be a setting for more than one "FieldName".".
 
    In accordance with the above I wanted clarification on the point that, is the above statement applicable regardless of what the field signifies (i.e. TypeField / FixedTypeValue etc..)? In the above e.g. are both the SyntaxList illegal, or is the SyntaxList of ObjectClass - MY-CLASS1 leagal since the fields refer to different FieldTypes. Thanking you.
 
Yours Sincerely
Ramaswamy

"Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." - Albert Einstein

Information contained and transmitted by this E-MAIL is proprietary to
Synergy Infotech Private Limited and is intended for use only by the
individual or entity to which it is addressed, and may contain information
that is privileged, confidential or exempt from disclosure under applicable
law. If this is a forwarded message, the content of this E-MAIL may not have
been sent with the authority of the Company. If you are not the intended
recipient, an agent of the intended recipient or a  person responsible for
delivering the information to the named recipient,  you are notified that any
use, distribution, transmission, printing, copying or dissemination of this
information in any way or in any manner is strictly prohibited. We have taken
precautions to minimize the risk of transmitting software viruses, but we
advise you to carry out your own virus checks on any attachment to this
message. We cannot accept liability for any loss or damage caused by software
viruses. If you have received this communication in error, please delete this
mail & notify us immediately at mailto:[EMAIL PROTECTED]

Reply via email to