Hi Ramaswamy, Yes, ASN.1 (2002) does permit the value notation you have used below. Note, however, that use of <c/> does not indicate the absense of the OPTIONAL field, but indicates it is present with zero-length value.
---------------------------------------------------------------------------- Paul E. Thorpe Toll Free : 1-888-OSS-ASN1 OSS Nokalva International: 1-732-302-0750 Email: [EMAIL PROTECTED] Tech Support : 1-732-302-9669 http://www.oss.com Fax : 1-732-302-0023 On Tue, 25 May 2004, Ramaswamy R - CTD, Chennai. wrote: > Hi, > > I have some queries regarding the XMLValue notation in an > XMLValueAssignment. The XML Single Tag is used in XMLTypedValue. The cases > where the XML Single Tag is used to represents value are not to be > considered. For e.g. the following is very much valid in ASN.1 (2002) - > > _____ > > null-value ::= <NULL/> > _____ > > But is usage of a similar notation for say sequence value permitted? > > _____ > > Sequence ::= SEQUENCE > { > a INTEGER { zero(0), two(2), four(4), six(6), eight(8) }, > c NumericString OPTIONAL > } > > seq-val ::= > <Sequence> > <a><four/></a> > <c/> > </Sequence> > _____ > > > In my understanding the above is not permitted as such by the grammar of > XMLSequenceValue as per X.680 (07/2002). But I find the same being > supportedby some tools. In my understanding this is non-conformance to the > 2002 standard, or an extension provided to the standard. I would like to > have a conformation on the above. Is the above sequence value permitted as > part of the 2002 standard? Thanking you. > > Yours Sincerely > Ramaswamy R > Member Technical Staff > HCL Technologies Ltd > 184 Arcot Road > Vadapalani > Chennai - 600026 > Ph (Off) : 23728366 ext 2344 > > To deny our instincts, is to deny the very thing that makes us human - Mouse > (The Matrix) > > >
