- From: Dan Brickley <danbri@w3.org>
- Date: Wed, 31 May 2000 11:56:04 -0400 (EDT)
- To: "Hawkes, Christopher D" <Christopher.D.Hawkes@icn.siemens.com>
- cc: "'xml-dist-app@w3.org'" <xml-dist-app@w3.org>
Hi
On Wed, 31 May 2000, Hawkes, Christopher D wrote:
> Has any work been done on the automatic translation of ASN.1 message
> definitions into XML?
At last a question I know the answer to! Check out
XER (XML Encoding Rules), http://asf.gils.net/xer/
--danbri
From http://asf.gils.net/xer/concept.html
values. When BER (Basic Encoding Rules) is
applied to the ASN.1 expressions, data structures are encoded as
octets in the form of tag, length, and
value (or an indefinite length value is delimited by an end-tag).
To change an ASN.1/BER data structure to XML, an XML tag and end-tag are
derived and the value is
wrapped within. To change an XML structure into ASN.1/BER, the appropriate
ASN.1/BER tag is derived
and the value length is calculated.
Scope
Although ASN.1 is used in a variety of network environments, the initial
focus of XER is on supporting
client-server applications on the Internet using TCP/IP. Also, those
currently involved nform work on a response to an OpenGIS Consortium
(OGC) RFP on Catalog
Services. In the initial sumbmission of the OGC specification, the EO/GEO
Team used XML to represent
some of the services employed in the draft Geospatial Profile of Z39.50. A
copy of the proposal is available
in MS Word 98 format and in MS Word 6 format.
Received on Wednesday, 31 May 2000 11:56:09 UTC