<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<blockquote
cite="mid:alpine.DEB.2.00.1002032123340.5653@freepascal.dyndns.org"
type="cite"><br>
JSON is not related to YAML at all except in that it is a simple data
format.
<br>
</blockquote>
That's true, but from the yaml v1.2 spec:<br>
"<span class="Apple-style-span"
style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span" style="font-family: sans-serif;">YAML can
therefore be viewed as a natural superset of JSON, offering improved
human readability and a more complete information model. This is also
the case in practice; every JSON file is also a valid YAML file.</span></span>"<br>
<br>
<blockquote
cite="mid:alpine.DEB.2.00.1002032123340.5653@freepascal.dyndns.org"
type="cite">And as far as I can see from the specs, YAML also does not
offer a direct way
<br>
to capture binary data. <br>
</blockquote>
That is also true. I got the impression from wikipedia that YAML has a
direct way to capture the binary data. From the specs I see that YAML
uses base64 coding for binary data, which was what I hoped to prevent
because it causes a lot of computation overhead.<br>
<br>
</body>
</html>