<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0" 
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">

<channel>
<title>elearningpost</title>
<link>http://www.elearningpost.com/</link>
<description></description>
<dc:language>en-us</dc:language>
<dc:creator>maish@elearningpost.com</dc:creator>
<dc:date>2006-01-10T16:30:57+08:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=2.661" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

<item>
<title> Update: New URLs for elearningpost RSS feeds</title>
<link>http://www.elearningpost.com/</link>
<description><![CDATA[<p>After a series of hiccups I finally got elearningpost back up again. Here's a brief chain of events: During Nov-Dec I received over 17,000 spam comments. When I tried to remove them, my database got corrupted. I was using BerkeleyDB with MovableType. So I had to revert to an Oct backup I had taken. Then instead of just importing entries back into a new version of Movable Type, I switched to Expression Engine. And again instead of just importing entries I made them all standards compliant. And instead of using the old interface, I created a new look to elearningpost, hopefully this is more simpler and cleaner. So all of these changes means that the RSS url has changed. Please update your aggregators to these URLS:<a href="http://www.elearningpost.com/blog/atom/">atom</a>, <a href="http://www.elearningpost.com/blog/rss2/">RSS 2.0</a>. More on the changes will follow.</p>]]></description>
<guid isPermaLink="false">7310@http://www.elearningpost.com/</guid>
<dc:subject>News</dc:subject>
<dc:date>2006-01-15T16:30:57+08:00</dc:date>
</item>


<item>
<title> Knowledge Management for Development Journal</title>
<link>http://www.elearningpost.com/archives/007309.asp</link>
<description><![CDATA[<p><a href="http://www.km4dev.org/journal/index.php/km4dj/issue/current">Nice articles</a> dealing with the role of culture in knowledge sharing. Via <a href="http://www.fullcirc.com/weblog/onfacblog.htm">Full Circle</a>.</p>]]></description>
<guid isPermaLink="false">7309@http://www.elearningpost.com/</guid>
<dc:subject>Knowledge Management</dc:subject>
<dc:date>2006-01-10T16:30:57+08:00</dc:date>
</item>
<item>
<title>Designing for the Web</title>
<link>http://www.elearningpost.com/archives/007308.asp</link>
<description><![CDATA[<p>Here's a <a href="http://www.digital-web.com/articles/designing_for_the_web/">reality check</a> when it comes to designing for the Web. The following constraints are covered:</p>

<ul><li>Resolution</li><li>Designing for browsers</li><li>Web-safe color</li><li>Graphics compression</li><li>Text</li></ul>]]></description>
<guid isPermaLink="false">7308@http://www.elearningpost.com/</guid>
<dc:subject>User Experience Design</dc:subject>
<dc:date>2006-01-10T16:23:59+08:00</dc:date>
</item>
<item>
<title>People as a Source of Breakthrough Innovation</title>
<link>http://www.elearningpost.com/archives/007307.asp</link>
<description><![CDATA[<p>Stefano Marzano, Chief Executive Officer and Chief Creative Director, Philips Design writes about how Philips goes about <a href="http://www.dmi.org/dmi/html/publications/news/ebulletin/05162MAR23.pdf">looking for design opportunities</a>. </p>

<blockquote>At Philips,we apply this approach to three things: our market,ourselves, and our interactions with our consumers...By combining all the insights we gain from looking at our market, ourselves, and the consumer interface, we can arrive at a general vision ofthe future. On that basis,we can then work out, for the next few years, what new types ofbenefits we should aim to provide, what new competences we need to do it, and how we should interact with our end users. </blockquote>]]></description>
<guid isPermaLink="false">7307@http://www.elearningpost.com/</guid>
<dc:subject>User Experience Design</dc:subject>
<dc:date>2006-01-10T09:28:34+08:00</dc:date>
</item>
<item>
<title>Adopt and Adapt</title>
<link>http://www.elearningpost.com/archives/007306.asp</link>
<description><![CDATA[<p>Mark Prensky on the need for schools to pick up the pace and start <a href="http://www.edutopia.org/magazine/ed1article.php?id=Art_1423&amp;issue=dec_05">integrating technology</a> more comprehensively:</p>

<p>So, let's not just adopt technology into our schools. Let's adapt it, push it, pull it, iterate with it, experiment with it, test it, and redo it, until we reach the point where we and our kids truly feel we've done our very best. Then, let's push it and pull it some more. And let's do it quickly, so the twenty-second century doesn't catch us by surprise with too much of our work undone.</p>]]></description>
<guid isPermaLink="false">7306@http://www.elearningpost.com/</guid>
<dc:subject>Learner Experience Design</dc:subject>
<dc:date>2006-01-06T07:52:47+08:00</dc:date>
</item>
<item>
<title>Podcast of BayCHI Events</title>
<link>http://www.elearningpost.com/archives/007305.asp</link>
<description><![CDATA[<p>A good <a href="http://www.baychi.org/podcast/">list of podcasts</a> on all things design -- from user research strategies to web2.0.</p>]]></description>
<guid isPermaLink="false">7305@http://www.elearningpost.com/</guid>
<dc:subject>User Experience Design</dc:subject>
<dc:date>2006-01-05T22:02:12+08:00</dc:date>
</item>
<item>
<title>Crash course in learning theory</title>
<link>http://www.elearningpost.com/archives/007304.asp</link>
<description><![CDATA[<p>A wonderful article describing <a href="http://headrush.typepad.com/creating_passionate_users/2006/01/crash_course_in.html">tips and techniques</a> to create engaging &#38; memorable learning moments:</p>

<blockquote>This is not a comprehensive look at the state of learning theory today, but it does include almost everything we think about in creating our books. And although it's geared toward blogs/writing virtually everything in here applies regardless of how you deliver the learning--you can easily adapt it to prentations, user documentation, or classroom learning. And remember, this is a BLOG, so don't expect academic rigor ; ) but I do have references, so leave a comment if there's something in particular you want.</blockquote>]]></description>
<guid isPermaLink="false">7304@http://www.elearningpost.com/</guid>
<dc:subject>Learner Experience Design</dc:subject>
<dc:date>2006-01-05T21:52:04+08:00</dc:date>
</item>
<item>
<title>Managing &apos;Glue&apos; at the BBC</title>
<link>http://www.elearningpost.com/archives/007303.asp</link>
<description><![CDATA[<p>An insightful article on <a href="http://www.currybet.net/articles/glue/">managing the brand identity</a> across multiple business functions across the BBC. The team depends on global navigation, search and classification to glue the different websites together.</p>]]></description>
<guid isPermaLink="false">7303@http://www.elearningpost.com/</guid>
<dc:subject>User Experience Design</dc:subject>
<dc:date>2006-01-05T21:14:32+08:00</dc:date>
</item>
<item>
<title>Horizontal knowledge</title>
<link>http://www.elearningpost.com/archives/007302.asp</link>
<description><![CDATA[<p><a href="http://sethgodin.typepad.com/seths_blog/2005/12/horizontal_know.html">Seth Godin</a> links to <a href="http://www.techcentralstation.com/060403A.html">this post</a> by Glenn Reynolds about horizontal knowledge -- the loosely coupled knowledge that you get by collaborating or by having a conversation. Vertical knowledge, on the other hand, is the stuff that is passed down from above, e.g., your bosses. I like the way common terms are being used to describe a fairly complex knowledge space. So, here's my list so far:</p>

<ul><li>Practice vs. Process</li><li>1st hand vs. nth hand</li><li>Horizontal vs. Vertical</li><li>Verb vs. Noun</li><li>Active vs. Passive</li><li>Us vs. Them</li></ul>]]></description>
<guid isPermaLink="false">7302@http://www.elearningpost.com/</guid>
<dc:subject>Knowledge Management</dc:subject>
<dc:date>2005-12-23T09:38:14+08:00</dc:date>
</item>


</channel>
</rss>