<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Information in Rotation &#187; Information Patterns</title>
	<atom:link href="http://appliedrotation.com/Techblog/?cat=13&#038;feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://appliedrotation.com/Techblog</link>
	<description>Dan Rabin writes on metadata, data, the information they represent and how.</description>
	<lastBuildDate>Sun, 01 Nov 2015 20:21:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
		<item>
		<title>Information Patterns: series introduction</title>
		<link>http://appliedrotation.com/Techblog/?p=27</link>
		<comments>http://appliedrotation.com/Techblog/?p=27#comments</comments>
		<pubDate>Fri, 02 Feb 2007 18:25:25 +0000</pubDate>
		<dc:creator>Dan Rabin</dc:creator>
				<category><![CDATA[Information Patterns]]></category>
		<category><![CDATA[Information Philosophy]]></category>

		<guid isPermaLink="false">http://appliedrotation.com/Techblog/?p=27</guid>
		<description><![CDATA[Every time a new data format spec hits my inbox, I get a little twinge of dread. Such documents are often enormous. They&#8217;re written in standardese (often badly). They&#8217;re usually written by committees. They go through a maze of twisty &#8230; <a href="http://appliedrotation.com/Techblog/?p=27">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Every time a new data format spec hits my inbox, I get a little twinge of dread.  </p>
<p>Such documents are often <em>enormous</em>.  They&#8217;re written in <em>standardese</em> (often badly).  They&#8217;re usually written by <em>committees</em>.  They go through a maze of twisty little <em>revisions</em>, all different.</p>
<p>But worst of all, they often bury their novelty in a sea of details that resemble those in the last spec I reviewed.</p>
<p>I&#8217;d like to do for data formats and other information representations what the <a href="http://www.amazon.com/Design-Patterns-Object-Oriented-Addison-Wesley-Professional/dp/0201633612">Gang of Four book</a> does for programs:  call out and label the patterns that come up over and over again so that I can classify details into bigger chunks for mental processing.  </p>
<p>You can expect to see several different kinds of post in this series:</p>
<ul>
<li><strong>Case studies.</strong> I have to look at lots of actual data formats in order to discern the patterns!</li>
<li><strong>Data format patterns.</strong> Most posts will be about patterns I find in data formats&#8230;</li>
<li><strong>Information usage patterns.</strong> &#8230;but some posts will be about how information is generated, stored, and used.</li>
<li><strong>Other.</strong> I&#8217;ll probably think of some other topics as well.</li>
</ul>
<p>I expect to look at simple cases, such as comma-separated values, as well as fiendishly complex cases, such as PDF.  Programming-language syntaxes are fair game; database index disk structures are right out.  In between, I&#8217;ll draw the boundary as interest dictates.</p>
<p>This series will be open-ended as long as people keep inventing data formats faster than I can look at them.</p>
]]></content:encoded>
			<wfw:commentRss>http://appliedrotation.com/Techblog/?feed=rss2&#038;p=27</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
