[ASN.1] WITH-COMPONENTS creates new type or just semantically constrains?

2002-07-17 Thread Paul Long
I have questions about inner subtyping. Given these two type definitions: Parent ::= SEQUENCE { anOptionalThing INTEGER OPTIONAL, anotherOptionalThing INTEGER OPTIONAL, aRequiredThing INTEGER } Child ::= Parent WITH COMPONENTS { ..., anOptionalThing

Re: [ASN.1] WITH-COMPONENTS creates new type or just semantically constrains?

2002-07-17 Thread John Larmouth
Paul Long wrote: Paul, I guess it depends on what you mean by a new type. (The term is not actual defined in ASN.1, but is used in the introduction and in a normal English way when talking about defining a new type from an old one by tagging or subtyping.) The text is clear that tagging and

Re: [ASN.1] WITH-COMPONENTS creates new type or just semantically constrains?

2002-07-17 Thread John Larmouth
Sorry, re my mention of possible unclarity in the A::=B and clauses 15.1 and 16.1, I missed the following in Annex B: B.2.1 The underlying model is of types, as non-overlapping containers, that contain values, with every occurrence of the ASN.1 Type construct defining a distinct new type (see

RE: [ASN.1] WITH-COMPONENTS creates new type or just semantically constrains?

2002-07-17 Thread Paul Long
Of John Larmouth Sent: Wednesday, July 17, 2002 12:17 PM To: [EMAIL PROTECTED] Subject: Re: [ASN.1] WITH-COMPONENTS creates new type or just semantically constrains? Paul Long wrote: Paul, I guess it depends on what you mean by a new type. (The term is not actual defined in ASN.1