<?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: A distributed, multi-client courseware</title>
	<atom:link href="http://teleogistic.net/2010/05/a-distributed-multi-client-courseware/feed/" rel="self" type="application/rss+xml" />
	<link>http://teleogistic.net/2010/05/a-distributed-multi-client-courseware/</link>
	<description></description>
	<lastBuildDate>Wed, 16 May 2012 17:57:41 -0400</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: The Results of an Unconference - ProfHacker - The Chronicle of Higher Education</title>
		<link>http://teleogistic.net/2010/05/a-distributed-multi-client-courseware/comment-page-1/#comment-31750</link>
		<dc:creator>The Results of an Unconference - ProfHacker - The Chronicle of Higher Education</dc:creator>
		<pubDate>Fri, 11 Mar 2011 15:13:44 +0000</pubDate>
		<guid isPermaLink="false">http://teleogistic.net/?p=793#comment-31750</guid>
		<description>[...] Another group found some time to updated some code for Zotero. And another group came up with a possible answer to the ever-present lament that &#8220;All courseware sucks!&#8221; There were groups building game [...]</description>
		<content:encoded><![CDATA[<p>[...] Another group found some time to updated some code for Zotero. And another group came up with a possible answer to the ever-present lament that &#8220;All courseware sucks!&#8221; There were groups building game [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#187; Evolution of Education Damon Cook</title>
		<link>http://teleogistic.net/2010/05/a-distributed-multi-client-courseware/comment-page-1/#comment-12382</link>
		<dc:creator>&#187; Evolution of Education Damon Cook</dc:creator>
		<pubDate>Fri, 16 Jul 2010 07:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://teleogistic.net/?p=793#comment-12382</guid>
		<description>[...] published a study on hybrid LMSs, which may help open the discussion.  I&#8217;m definitely liking Boone Gorge&#8217;s theories on abstracting content from platform for a &#8220;distributed, multi-cl... but this will take a deal of development.  Who&#8217;s [...]</description>
		<content:encoded><![CDATA[<p>[...] published a study on hybrid LMSs, which may help open the discussion.  I&#8217;m definitely liking Boone Gorge&#8217;s theories on abstracting content from platform for a &#8220;distributed, multi-cl&#8230; but this will take a deal of development.  Who&#8217;s [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Boone Gorges</title>
		<link>http://teleogistic.net/2010/05/a-distributed-multi-client-courseware/comment-page-1/#comment-10449</link>
		<dc:creator>Boone Gorges</dc:creator>
		<pubDate>Mon, 24 May 2010 08:15:16 +0000</pubDate>
		<guid isPermaLink="false">http://teleogistic.net/?p=793#comment-10449</guid>
		<description>Thanks for the thoughts, Luke.

I think that a default system is the beginning of the answer to your question about critical platform choice. You&#039;re right that defaults are privileged, but certainly no more so than *sole* options. Platform-sampling might be built into a first-semester curriculum, and students could be encouraged to revisit and rejustify their choice periodically throughout their careers. I might start with the default, move to WP as a sophomore, and then to Drupal as a senior, for instance. I&#039;d still reap the benefit of not having to platform hop within a given term, without suffering lockin.

I agree with the spirit of your comment about the value of platform choice. I should note that my proposal, prima facie at least, shifts the generative process from faculty members making curricular decisions to students in a learning environment, which seems like a good trade off. Still, I can appreciate the force of what you&#039;re saying. In some cases it will be recommended and perhaps even necessary for a faculty member to require a given platform for a certain class. That might happen, for instance, in a publishing class, or a design class. But it wouldn&#039;t have to happen in every class, which I think is a good thing - while I&#039;m all for reflection and critical engagement with media, I don&#039;t think that the wheel needs to be reinvented for every semester or every professor or every class. There is some real value in being able to elide over this decision in certain kinds of classes.</description>
		<content:encoded><![CDATA[<p>Thanks for the thoughts, Luke.</p>
<p>I think that a default system is the beginning of the answer to your question about critical platform choice. You&#8217;re right that defaults are privileged, but certainly no more so than *sole* options. Platform-sampling might be built into a first-semester curriculum, and students could be encouraged to revisit and rejustify their choice periodically throughout their careers. I might start with the default, move to WP as a sophomore, and then to Drupal as a senior, for instance. I&#8217;d still reap the benefit of not having to platform hop within a given term, without suffering lockin.</p>
<p>I agree with the spirit of your comment about the value of platform choice. I should note that my proposal, prima facie at least, shifts the generative process from faculty members making curricular decisions to students in a learning environment, which seems like a good trade off. Still, I can appreciate the force of what you&#8217;re saying. In some cases it will be recommended and perhaps even necessary for a faculty member to require a given platform for a certain class. That might happen, for instance, in a publishing class, or a design class. But it wouldn&#8217;t have to happen in every class, which I think is a good thing &#8211; while I&#8217;m all for reflection and critical engagement with media, I don&#8217;t think that the wheel needs to be reinvented for every semester or every professor or every class. There is some real value in being able to elide over this decision in certain kinds of classes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luke</title>
		<link>http://teleogistic.net/2010/05/a-distributed-multi-client-courseware/comment-page-1/#comment-10435</link>
		<dc:creator>Luke</dc:creator>
		<pubDate>Sun, 23 May 2010 15:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://teleogistic.net/?p=793#comment-10435</guid>
		<description>Wow, Boone, a lot to think about here. 

Two concerns immediately come to my mind about a model like this as an &quot;enterprise solution,&quot; and I&#039;m curious what folks thought about these ?s at THATcamp.  

The first is that this model presupposes both the desire and the ability for students to make a critical choice about how online they want to do their coursework. Should we expect it of all of them? Only some? If so, which ones, and when?  You could address this by having a default platform, but as we all know, defaults are privileged.   

The second is that it absolves faculty members of making a choice for the platform through which students engage with course material, and switches that burden to students. There are definite arguments &lt;em&gt;for&lt;/em&gt; this, but one argument against it is that the process of choosing a platform is often pedagogically generative for faculty members. If the underlying argument is that the differences between CMS platforms will and should be flattened by bridging, then does that fact ultimately devalue the presence of a choice in the first place?

These points aside, your proposal creates all sorts of new and valuable questions that could certainly trump these concerns.</description>
		<content:encoded><![CDATA[<p>Wow, Boone, a lot to think about here. </p>
<p>Two concerns immediately come to my mind about a model like this as an &#8220;enterprise solution,&#8221; and I&#8217;m curious what folks thought about these ?s at THATcamp.  </p>
<p>The first is that this model presupposes both the desire and the ability for students to make a critical choice about how online they want to do their coursework. Should we expect it of all of them? Only some? If so, which ones, and when?  You could address this by having a default platform, but as we all know, defaults are privileged.   </p>
<p>The second is that it absolves faculty members of making a choice for the platform through which students engage with course material, and switches that burden to students. There are definite arguments <em>for</em> this, but one argument against it is that the process of choosing a platform is often pedagogically generative for faculty members. If the underlying argument is that the differences between CMS platforms will and should be flattened by bridging, then does that fact ultimately devalue the presence of a choice in the first place?</p>
<p>These points aside, your proposal creates all sorts of new and valuable questions that could certainly trump these concerns.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

