Identification of Express Version

[Wilson, Peter R]

Dave,

    I don't see why a TC will automatically lead to a change in the ASN.1
identifier. Surely it is up to the authors of the TC to decide whether or
not to change it. I would expect that editorial changes would have no effect
on the identifier as they would not affect an EXPRESS parser. It is only
changes that a parser has to be aware of that would require a change to the
identifier.

Peter W.

Dr Peter R. Wilson
Boeing Commercial Airplanes
PO Box 3707, MS 6H-AF, Seattle, WA 98124-2207
(Package Delivery: MS 6H-AF, 1601 E. Valley Frontage Road, Renton, WA 98055)
Tel: (425) 237-3506, Fax: (425) 237-3428
Email: peter.r.wilson at boeing.com
--------------------------------
Any opinions expressed above are personal;
they shall not be construed as representative of any organisation.
--------------------------------
 

> -----Original Message-----
> From: Dave Loffredo [mailto:loffredo at steptools.com]
> Sent: Friday, May 03, 2002 11:03 AM
> To: edbark at nist.gov
> Cc: wg11 at steptools.com
> Subject: Re: Identification of Express Version
> 
> 
> 
> Ed, 
> 
> If I can summarize your two points as follows:
> 
>    #1 -- the ASN.1 identifier will stay the same from draft 
>       status to IS
> 
> Perhaps, but that is not the key issue.  A TC will change the ASN.1
> identifier, even if there are no technical changes to the spec.  So
> the issue may not hit now, but it eventually will.
> 
> 
>    #2 -- the ASN.1 identifier is needed to separate E1 from E2
>       schemas.
> 
> I completely agree that something is needed to separate the two, but
> is the ASN.1 identifer too fragile for this purpose?  THIS is the real
> question.  As shown above, the ASN.1 identifier may change because of
> editorial fixes that have nothing to do with new language features.
> 
> 					       - Dave
> 
>