Hi,
    I have some clarification on the validity of the SyntaxList w.r.t. the clause in Sec 10.12 of X.681 which says - "If an "OptionalGroup" starts with a "Literal", then the first token following the "OptionalGroup" shall also be a "Literal" and shall be different from the first "Literal" of all immediately preceding "OptionalGroup"s,".
 
    Consider the following ASN.1 spec snippet -

MY-CLASS ::= CLASS
{
    &Type    OPTIONAL,
    &value   INTEGER OPTIONAL
}
WITH SYNTAX
{
    [ &Type A &value ] A
}

 
    In the above case, is the starting literal of the OptionalGroup '&Type' or 'A'?
 
    Further if an OptionalGroup begins with an OptionalGroup then is the starting literal of the outer OptionalGroups the set of starting literal of the inner OptionalGroups and that of its own. Lets assume the above SyntaxList is changed as follows -
 

WITH SYNTAX
{
    [ [ A &Type ] [ B &value ] ] C
}

 
    Then is the starting literal of the outer OptionalGroup { A, B }? 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