A glance at RSS code

In my last post, I described RSS (an exml code) as a feed method for retrieving news, information, and in out case, podcasts. Though the code itself is similar in structure to HTML, we need to remember that every space and character have meaning. I've learned this through some tough lessons as I've posted pods on the server and then scratch my head as to why Itunes or any other reader won't retrieve or even read the file. ...Usually it's because of an error in my code. Below is what a sample of the RSS (xml) code looks like. Again, similar to a web page where we see all of the content layed out with images, etc., what is behind all of that is a lot of code. Podcast feeds are read based on similar code that you see here. The objective is not deviating too much from what you have set up so that less time is spent on thinking and more time is spent of production. ...more to come...

Vehicles for Professional Development's Podcasts

There are a variety of ways to deliver podcasts. In particular, our (HRD) initial plan was to use Itunes as the primary vehicle to deliver the content since Itunes is a cross-platform (both MAC and PC) application. ...From there, users who have a fifth generation IPOD (video IPOD) can then download to their ipods for greater mobility. As plans do typically change, the primary delivery tool is now the RSS Feed that is read by the Safari browser, which comes with a built-in reader. PC users must download any number of RSS readers such as PLUCK, etc.

What this means technically is additional code that must be written so that now both RSS readers and ITUNES read and deliver the same content. If you're familiar with the fact that Web pages are programmed in the HTML language, RSS code is written in the XML language (just another language for the World Wide Web applications).

...and as a safe guard for those who do not have (or use) ITUNES, we (HRD) create HTML versions of that XML page so that users can pull up a typical looking Web page and view/download what the rest of the ITunes/safari/etc., users see.

...more on this to come...

PODCASTING, magic or just smoke and mirrors?

PODCASTING, magic or just smoke and mirrors?

Creating a pod is just half the fun. In terms of complexity, just about anyone with very rudimentary technology can create a pod. For most of us, we just create them, find a hosting site on the Web and upload them. That’s it…magically there they are on the Web!

…Actually…though it may not be magic to host podcasts, there are several things that need to be in place on the technical side in order for the magic to happen. Otherwise, you end up with just smoke and mirrors (broken links and dashed dreams of why my pods don’t work).

… and being on the technical end of this magic trick has taught me a lot about what it takes to host and manage podcasts for Broward County Public Schools’ Professional Development department, AKA HRD, AKA Staff Development, AKA Podcasters Rulers of the World J

Here is some of what I’ve learned from the first days:

First, Web servers come in many flavors and it doesn’t really matter which one it is. In our case, Broward Schools maintains a Windows server running Internet Information Services (IIS), the software that makes all of the pretty Web pages appear in your browser. This is where we host every Web site for Broward County Public Schools and by default, where BCPS HRD would host their content including their podcasts.

Second, podcasts files come in different flavors. You have your audio files (.mp3 and .m4a) and you video files (.mov and .mp4 for those delivered via I Tunes).

Third, in order for any of these three files to download via Itunes or an RSS feed, these file types must be added to the MIME types configuration within IIS. In other words, we must tell the Web server to recognize these files so that they will properly download and play via the appropriate browser. ……….magic!

…to be continued

Providing Support

testing content