<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Free Cyberlaw Syllabi</title>
	<atom:link href="http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/</link>
	<description>Information, Law, and the Law of Information</description>
	<lastBuildDate>Tue, 24 Nov 2009 00:08:14 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Info/Law &#187; Open Access Law, or: Should Law Professors Write for Wikipedia?</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/comment-page-1/#comment-3241</link>
		<dc:creator>Info/Law &#187; Open Access Law, or: Should Law Professors Write for Wikipedia?</dc:creator>
		<pubDate>Tue, 30 Jan 2007 19:48:01 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/#comment-3241</guid>
		<description>[...] This is unfortunate. One of the things I liked about the class Derek and I co-taught last spring is that we were able to dispense entirely with a textbook and rely entirely on online readings, some of which were updated mere days before the class in which they would be taught. It lent an air of immediacy to the course content that I think was particularly appropriate in view of the au courant subject matter. The day of doing that routinely and easily in a law school setting may still be a ways off (although some bold cyberprofs have taken the plunge), but it&#8217;s still an ambition of mine. [...]</description>
		<content:encoded><![CDATA[<p>[...] This is unfortunate. One of the things I liked about the class Derek and I co-taught last spring is that we were able to dispense entirely with a textbook and rely entirely on online readings, some of which were updated mere days before the class in which they would be taught. It lent an air of immediacy to the course content that I think was particularly appropriate in view of the au courant subject matter. The day of doing that routinely and easily in a law school setting may still be a ways off (although some bold cyberprofs have taken the plunge), but it&#8217;s still an ambition of mine. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: book and sword : gratitude and revenge &#187; a course on participatory media and collective action</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/comment-page-1/#comment-733</link>
		<dc:creator>book and sword : gratitude and revenge &#187; a course on participatory media and collective action</dc:creator>
		<pubDate>Thu, 17 Aug 2006 01:52:39 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/#comment-733</guid>
		<description>[...] I think it is great how they used a wiki to publish their syllabus online. It is sad to notice a trend where syllabi increasingly are hidden and not made public, and there is really very little reason to hide them, right? So this class syllabus is a great exception. In addition, Tim Armstrong of Info/Law found this great collection by Jessica Litman of online syllabi on the topics of internet law. Whereas these are bottom-up examples of what I see as attempts to free up education, Wikiversity is a more top-down driven example that just started and which I hope will be an aggregator of these online syllabi. [...]</description>
		<content:encoded><![CDATA[<p>[...] I think it is great how they used a wiki to publish their syllabus online. It is sad to notice a trend where syllabi increasingly are hidden and not made public, and there is really very little reason to hide them, right? So this class syllabus is a great exception. In addition, Tim Armstrong of Info/Law found this great collection by Jessica Litman of online syllabi on the topics of internet law. Whereas these are bottom-up examples of what I see as attempts to free up education, Wikiversity is a more top-down driven example that just started and which I hope will be an aggregator of these online syllabi. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William McGeveran</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/comment-page-1/#comment-732</link>
		<dc:creator>William McGeveran</dc:creator>
		<pubDate>Wed, 16 Aug 2006 20:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/#comment-732</guid>
		<description>Hear, hear, Tim!

Hopefully as professors get more comfortable with the technology they will be more inclined to alter the default option of locked-up content.</description>
		<content:encoded><![CDATA[<p>Hear, hear, Tim!</p>
<p>Hopefully as professors get more comfortable with the technology they will be more inclined to alter the default option of locked-up content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Armstrong</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/comment-page-1/#comment-731</link>
		<dc:creator>Tim Armstrong</dc:creator>
		<pubDate>Wed, 16 Aug 2006 19:10:23 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/#comment-731</guid>
		<description>Yes, I&#039;ve heard variations on those same themes from some of my colleagues.  Certainly the point about preserving the confidentiality of student information is a good one, and I wouldn&#039;t suggest the contrary.  But there are plenty of ways to achieve that.  At last spring&#039;s &lt;a rel=&quot;nofollow&quot; href=&quot;http://cyber.law.harvard.edu/home/bloggership&quot;&gt;bloggership conference&lt;/a&gt;, &lt;a rel=&quot;nofollow&quot; href=&quot;http://www.discourse.net/&quot;&gt;Michael Froomkin&lt;/a&gt; suggested maintaining a password-protected class blog where students could participate without fear that something they said might come back to bite them down the road.  You can achieve the same thing with &lt;a rel=&quot;nofollow&quot; href=&quot;http://h2o.law.harvard.edu/&quot;&gt;H2O&lt;/a&gt;, I believe, by marking the rotisserie boards and discussion forums as visible only to members of the group, then restricting group membership to students who are registered for your class.  Maintaining this sort of confidentiality isn&#039;t just a good idea (because it fosters freer discussion), it&#039;s the law, and clearly worthwhile.

Using an integrated CMS suite yields advantages in ease of use (undeniably important, particularly for less tech-savvy faculty), but as you suggest, seems to impose costs in the form of reduced granularity of control.  When deployed in the fashion that seems most common, CMS overprotects; it makes hiding information that doesn&#039;t need to be confidential part of the price of hiding information that does.  Litman thinks that&#039;s an unfortunate and unnecessary result, and I&#039;m inclined to agree.  Which is not to deny the institutional pressures that foster the use of closed systems, only to suggest that we remain mindful of their limitations and keep the university&#039;s broader missions in mind when determining whether and how to use them.</description>
		<content:encoded><![CDATA[<p>Yes, I&#8217;ve heard variations on those same themes from some of my colleagues.  Certainly the point about preserving the confidentiality of student information is a good one, and I wouldn&#8217;t suggest the contrary.  But there are plenty of ways to achieve that.  At last spring&#8217;s <a rel="nofollow" href="http://cyber.law.harvard.edu/home/bloggership">bloggership conference</a>, <a rel="nofollow" href="http://www.discourse.net/">Michael Froomkin</a> suggested maintaining a password-protected class blog where students could participate without fear that something they said might come back to bite them down the road.  You can achieve the same thing with <a rel="nofollow" href="http://h2o.law.harvard.edu/">H2O</a>, I believe, by marking the rotisserie boards and discussion forums as visible only to members of the group, then restricting group membership to students who are registered for your class.  Maintaining this sort of confidentiality isn&#8217;t just a good idea (because it fosters freer discussion), it&#8217;s the law, and clearly worthwhile.</p>
<p>Using an integrated CMS suite yields advantages in ease of use (undeniably important, particularly for less tech-savvy faculty), but as you suggest, seems to impose costs in the form of reduced granularity of control.  When deployed in the fashion that seems most common, CMS overprotects; it makes hiding information that doesn&#8217;t need to be confidential part of the price of hiding information that does.  Litman thinks that&#8217;s an unfortunate and unnecessary result, and I&#8217;m inclined to agree.  Which is not to deny the institutional pressures that foster the use of closed systems, only to suggest that we remain mindful of their limitations and keep the university&#8217;s broader missions in mind when determining whether and how to use them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: William McGeveran</title>
		<link>http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/comment-page-1/#comment-730</link>
		<dc:creator>William McGeveran</dc:creator>
		<pubDate>Wed, 16 Aug 2006 18:32:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/2006/08/16/free-cyberlaw-syllabi/#comment-730</guid>
		<description>Tim:

In the &lt;a target=&quot;_blank&quot; href=&quot;http://cyber.law.harvard.edu/media/files/copyrightandeducation.html&quot;&gt;Digital Learning paper&lt;/a&gt; (shameless plug once again!) &lt;a target=&quot;_blank&quot; href=&quot;http://cyber.law.harvard.edu/media/files/copyrightandeducation.html#4_2_5&quot;&gt;we found&lt;/a&gt; that a lot of universities encourage the use of integrated course management systems (CMS).  As a result, there are pressures and intertia that lead to firewalls surrounding &lt;strong&gt;everything &lt;/strong&gt;within the CMS.

It is deemed undesirable to make certain kinds of content public.  Often this makes sense.  Many CMS include personal data about students (the system here at Minnesota has student pictures, addresses, e-mail); discussion forums where the desired student openness requires keeping it within the confines of the class; and, of course, copyrighted material (whether used illicitly or under a license).

Once you have an integrated system with any of those kinds of presumptively private items, then the path of least resistance is to plop it all behind the wall rather than picking and choosing among different types of content.</description>
		<content:encoded><![CDATA[<p>Tim:</p>
<p>In the <a target="_blank" href="http://cyber.law.harvard.edu/media/files/copyrightandeducation.html">Digital Learning paper</a> (shameless plug once again!) <a target="_blank" href="http://cyber.law.harvard.edu/media/files/copyrightandeducation.html#4_2_5">we found</a> that a lot of universities encourage the use of integrated course management systems (CMS).  As a result, there are pressures and intertia that lead to firewalls surrounding <strong>everything </strong>within the CMS.</p>
<p>It is deemed undesirable to make certain kinds of content public.  Often this makes sense.  Many CMS include personal data about students (the system here at Minnesota has student pictures, addresses, e-mail); discussion forums where the desired student openness requires keeping it within the confines of the class; and, of course, copyrighted material (whether used illicitly or under a license).</p>
<p>Once you have an integrated system with any of those kinds of presumptively private items, then the path of least resistance is to plop it all behind the wall rather than picking and choosing among different types of content.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
