[
Lists Home |
Date Index |
Thread Index
]
- From: Olivier DUBUISSON <Olivier.Dubuisson@francetelecom.fr>
- To: Peter Jacobi <pj@walter-graphtek.com>
- Date: Wed, 21 Jun 2000 17:41:56 +0000
Peter Jacobi wrote:
>
> One of the
> > interesting issues is that ASN.1 has both named data types and named
> > identifiers (an element has both a type and an identifier), but in XML you
> > have only element names (basically representing complex data types). So
> > do you use identifiers or data type names, and what do you do with the
> > other of the pair? There are a lot of possible solutions.
>
> Two possibilities, I prefer:
>
> a) use the tags as element names ("A17" for [APPLICATION 17]),
> use fixed attributes for identifiers and data type names.
Tags are historical "residues" in ASN.1. They are only used by the
BER encoding rules.
It is now recommended to add the "AUTOMATIC TAGS" clause in the
module headers and to not take core of the tags any more.
> b) use the identifiers as element names, use fixed attributes for tags and
> data type names.
What's the need to keep the tags and type names? It seems to me that
this verbosity is useless.
Do you make the assumption that both sides (i.e., the encoder and the
decoder) are generated from the same ASN.1 module?
--
Olivier DUBUISSON
france telecom R&D
_ DTL/MSV - 22307 Lannion Cedex - France
( ) tel: +33 2 96 05 38 50 - fax: +33 2 96 05 39 45
/ \/ --------------------------------------
\_/\ Site ASN.1 : http://asn1.elibel.tm.fr/
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************
|
