<?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 Living Systems_</title>
    <link>https://livesys.se/tags/json/</link>
    <description>Recent content in Json on Living Systems_</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Dec 2015 07:10:00 +0100</lastBuildDate>
    <atom:link href="https://livesys.se/tags/json/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The unexpected convenience of JSON on the commandline</title>
      <link>https://livesys.se/posts/the-unexpected-usefullness-of-json-on-the-commandline/</link>
      <pubDate>Tue, 08 Dec 2015 07:10:00 +0100</pubDate>
      <guid>https://livesys.se/posts/the-unexpected-usefullness-of-json-on-the-commandline/</guid>
      <description>&lt;p&gt;I was working with a migration from &lt;a href=&#34;http://drupal.org&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;drupal&lt;/a&gt;&#xA; to&#xA;&lt;a href=&#34;http://processwire.com&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;processwire&lt;/a&gt;&#xA; CMS:es, where I wanted to be able&#xA;to pipe data, including the body field with HTML formatting and all,&#xA;through multiple processing steps in a flexible manner. I&amp;rsquo;d start with&#xA;an extraction SQL query, through a few components to replace and massage&#xA;the data, and finally over to an import command using processwire&amp;rsquo;s&#xA;&lt;a href=&#34;http://wireshell.pw&#34; target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;wireshell tool&lt;/a&gt;&#xA;. So, basically I needed a flexible&#xA;format for structured data that could be sent as one &amp;ldquo;data object&amp;rdquo; per&#xA;line, to work nicely with linux commandline tools like grep, sed and&#xA;awk.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
