Mark, I believe that the ASN.1/XML standarization efforts are still in ballot (last call?). So, they have not yet been published and made available for free on the ITU-T SG17 web site along with the rest of the ASN.1 standards.
I guess that at this point, only those attending the ASN.1 meetings and contributing to the development of this work have copies of these amendments and documents. To review them I believe would require ASN.1 Project leader approval. According to the ASN.1 Project web page at http://www.itu.int/ITU-T/asn1/ ... "The ASN.1 standard is being enhanced to provide a standard mapping of values of types defined using ASN.1 into XML markup format, making it possible for such values to be easily displayed using common XML browsers regardless of which encoding rules (e.g., BER, PER) such messages were encoded in. This is being achieved by using ASN.1 as the schema of the messages, and XML markup as the display format. In addition to the enhancements to the ASN.1 standard, a new encoding rules document (X.693) titled 'Encoding using XML or basic ASN.1 value notation', is being created. This document specifies how to encode values of ASN.1 types in XML markup format for the purpose of transmission (as opposed to using XML markup as value notation within an ASN.1 module). Also specified in this document is how to encode values of ASN.1 types using ordinary ASN.1 value notation for the purposes of transmission. Some benefits of this work are: - Applications will be able to easily display BER-encoded or PER-encoded messages (for example) using XML browsers. - It makes possible the creation of tools that allow applications to encode messages in XML markup format, BER format, PER format, etc., without the need to know the details of how to encode values in any of these formats. - It will be possible for application protocols to exploit the ASN.1 value notation as an ordinary set of encoding rules in those cases where textual encodings are desired but there is no interest in using XML markup. - Used in conjunction with the ECN support (explained in Section 3), this also enables legacy protocols to have their values displayed using XML." Phil Griffin Michel PERIN wrote: > > From: Mark DeCoursey <[EMAIL PROTECTED]> > > > Can you tell me the spec on ASN.1 -> XML, and where I can get it? > > Is that "XER"? > Yes. > Have a look at: > http://asn1.elibel.tm.fr/xml > > Michel P�rin > ---------------------------------------------------- > Atos Origin Int�gration > T�l�com/TEQ > 18, avenue d'Alsace > 92926 Paris La D�fense Cedex > > Tel: +33 1 55 91 28 41 > Web site: http://www.marben-products.com > E-Mail : [EMAIL PROTECTED] > ---------------------------------------------------- > ======================================================================== > This electronic transmission and any files attached to it are strictly > confidential and intended solely for the addressee. If you are not the > intended addressee, you must not disclose, copy or take any action in > reliance of this transmission. If you have received this transmission in > error, please notify us by return and delete the same. The views expressed > in this electronic transmission do not necessarily reflect those of Atos > Origin or any of its subsidiary companies. Although the sender endeavours to > maintain a computer virus free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. > Thank You. > =========================================================================
