<?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/"
		>
<channel>
	<title>Comments on: Discovering Instructional Design 12: the ICARE Model</title>
	<atom:link href="http://michaelhanley.ie/elearningcurve/discovering-instructional-design-12-the-icare-model/2009/06/11/feed/" rel="self" type="application/rss+xml" />
	<link>http://michaelhanley.ie/elearningcurve/discovering-instructional-design-12-the-icare-model/2009/06/11/</link>
	<description>Michael Hanley&#039;s blog about e-learning, web-based elearning, technology in education, e-learning tools, learning 2.0 (blogs and podcasts), &#38; continuous professional development.</description>
	<lastBuildDate>Sat, 24 Dec 2011 19:09:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Discovering Instructional Design 13: ICARE Model – Middlesex University’s experience &#124; E-Learning Curve Blog</title>
		<link>http://michaelhanley.ie/elearningcurve/discovering-instructional-design-12-the-icare-model/2009/06/11/comment-page-1/#comment-532</link>
		<dc:creator>Discovering Instructional Design 13: ICARE Model – Middlesex University’s experience &#124; E-Learning Curve Blog</dc:creator>
		<pubDate>Fri, 12 Jun 2009 13:34:17 +0000</pubDate>
		<guid isPermaLink="false">http://michaelhanley.ie/elearningcurve/discovering-instructional-design-12-the-icare-model/2009/06/11/#comment-532</guid>
		<description>[...] I discussed yesterday, the ICARE approach is a distillation of the Dick and Carey Model for instructional design. Today, [...]</description>
		<content:encoded><![CDATA[<p>[...] I discussed yesterday, the ICARE approach is a distillation of the Dick and Carey Model for instructional design. Today, [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

