ASN.1 is totally unsuitable for most tasks. It is a 'one size fits a
few' solution.
sdw
Dennis Sosnoski wrote:
> Bob Wyman wrote:
>
>> Whether or not you think you need it, the reality is that you
>> can't have it. There is no "one-size-fits-all" binary format. The best
>> you can hope for is one-size-fits-most or
>> one-size-fits-more-than-others... In any case, the key is to make sure
>> that the final result is "one-size-fits-enough-to-be-worth-it."
>> My personal feeling is that ASN.1 is the best available
>> solution to the "one-size-fits-most" case. ASN.1 has been an
>> international standard for a very long time, has been used extensively
>> and has defined mappings from XML Schema to ASN.1. Basically, all the
>> hard work has been done here... The choice should be obvious...
>>
>>
>>
> I think that makes ASN.1 a reasonable "one-size-fits-schema" choice. A
> lot of the world is still not schema, though - and even for documents
> with schemas, would the ASN.1 approach handle arbitrary documents at
> runtime, or would it need to use pregenerated codecs?
>
> - Dennis
>
--
http://www.hpti.com Per: http://sdw.st
Stephen D. Williams 703-724-0118W 703-995-0407Fax 20147-4622 AIM: sdw
