<?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"
	>
<channel>
	<title>Comments on: Who&#8217;s Afraid of iTunes U?</title>
	<atom:link href="http://mfeldstein.com/whos_afraid_of_itunes_u/feed/" rel="self" type="application/rss+xml" />
	<link>http://mfeldstein.com/whos_afraid_of_itunes_u/</link>
	<description>What Michael Feldstein Is Learning About Online Learning...Online</description>
	<pubDate>Thu, 20 Nov 2008 07:12:59 +0000</pubDate>
	
		<item>
		<title>By: Jim Greenberg</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-312</link>
		<dc:creator>Jim Greenberg</dc:creator>
		<pubDate>Thu, 09 Mar 2006 19:30:54 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-312</guid>
		<description>I would be interested in cross-campus collaboration ideas and talking about the pros and cons. I would be interested in cross-campus collaboration ideas and talking about the pros and cons.  I have begun to talk to my Alumni Office, Student Affairs Office and Music Industry Program for ideas on how they might use this.  We don't have crystal clear ideas yet, but we do find the concept intriguing. 

 As for missing you at TLT, my campus responsibilities have taken over my professional life.  The good news is my campus has gotten its act together with technology support and integration.  This has resulted in my needing to focus all my attention here and being scarce at SUNY wide things.  I do miss things like STC, Wizard, TLT, for sure, but I am enjoying the marvelous opportunities to do interesting work on my campus.</description>
		<content:encoded><![CDATA[<p>I would be interested in cross-campus collaboration ideas and talking about the pros and cons. I would be interested in cross-campus collaboration ideas and talking about the pros and cons.  I have begun to talk to my Alumni Office, Student Affairs Office and Music Industry Program for ideas on how they might use this.  We don&#8217;t have crystal clear ideas yet, but we do find the concept intriguing. </p>
<p> As for missing you at TLT, my campus responsibilities have taken over my professional life.  The good news is my campus has gotten its act together with technology support and integration.  This has resulted in my needing to focus all my attention here and being scarce at SUNY wide things.  I do miss things like STC, Wizard, TLT, for sure, but I am enjoying the marvelous opportunities to do interesting work on my campus.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Feldstein</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-309</link>
		<dc:creator>Michael Feldstein</dc:creator>
		<pubDate>Sat, 04 Mar 2006 01:15:22 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-309</guid>
		<description>Jim! Glad you found me. (And sorry we somehow missed each other at TLT....)

Using iTunes U for social outreach to alumni and students is interesting; it hadn't occurred to me. Let's catch up about this via email; there's a lot of interest at a number of SUNY campuses and I think we can do some interesting cross-campus collaboration here.</description>
		<content:encoded><![CDATA[<p>Jim! Glad you found me. (And sorry we somehow missed each other at TLT&#8230;.)</p>
<p>Using iTunes U for social outreach to alumni and students is interesting; it hadn&#8217;t occurred to me. Let&#8217;s catch up about this via email; there&#8217;s a lot of interest at a number of SUNY campuses and I think we can do some interesting cross-campus collaboration here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Greenberg</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-308</link>
		<dc:creator>Jim Greenberg</dc:creator>
		<pubDate>Sat, 04 Mar 2006 00:06:55 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-308</guid>
		<description>Michael, 

Nice series on iTunes U.  We here at SUNY Oneonta just received word from Apple that we have been accepted into this program.  We are looking at learning as we go and initially using it to reach out to Alumni, the general public and also give our students a place to post.  For example, we have a large number of student musicans that could use this to post their music.  

We don't see this replacing our content managment or learning managmnet software at all (at this point).  Rather just another option in the tools to provide content.</description>
		<content:encoded><![CDATA[<p>Michael, </p>
<p>Nice series on iTunes U.  We here at SUNY Oneonta just received word from Apple that we have been accepted into this program.  We are looking at learning as we go and initially using it to reach out to Alumni, the general public and also give our students a place to post.  For example, we have a large number of student musicans that could use this to post their music.  </p>
<p>We don&#8217;t see this replacing our content managment or learning managmnet software at all (at this point).  Rather just another option in the tools to provide content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Feldstein</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-301</link>
		<dc:creator>Michael Feldstein</dc:creator>
		<pubDate>Sun, 19 Feb 2006 03:35:54 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-301</guid>
		<description>Nope, it's just bandwidth (which is &lt;i&gt;not&lt;/i&gt; a fixed cost in the US) and disk space. A lot of IT departments in US schools put sharp limits on large file sharing. It's hard to say how much of this is real cost limitation and how much is just fear of opening the floodgates, but either way the practical effect is that faculty and, more to the poiint, students aren't free to share multimedia files without sharp limitations.</description>
		<content:encoded><![CDATA[<p>Nope, it&#8217;s just bandwidth (which is <i>not</i> a fixed cost in the US) and disk space. A lot of IT departments in US schools put sharp limits on large file sharing. It&#8217;s hard to say how much of this is real cost limitation and how much is just fear of opening the floodgates, but either way the practical effect is that faculty and, more to the poiint, students aren&#8217;t free to share multimedia files without sharp limitations.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Dale</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-300</link>
		<dc:creator>John Dale</dc:creator>
		<pubDate>Sun, 19 Feb 2006 00:36:48 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-300</guid>
		<description>&gt; For most institutions, setting up a 
&gt; distribution system for multimedia 
&gt; files would be cost-prohibitive

I'm curious as to what you think the prohibitive costs would be.  The two factors I can think of are disk space (cheap, and getting cheaper all the time) and bandwidth (in the UK, at least, bandwidth is a fixed cost for HE institutions for more capacity than we come close to using).  Are there ways in which these two could be cost-prohibitive that I'm not seeing, or are there other factors I'm overlooking?</description>
		<content:encoded><![CDATA[<p>> For most institutions, setting up a<br />
> distribution system for multimedia<br />
> files would be cost-prohibitive</p>
<p>I&#8217;m curious as to what you think the prohibitive costs would be.  The two factors I can think of are disk space (cheap, and getting cheaper all the time) and bandwidth (in the UK, at least, bandwidth is a fixed cost for HE institutions for more capacity than we come close to using).  Are there ways in which these two could be cost-prohibitive that I&#8217;m not seeing, or are there other factors I&#8217;m overlooking?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-293</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Thu, 16 Feb 2006 21:18:56 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-293</guid>
		<description>Yes, I did goof a bit in my thinking on the hosting bit of the final content. The having a backup is not really a big worry, since nearly any audio/video I have done that is streamed or podcasted does not just exist in its final server delivered form- there are the original source audio and video files which are used to generate the final mp3, m4a, etc. So it is really a workflow issue to consider generating content in perhaps two forms/places.

The URL masking is something I still stand on as a small fixable issue. Try this. Find a URL for a podcast feed from anywhere else on the web. Copy it. In iTunes, use the Subscribe option where you can paste in the URL. 

Now when you have this feed embedded in iTunes, try to find a place where you can locate that URL, and copy/paste it outside of iTunes. I have looked high and low- the only place it is displayed (under Get Info for a feed) *** it is not copy-able *** This is either a minor software glitch (I hope) or a heinous plot. So for that matter, using anyother podcatcher would necessitate doing something like writing out the URL by hand on a piece of paper, and then typing it back in to the not iTunes catcher.

This disfunction, IMHO, is in serious conflict with Apple's own interface guidelines. I would like to hear an offical reason for this, since it has been weeks since Jon Udell posted this. This is the vague-ness which gives Apple a bad rap.</description>
		<content:encoded><![CDATA[<p>Yes, I did goof a bit in my thinking on the hosting bit of the final content. The having a backup is not really a big worry, since nearly any audio/video I have done that is streamed or podcasted does not just exist in its final server delivered form- there are the original source audio and video files which are used to generate the final mp3, m4a, etc. So it is really a workflow issue to consider generating content in perhaps two forms/places.</p>
<p>The URL masking is something I still stand on as a small fixable issue. Try this. Find a URL for a podcast feed from anywhere else on the web. Copy it. In iTunes, use the Subscribe option where you can paste in the URL. </p>
<p>Now when you have this feed embedded in iTunes, try to find a place where you can locate that URL, and copy/paste it outside of iTunes. I have looked high and low- the only place it is displayed (under Get Info for a feed) *** it is not copy-able *** This is either a minor software glitch (I hope) or a heinous plot. So for that matter, using anyother podcatcher would necessitate doing something like writing out the URL by hand on a piece of paper, and then typing it back in to the not iTunes catcher.</p>
<p>This disfunction, IMHO, is in serious conflict with Apple&#8217;s own interface guidelines. I would like to hear an offical reason for this, since it has been weeks since Jon Udell posted this. This is the vague-ness which gives Apple a bad rap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Feldstein</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-291</link>
		<dc:creator>Michael Feldstein</dc:creator>
		<pubDate>Thu, 16 Feb 2006 08:46:48 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-291</guid>
		<description>Chris is correct; iTunes U &lt;i&gt;does&lt;/i&gt; store content, but Apple encourages universities to think about iTunes U as a distribution mechanism rather than a long-term repository. In other words, just as you should keep your source documents for a course in, say, Blackboard stored somewhere other than &lt;i&gt;only&lt;/i&gt; in the current semester's course instance, keep your source files for iTunes U backed up somewhere else (or integrate iTunes U directly with your repository). 

As for what happens after 2007, it's not unreasonable to wonder, but it's also not unreasonable for Apple to decide that they can't guarantee free forever until they understand their long-term cost structures better for what amounts to a pilot program. The main point of my post is that Apple has no profit motive to charge, since it's not really a viable business to do so and since they get more financial benefit by giving it away as part of their branding campaign.

I'm not sure about the URL masking; I'm pretty sure that it's possible to use a non-iTunes client to podcatch from iTunes U but I don't know the details. I'll try to find out.

Regarding their degree of openness about their plans...well...they let me blog about it, so they're not being &lt;i&gt;too&lt;/i&gt; secretive. If you think about this as a non-revenue-generating operation with costs that are not fully known yet, it makes sense that they might go for a soft launch and not try to trumpet the details too widely until they have all the pieces in place. My sense is that they are feeling their way along with this somewhat. But really, I'm just guessing.</description>
		<content:encoded><![CDATA[<p>Chris is correct; iTunes U <i>does</i> store content, but Apple encourages universities to think about iTunes U as a distribution mechanism rather than a long-term repository. In other words, just as you should keep your source documents for a course in, say, Blackboard stored somewhere other than <i>only</i> in the current semester&#8217;s course instance, keep your source files for iTunes U backed up somewhere else (or integrate iTunes U directly with your repository). </p>
<p>As for what happens after 2007, it&#8217;s not unreasonable to wonder, but it&#8217;s also not unreasonable for Apple to decide that they can&#8217;t guarantee free forever until they understand their long-term cost structures better for what amounts to a pilot program. The main point of my post is that Apple has no profit motive to charge, since it&#8217;s not really a viable business to do so and since they get more financial benefit by giving it away as part of their branding campaign.</p>
<p>I&#8217;m not sure about the URL masking; I&#8217;m pretty sure that it&#8217;s possible to use a non-iTunes client to podcatch from iTunes U but I don&#8217;t know the details. I&#8217;ll try to find out.</p>
<p>Regarding their degree of openness about their plans&#8230;well&#8230;they let me blog about it, so they&#8217;re not being <i>too</i> secretive. If you think about this as a non-revenue-generating operation with costs that are not fully known yet, it makes sense that they might go for a soft launch and not try to trumpet the details too widely until they have all the pieces in place. My sense is that they are feeling their way along with this somewhat. But really, I&#8217;m just guessing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris L</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-290</link>
		<dc:creator>Chris L</dc:creator>
		<pubDate>Thu, 16 Feb 2006 02:55:13 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-290</guid>
		<description>Alan writes "What was helpful here is the reminder that the source content does not lie in iTunes- the podcasts are thus referring to content we still need to store in our own sites, servers, etc-- is that correct? iTunes is merely the handy referrer and link in the plaback chain of content?"

I don't believe that is correct. From what I am seeing, Apple does store the podcasts and information on their servers. 

The larger issue-- that they explicitly indicate they won't be an archive/repository is an interesting one. One of the benefits of iTunes U, as envisioned by some commentators, is that it relieves them of the infrastructure needed for storage and archiving. I wonder what Apple's conditions will be for retention?

At any rate, it seems to me that any program using the service would be wise to mirror content (easy enough to do) and certainly retain it for long term access. iTunes U is-- as these articles so clearly spell out-- a marketing tool. Use it, maybe, but not use it SOLELY.</description>
		<content:encoded><![CDATA[<p>Alan writes &#8220;What was helpful here is the reminder that the source content does not lie in iTunes- the podcasts are thus referring to content we still need to store in our own sites, servers, etc&#8211; is that correct? iTunes is merely the handy referrer and link in the plaback chain of content?&#8221;</p>
<p>I don&#8217;t believe that is correct. From what I am seeing, Apple does store the podcasts and information on their servers. </p>
<p>The larger issue&#8211; that they explicitly indicate they won&#8217;t be an archive/repository is an interesting one. One of the benefits of iTunes U, as envisioned by some commentators, is that it relieves them of the infrastructure needed for storage and archiving. I wonder what Apple&#8217;s conditions will be for retention?</p>
<p>At any rate, it seems to me that any program using the service would be wise to mirror content (easy enough to do) and certainly retain it for long term access. iTunes U is&#8211; as these articles so clearly spell out&#8211; a marketing tool. Use it, maybe, but not use it SOLELY.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-289</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Wed, 15 Feb 2006 20:37:59 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-289</guid>
		<description>oops a wasted comment since I forgot to check "notify".</description>
		<content:encoded><![CDATA[<p>oops a wasted comment since I forgot to check &#8220;notify&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://mfeldstein.com/whos_afraid_of_itunes_u/#comment-288</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Wed, 15 Feb 2006 20:37:24 +0000</pubDate>
		<guid isPermaLink="false">1589233586#comment-288</guid>
		<description>Thanks so much Michael for the semi-inside scoops on iTunes U. It is very valuable to us here trying to understand what is on the table.

The questions I have are why do we have to guess what the plan, strategy is from Apple? There is some degree of opaqueness to them that maybe is a plan or not, but the side effect is conjuring up notions of conspiracy from those trying to "guess the apple".

The vagueness of the "beyond 2000" plans is worrisome. Is it really unreasonable to wonder what happens past then?

Why does iTunes mask the URLs of podcasts? You can see, them, but there is no way to copy/paste them elsewhere outside of iTunes, say to another iPodder type app or just to use in some other RSS enabled application. This is either a simple techical oversight or .... a means of evil lock in. It seems silly to hide a piece of data that at somepoint a user enters inside iTunes.

What was helpful here is the reminder that the source content does not lie in iTunes- the podcasts are thus referring to content we still need to store in our own sites, servers, etc-- is that correct? iTunes is merely the handy referrer and link in the plaback chain of content?</description>
		<content:encoded><![CDATA[<p>Thanks so much Michael for the semi-inside scoops on iTunes U. It is very valuable to us here trying to understand what is on the table.</p>
<p>The questions I have are why do we have to guess what the plan, strategy is from Apple? There is some degree of opaqueness to them that maybe is a plan or not, but the side effect is conjuring up notions of conspiracy from those trying to &#8220;guess the apple&#8221;.</p>
<p>The vagueness of the &#8220;beyond 2000&#8243; plans is worrisome. Is it really unreasonable to wonder what happens past then?</p>
<p>Why does iTunes mask the URLs of podcasts? You can see, them, but there is no way to copy/paste them elsewhere outside of iTunes, say to another iPodder type app or just to use in some other RSS enabled application. This is either a simple techical oversight or &#8230;. a means of evil lock in. It seems silly to hide a piece of data that at somepoint a user enters inside iTunes.</p>
<p>What was helpful here is the reminder that the source content does not lie in iTunes- the podcasts are thus referring to content we still need to store in our own sites, servers, etc&#8211; is that correct? iTunes is merely the handy referrer and link in the plaback chain of content?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.298 seconds -->
