<?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>The history of the Fact! &#187; The history of the Fact!</title>
	<atom:link href="http://www.henkbinnendijk.nl/blog/category/architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.henkbinnendijk.nl/blog</link>
	<description>About datawarehouse architecture practice and thoughts</description>
	<lastBuildDate>Wed, 11 Jan 2012 10:24:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Proces Metadata vs Powercenter metadata: een praktische invulling</title>
		<link>http://www.henkbinnendijk.nl/blog/2011/12/proces-metadata-vs-powercenter-metadata-een-praktische-invulling/</link>
		<comments>http://www.henkbinnendijk.nl/blog/2011/12/proces-metadata-vs-powercenter-metadata-een-praktische-invulling/#comments</comments>
		<pubDate>Mon, 19 Dec 2011 11:34:11 +0000</pubDate>
		<dc:creator>Henk</dc:creator>
				<category><![CDATA[architecture]]></category>
		<category><![CDATA[Data Integratie]]></category>
		<category><![CDATA[Data Management]]></category>
		<category><![CDATA[Data Modeling]]></category>
		<category><![CDATA[Datawarehouse]]></category>
		<category><![CDATA[Informatie Architectuur]]></category>
		<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://www.henkbinnendijk.nl/blog/?p=416</guid>
		<description><![CDATA[Soms kan het handig zijn om in je metadatamodel informatie van je applicatielaag op te nemen. We denken dan bijvoorbeeld aan: met welke techniek en welke versie heb ik deze data in m&#8217;n datawarehouse geladen? Of met welke versie heb ik een data conversie uitgevoerd. Natuurlijk is elke powercenter ontwikkelaar bekend met het welbekende $PMWorkflowRunId [...]]]></description>
		<wfw:commentRss>http://www.henkbinnendijk.nl/blog/2011/12/proces-metadata-vs-powercenter-metadata-een-praktische-invulling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Goudmijn</title>
		<link>http://www.henkbinnendijk.nl/blog/2009/12/goudmijn/</link>
		<comments>http://www.henkbinnendijk.nl/blog/2009/12/goudmijn/#comments</comments>
		<pubDate>Wed, 30 Dec 2009 14:29:06 +0000</pubDate>
		<dc:creator>Henk</dc:creator>
				<category><![CDATA[architecture]]></category>
		<category><![CDATA[Datawarehouse]]></category>
		<category><![CDATA[architectuur]]></category>
		<category><![CDATA[data]]></category>

		<guid isPermaLink="false">http://www.henkbinnendijk.nl/blog/?p=247</guid>
		<description><![CDATA[Een nieuwe mijnschacht Data is als goud te vinden in de grond. Met goud kan men bv prachtige juwelen maken om te verkopen. Maar om het te ontginnen is een schacht nodig om bij het goud te komen. In de praktijk zijn er al vele projecten opgezet om dit goud te ontginnen. Maar met de [...]]]></description>
		<wfw:commentRss>http://www.henkbinnendijk.nl/blog/2009/12/goudmijn/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kimball or Inmon in an enterprise environment</title>
		<link>http://www.henkbinnendijk.nl/blog/2009/10/kimball-or-inmon-in-an-enterprise-environment/</link>
		<comments>http://www.henkbinnendijk.nl/blog/2009/10/kimball-or-inmon-in-an-enterprise-environment/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 05:58:26 +0000</pubDate>
		<dc:creator>Henk</dc:creator>
				<category><![CDATA[architecture]]></category>
		<category><![CDATA[architectuur]]></category>
		<category><![CDATA[bus]]></category>
		<category><![CDATA[datamart]]></category>
		<category><![CDATA[Datawarehouse]]></category>
		<category><![CDATA[ELT]]></category>
		<category><![CDATA[ETL]]></category>
		<category><![CDATA[Inmon]]></category>
		<category><![CDATA[Kimball]]></category>

		<guid isPermaLink="false">http://www.henkbinnendijk.nl/blog/?p=83</guid>
		<description><![CDATA[ datawarehousing out of the book? In the last few years I have seen a dozen of data warehouse projects. more than 70% were build upon the (Kimball) Bus architecture having a 2-tier layer. Most of the time build &#8220;out of the book&#8221;. With other words the architecture has not been applied to what the business needs, but [...]]]></description>
		<wfw:commentRss>http://www.henkbinnendijk.nl/blog/2009/10/kimball-or-inmon-in-an-enterprise-environment/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>(e)DWH Architecture of the Shelf</title>
		<link>http://www.henkbinnendijk.nl/blog/2009/06/edwh-architecture-of-the-shelf/</link>
		<comments>http://www.henkbinnendijk.nl/blog/2009/06/edwh-architecture-of-the-shelf/#comments</comments>
		<pubDate>Fri, 26 Jun 2009 10:26:40 +0000</pubDate>
		<dc:creator>Henk</dc:creator>
				<category><![CDATA[architecture]]></category>
		<category><![CDATA[approach]]></category>
		<category><![CDATA[Datavault]]></category>
		<category><![CDATA[Datawarehouse]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[Inmon]]></category>
		<category><![CDATA[Kimball]]></category>
		<category><![CDATA[methods]]></category>

		<guid isPermaLink="false">http://www.henkbinnendijk.nl/blog/?p=127</guid>
		<description><![CDATA[It is such a pity that so many designers and -even worse- architects of data warehouses use only 1 architect design for all their customers. It is not called designing under architecture. There is no &#8220;one-size-fits-all&#8221; architecture for data warehouses. I can image that people still do so because of simplicity in for example implementation. [...]]]></description>
		<wfw:commentRss>http://www.henkbinnendijk.nl/blog/2009/06/edwh-architecture-of-the-shelf/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

