JsonML allows browsers to process RFC 3252 protocols.
To parse his statement, there is no need to read RFC 3252. Here is a brief snippet for your convenience.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ip PUBLIC "-//IETF//DTD BLOAT 1.0 IP//EN" "bloat.dtd">
<ip>
<header length="474">
<version value="4"/>
<tos precedence="Routine" delay="Normal" throughput="Normal"
relibility="Normal" reserved="0"/>
<total.length value="461"/>
<id value="1"/>
<flags reserved="0" df="dont" mf="last"/>
<offset value="0"/>
<ttl value="255"/>
<protocol value="6"/>
<checksum value="8707"/>
<source address="10.0.0.22"/>
<destination address="10.0.0.1"/>
<options>
<end copied="0" class="0" number="0"/>
</options>
<padding pad="0"/>
</header>
<payload>
</payload>
</ip>
<grin>:)</grin>
Update: Here is a better "grin" suggested by Stefan Tilkov:
<emotionml xmlns="http://www.w3.org/2008/11/emotionml">
<emo:emotion>
<emo:category set="everydayEmotions" name="fun"/>
<emo:intensity value="0.9"/>
</emo:emotion>
</emotionml>

{ 1 comment… read it below or add one }
I’m sure you mean
<emotionml xmlns=”http://www.w3.org/2008/11/emotionml”>
<emo:emotion>
<emo:category set=”everydayEmotions” name=”fun”/>
<emo:intensity value=”0.9″/>
</emo:emotion>
</emotionml>
:-)