<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Modeling the Blueprint for MDM</title>
	<atom:link href="http://hubdesignsmagazine.com/2009/03/01/modeling-the-blueprint-for-mdm/feed/" rel="self" type="application/rss+xml" />
	<link>http://hubdesignsmagazine.com/2009/03/01/modeling-the-blueprint-for-mdm/</link>
	<description></description>
	<lastBuildDate>Tue, 22 May 2012 08:05:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Modeling the MDM Blueprint – Part 2 &#171; Hub Designs Blog</title>
		<link>http://hubdesignsmagazine.com/2009/03/01/modeling-the-blueprint-for-mdm/#comment-2759</link>
		<dc:creator><![CDATA[Modeling the MDM Blueprint – Part 2 &#171; Hub Designs Blog]]></dc:creator>
		<pubDate>Mon, 19 Jul 2010 11:04:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hubdesigns.com/?p=892#comment-2759</guid>
		<description><![CDATA[[...] Information Model, Operating Model, Reference Architecture, Semantic Model by James Parnitzke   In Part 1 of this series, we discussed what essential elements should be included in an MDM blueprint. The [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Information Model, Operating Model, Reference Architecture, Semantic Model by James Parnitzke   In Part 1 of this series, we discussed what essential elements should be included in an MDM blueprint. The [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Modeling the MDM Blueprint – Part 2 &#171; Hub Designs Blog</title>
		<link>http://hubdesignsmagazine.com/2009/03/01/modeling-the-blueprint-for-mdm/#comment-1809</link>
		<dc:creator><![CDATA[Modeling the MDM Blueprint – Part 2 &#171; Hub Designs Blog]]></dc:creator>
		<pubDate>Thu, 26 Mar 2009 17:20:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hubdesigns.com/?p=892#comment-1809</guid>
		<description><![CDATA[[...] Part 1 of this series, we discussed what essential elements should be included in an MDM blueprint. The [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Part 1 of this series, we discussed what essential elements should be included in an MDM blueprint. The [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sameer Nayak</title>
		<link>http://hubdesignsmagazine.com/2009/03/01/modeling-the-blueprint-for-mdm/#comment-1749</link>
		<dc:creator><![CDATA[Sameer Nayak]]></dc:creator>
		<pubDate>Thu, 05 Mar 2009 01:15:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hubdesigns.com/?p=892#comment-1749</guid>
		<description><![CDATA[I agree. The canonical model has been critical in my MDM journey. I think of it as the foundational element in integration of MDM systems with its consuming systems, often disparate systems using different data formats. It provides a common data format for master data exchange and reduces complexity&amp; cost  associated with point to point integrations. Additionally its allows one to better define the data domain at hand and ensure its relevance to the organization&#039;s use.]]></description>
		<content:encoded><![CDATA[<p>I agree. The canonical model has been critical in my MDM journey. I think of it as the foundational element in integration of MDM systems with its consuming systems, often disparate systems using different data formats. It provides a common data format for master data exchange and reduces complexity&amp; cost  associated with point to point integrations. Additionally its allows one to better define the data domain at hand and ensure its relevance to the organization&#8217;s use.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

