Hi Roger,

There is JSON as well.  I'm not sure what format it uses under the 
covers to encode the data though.

I would also point out on item 3 the nomenclature of an ASN.1 file is 
not correct.  ASN.1 is the schema syntax (like XSD), encoded instances 
can be BER, DER, or PER (the equivalent of the XML instance).

Regards,

Ed Day

Costello, Roger L. wrote:
> When sending an XML document across the wire, here are the main
> choices:
>
> 1. Send the XML document as is, as ASCII text, without any compression
> or other alterations.
>
> 2. Compress the XML document using a compression tool such as WinZip or
> Bzip, and then send the compressed document.
>
> 3. Encode the XML document as an ASN.1 file, and then send the ASN.1
> file.
>
> 4. Encode the XML document a Fast Infoset file, and then send the FI
> file.
>
> 5. Encode the XML as an Efficient XML Interchange file, and then send
> the EXI file.
>
> Are there other choices?  Have I phrased each choice properly?
>
> Under what circumstances would a choice be selected? 
>
> What are the advantages and disadvantages of each choice?
>
> /Roger
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@l...
> subscribe: xml-dev-subscribe@l...
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
>
>
>   


-- 
Ed Day
Objective Systems, Inc.
http://www.obj-sys.com