[147485] in cryptography@c2.net mail archive
Re: [Cryptography] encoding formats should not be committee'ized
daemon@ATHENA.MIT.EDU (dan@geer.org)
Thu Oct 3 12:40:12 2013
X-Original-To: cryptography@metzdowd.com
From: dan@geer.org
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
In-Reply-To: Your message of "Thu, 03 Oct 2013 20:49:05 +1300."
<E1VRdej-0005ax-OV@login01.fos.auckland.ac.nz>
Date: Thu, 03 Oct 2013 11:59:54 -0400
Cc: cryptography@metzdowd.com
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
> For those not familiar with TL1, "supposed to be readable" here means
> "encoded in ASCII rather than binary". It's about as readable as
> EDIFACT and HL7.
<utter_tangent>
The (U.S.) medical records system that started at the Veterans'
Administration and has now spread to all but all parts of the
U.S. Federal government that handle electronic health records is
ASCII encoded, and readable. Called "The Blue Button,"[1] there
is even an HL7->Blue Button file converter.[2]
Score one for human readable.
</utter_tangent>
--dan
[1] www.va.gov/BLUEBUTTON/Resources.asp
[2] www.hl7.org/implement/standards/product_brief.cfm?product_id=288
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
