From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 20 Feb 2006 02:04:37 +0200 From: Harri Haataja Subject: Re: [9fans] asn.1 alternatives In-reply-to: <541ac7952476f11c319d81a7b9f7d516@terzarima.net> To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Message-id: <20060220000437.GC20071@XTL.antioffline.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline References: <11d846ba1d1323cc1e956b2f67dfa6ec@plan9.bell-labs.com> <541ac7952476f11c319d81a7b9f7d516@terzarima.net> User-Agent: Mutt/1.5.11 Topicbox-Message-UUID: 01f0a94e-ead1-11e9-9d60-3106f5b1d025 On Sat, Feb 11, 2006 at 02:29:19PM +0000, Charles Forsyth wrote: > when i need to represent more than simple text or values, or attribute > value pairs, which isn't all that often, more and more i use Rivest > S-expressions, as i did on wednesday. > they are unambiguous (unlike both ASN.1 and XML), easy to read and > write, that can represent binary directly where that's appropriate, > with an `advanced textual form' (like it!) that people can read > without suffering eye strain, but with a well-defined canonical form > (always helpful when comparing or signing things). Sexprs would get my humble vote as well. BTW, re XML, there's also SXML that may or may not be interesting. http://okmij.org/ftp/Scheme/SXML.html -- The memory management on the PowerPC can be used to frighten small children. -- Linus Torvalds