----- Original Message ----- From: "Paul Thorpe" <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> To: <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> Sent: Tuesday, September 30, 2003 8:54 PM Subject: Re: [ASN.1] Rgd tagging of SEQUENCE type
> On Tue, 30 Sep 2003, Ramaswamy wrote:
> > The objective was that all "Root" components are numbered first, then all
> extension additions. Note that X.680, 24.9 does not distiguish between
> what is in the first or second RootComponentTypeList. I treats both
> "RootComponentTypeList" together.
>
Hi,
I still could not quite convince myself with the process of AUTOMATIC TAGGING for the specific case that we discusses w.r.t. extensibility. I guess I didn't express myself clear enough. The following illustrates the problem that I have -
------------------------------------------------------------------------
ComponentTypeLists <- RootComponentTypeList "," ExtensionAndException ExtensionAdditions ExtensionEndMarker ","
RootComponentTypeList
In Version1 of protocol:
SomeSequence ::=
SEQUENCE
{
a INTEGER,
b REAL,
...,
eal1 BOOLEAN,
eal2 NULL OPTIONAL,
...,
rctl1 REAL
}
In Version2 of protocol:
SomeSequence ::=
SEQUENCE
{
a INTEGER,
b REAL,
...,
eal1 BOOLEAN,
eal2 NULL OPTIONAL,
...,
rctl1 REAL,
rctl2 NumericString
}
You are not allowed to add a component in the extension root, even if the second part appears after an extension marker. In fact, the idea is that the second extension marker "..." closes the extension series, i.e., you are only allowed to add components immediately before the second extension marker.
Please note that your questions are FAQ that are answered in the books that you can download from http://www.oss.com/asn1/booksintro.html
--
Olivier DUBUISSON
france telecom R&D
DTL/TAL - 22307 Lannion Cedex - France t: +33 2 96 05 38 50 - f: +33 2 96 05 39 45 - http://asn1.elibel.tm.fr/
