<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JSON on Nick Whiteley</title><link>http://nickwhiteley.com/tags/json/</link><description>Recent content in JSON on Nick Whiteley</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Fri, 09 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="http://nickwhiteley.com/tags/json/index.xml" rel="self" type="application/rss+xml"/><item><title>JSON data</title><link>http://nickwhiteley.com/posts/json-data/</link><pubDate>Fri, 09 Jan 2026 00:00:00 +0000</pubDate><guid>http://nickwhiteley.com/posts/json-data/</guid><description>&lt;p&gt;JSON is a a great format for data exchange. It is simple, human readable and can be precise. On the down side it is untyped and it can be verbose. With formal data exchange this can be a problem.&lt;/p&gt;
&lt;p&gt;I have been using a simple JSON data structure for a few years and so thought I would share it here. It is a robust way to exchange data between systems which don&amp;rsquo;t necessarily have a contract for the data format. It also scales better than the usual key value methos favoured by many systems.&lt;/p&gt;</description></item></channel></rss>