<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/rss2enclosuresfull.xsl" type="text/xsl" media="screen"?><?xml-stylesheet href="http://feeds.feedburner.com/~d/styles/itemcontent.css" type="text/css" media="screen"?><!-- generator="wordpress/2.0.4" --><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dtvmedia="http://participatoryculture.org/RSSModules/dtv/1.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>ptvGuy</title>
	<link>http://www.ptvguy.com</link>
	<description>Public Television Station Web Development</description>
	<pubDate>Sun, 10 Dec 2006 00:40:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>
	<language>en</language>
		<!-- podcast_generator="podPress/6.8" -->
		<copyright>©ptvGuy 2003-2006</copyright>
		<managingEditor>ptvguy@ptvguy.com (ptvGuy)</managingEditor>
		<webMaster>ptvguy@ptvguy.com</webMaster>
		<category>webdev</category>
		<ttl>1440</ttl>
		<itunes:keywords>webdev, PBS, public television, web development, web design, accessibility, webmaster, web 2.0</itunes:keywords>
		<itunes:subtitle>ptvguy</itunes:subtitle>
		<itunes:summary>A podcast about web development, web standards, and the creation and distribution of original web content with a focus on public television station web development.</itunes:summary>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:category text="Technology" />
<itunes:category text="Technology">
  <itunes:category text="Podcasting" />
</itunes:category>
<itunes:category text="Technology">
  <itunes:category text="Tech News" />
</itunes:category>
		<itunes:owner>
			<itunes:name>ptvGuy</itunes:name>
			<itunes:email>ptvguy@ptvguy.com</itunes:email>
		</itunes:owner>
		<itunes:block>No</itunes:block>
		<itunes:explicit>clean</itunes:explicit>
		<itunes:image href="http://www.ptvguy.com/wp-content/plugins/podpress/images/ptvGuyPodcast_large.jpg" />
		<image><link>http://creativecommons.org/licenses/by-nc-nd/2.0/</link><url>http://creativecommons.org/images/public/somerights20.gif</url><title>Some Rights Reserved</title></image>
		<creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/ptvguy" type="application/rss+xml" /><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Ffeeds.feedburner.com%2Fptvguy" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2Fptvguy" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Ffeeds.feedburner.com%2Fptvguy" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Ffeeds.feedburner.com%2Fptvguy" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Ffeeds.feedburner.com%2Fptvguy" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><feedburner:feedFlare href="http://odeo.com/listen/subscribe?feed=http%3A%2F%2Ffeeds.feedburner.com%2Fptvguy" src="http://odeo.com/img/badge-channel-black.gif">Subscribe with ODEO</feedburner:feedFlare><feedburner:feedFlare href="http://www.podnova.com/add.srf?url=http%3A%2F%2Ffeeds.feedburner.com%2Fptvguy" src="http://www.podnova.com/img_chicklet_podnova.gif">Subscribe with Podnova</feedburner:feedFlare><item>
		<title>Please DO Feed the Sites: Creating Outgoing Feeds</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/56917874/</link>
		<comments>http://www.ptvguy.com/please-do-feed-the-sites-creating-outgoing-feeds/#comments</comments>
		<pubDate>Mon, 04 Dec 2006 01:20:36 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>advertising</dc:subject>
	<dc:subject>browser</dc:subject>
	<dc:subject>coding</dc:subject>
	<dc:subject>content</dc:subject>
	<dc:subject>markup</dc:subject>
	<dc:subject>money</dc:subject>
	<dc:subject>original content</dc:subject>
	<dc:subject>PBS</dc:subject>
	<dc:subject>promotion</dc:subject>
	<dc:subject>SEO</dc:subject>
	<dc:subject>station</dc:subject>
	<dc:subject>time</dc:subject>
	<dc:subject>usability</dc:subject>
	<dc:subject>podcasting</dc:subject>
	<dc:subject>Movable Type</dc:subject>
	<dc:subject>WTIU</dc:subject>
	<dc:subject>Angela Jordan</dc:subject>
	<dc:subject>CMS</dc:subject>
	<dc:subject>plugins</dc:subject>
	<dc:subject>RSS</dc:subject>
	<dc:subject>feeds</dc:subject>
	<dc:subject>WordPress</dc:subject>
	<dc:subject>blogging tools</dc:subject>
	<dc:subject>database</dc:subject>
	<dc:subject>support</dc:subject>
	<dc:subject>membership</dc:subject>
	<dc:subject>value</dc:subject>
	<dc:subject>local</dc:subject>
	<dc:subject>URL</dc:subject>
	<dc:subject>revenues</dc:subject>
	<dc:subject>content distributors</dc:subject>
	<dc:subject>SSI</dc:subject>
	<dc:subject>self-sufficiency</dc:subject>
	<dc:subject>maintenance</dc:subject>
	<dc:subject>marketing</dc:subject>
	<dc:subject>new tools</dc:subject>
	<dc:subject>IE7</dc:subject>
	<dc:subject>Firefox</dc:subject>
	<dc:subject>Internet Explorer</dc:subject>
	<dc:subject>XML</dc:subject>
	<dc:subject>syndication</dc:subject>
	<dc:subject>Please DO Feed the Sites Series</dc:subject>
	<dc:subject>HTML to RSS</dc:subject>
	<dc:subject>RSSxl Generator</dc:subject>
	<dc:subject>WotZWot</dc:subject>
	<dc:subject>XML Wrench</dc:subject>
	<dc:subject>RSS Wizard</dc:subject>
	<dc:subject>Extralabs Software</dc:subject>
	<dc:subject>FeedForAll</dc:subject>
	<dc:subject>PRESSfeed</dc:subject>
	<dc:subject>Sally Falkow</dc:subject>
	<dc:subject>ONIX</dc:subject>
	<dc:subject>Newshour</dc:subject>
	<dc:subject>Newshour RSS feed tool</dc:subject>
	<dc:subject>Drupal</dc:subject>
	<dc:subject>Joomla</dc:subject>
	<dc:subject>Ang Zhuu Ming</dc:subject>
	<dc:subject>blogHelper</dc:subject>
	<dc:subject>Ross Johnson</dc:subject>
	<dc:subject>3.7 Designs</dc:subject>
	<dc:subject>RSS specification</dc:subject>
	<dc:subject>CDATA</dc:subject>
	<dc:subject>auto-discovery</dc:subject>
	<dc:subject>LINK tag</dc:subject>
	<dc:subject>syndic8</dc:subject>
	<dc:subject>FeedBurner</dc:subject>
	<dc:subject>nonprofit</dc:subject><dc:subject>3.7 Designs</dc:subject><dc:subject>advertising</dc:subject><dc:subject>Ang Zhuu Ming</dc:subject><dc:subject>Angela Jordan</dc:subject><dc:subject>auto discovery</dc:subject><dc:subject>blogging tools</dc:subject><dc:subject>blogHelper</dc:subject><dc:subject>browser</dc:subject><dc:subject>CDATA</dc:subject><dc:subject>CMS</dc:subject><dc:subject>coding</dc:subject><dc:subject>content</dc:subject><dc:subject>content distributors</dc:subject><dc:subject>database</dc:subject><dc:subject>Drupal</dc:subject><dc:subject>Extralabs Software</dc:subject><dc:subject>FeedBurner</dc:subject><dc:subject>FeedForAll</dc:subject><dc:subject>feeds</dc:subject><dc:subject>Firefox</dc:subject><dc:subject>HTML to RSS</dc:subject><dc:subject>IE7</dc:subject><dc:subject>Internet Explorer</dc:subject><dc:subject>Joomla</dc:subject><dc:subject>LINK tag</dc:subject><dc:subject>local</dc:subject><dc:subject>maintenance</dc:subject><dc:subject>marketing</dc:subject><dc:subject>markup</dc:subject><dc:subject>membership</dc:subject><dc:subject>money</dc:subject><dc:subject>Movable Type</dc:subject><dc:subject>new tools</dc:subject><dc:subject>Newshour</dc:subject><dc:subject>Newshour RSS feed tool</dc:subject><dc:subject>nonprofit</dc:subject><dc:subject>ONIX</dc:subject><dc:subject>original content</dc:subject><dc:subject>PBS</dc:subject><dc:subject>Please DO Feed the Sites Series</dc:subject><dc:subject>plugins</dc:subject><dc:subject>podcasting</dc:subject><dc:subject>PRESSfeed</dc:subject><dc:subject>promotion</dc:subject><dc:subject>revenues</dc:subject><dc:subject>Ross Johnson</dc:subject><dc:subject>RSS</dc:subject><dc:subject>RSS specification</dc:subject><dc:subject>RSS Wizard</dc:subject><dc:subject>RSSxl Generator</dc:subject><dc:subject>Sally Falkow</dc:subject><dc:subject>self sufficiency</dc:subject><dc:subject>SEO</dc:subject><dc:subject>SSI</dc:subject><dc:subject>station</dc:subject><dc:subject>support</dc:subject><dc:subject>syndic8</dc:subject><dc:subject>syndication</dc:subject><dc:subject>time</dc:subject><dc:subject>URL</dc:subject><dc:subject>usability</dc:subject><dc:subject>value</dc:subject><dc:subject>WordPress</dc:subject><dc:subject>WotZWot</dc:subject><dc:subject>WTIU</dc:subject><dc:subject>xml</dc:subject><dc:subject>XML Wrench</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/please-do-feed-the-sites-creating-outgoing-feeds/</guid>
		<description>There are numerous methods for the creation of an outgoing feed including the conversion of current HTML files to RSS, using fill-in-the-blank RSS creation forms like the new one from Newshour, and adapting database driven CMS tools.  With all that ease of RSS creation in mind, it's still important to leverage your feed, play nice with RSS, and do all the promotion you can.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=r0urBUnS"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=r0urBUnS" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=xUvnw55t"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=xUvnw55t" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=yMHHPxDw"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=yMHHPxDw" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=Cp0oBnJA"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=Cp0oBnJA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=8Rm6uza9"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=8Rm6uza9" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=MovFmlqx"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=MovFmlqx" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/please-do-feed-the-sites-creating-outgoing-feeds/feed/</wfw:commentRSS>
			
<itunes:duration>13:18</itunes:duration>
		<itunes:subtitle>Are you tired of all the geek bullies kicking virtual sand in your face, flexing their apps, and getting all the URLs? Have you ever ...</itunes:subtitle>
		<itunes:summary>Are you tired of all the geek bullies kicking virtual sand in your face, flexing their apps, and getting all the URLs? Have you ever looked at your site on the monitor and wished that you too could bulk up like the big geeks? Well, now you can.


Presenting Outgoing RSS Feeds:


They#39;re quick.


They#39;re easy.


They keep working even while you sleep.


No special diet.


No exercise.



Whatever your coding preference, we#39;ve got the plan for you. Whether you#39;d rather pop it right out of the bottle or create beautifully hand-crafted feeds we#39;ve got you covered. Order now, supplies are limited (only by your imagination.)


Sorry, folks, I just couldn#39;t resist that. ;)



Basically, the fastest way to begin putting an RSS feed out from a standard website is to convert already existing HTML pages to RSS XML. This works especially well if you#39;re already separating content like event announcements and program highlights into separate files and using SSIs to plug them into your page templates. However, some of the available tools will parse sections out of larger pages.


A good, free tool for this is the RSSxl Generator from WotZWot. This is a (seemingly permanent) beta application, so you might have to double-check the resulting XML. However, it does let you specify strings in your document that identify where the feed content starts and where individual RSS items and item descriptions are located.


XML:Wrench is another free tool. It#39;s a fairly decent (if simple) XML editor that will convert HTML to XML. Even if you limit the source HTML document to nothing but the basic feed content, you#39;ll still have to go through the code itself in the editor and do some cleanup.


The RSS Wizard is a fairly cheap solution from Extralabs Software  that generates "the RSS feed out of virtually any web page without having to edit it first." That#39;s the claim anyway. I say you#39;re better off checking code out for yourself, but, then, I#39;m known to be somewhat anal about these things.

Fill-In-the-Blanks RSS Creation


A fill-in-the-blanks form solution for the quick creation of RSS feeds is a distinct possibility to get you started. This is a good interim option until you have something better in place. This type of tool is available as a stand-alone desktop application or through web applications on other sites.


FeedForAll has one of the best known tools for the dynamic creation of RSS feeds, and the software, although powerful, is very cheap. Another paid option is PRESSfeed which actively promotes the use of RSS feeds for press releases and other forms of marketing and includes social bookmarking aspects and a number of other services.
Go there for Sally Falkow's blog on How to use RSS feeds in enterprise marketing and promotions if for no other reason.



The main fill-in-the-blanks solution I want to draw your attention to is a special resource created by the web team at ONIX specifically for the creation of station feeds. It seems that the folks at Newshour would like to see more stations syndicating their news content so that more local news can be picked up by the national Newshour site--especially local election coverage. Pretty smart of them, huh? The thing to remember about this web application from Newshour is that it will work for the creation of any RSS feed irregardless of its "newsworthiness." You simply enter the content directly into form fields, and it does the rest.



There are a couple quick caveats worth noting with this service. First of all, there#39;s a separate form to use if your feed will include podcasts. Podcasts require their own special code enclosures to be part of the feed, and, even though nearly any type of content can be syndicated by RSS, they#39;ve limited the content type to MP3s for this tool. Also, there#39;s currently a bug that leaves empty image enclosures if you don#39;t happen to</itunes:summary>
		<itunes:keywords>All, advertising, browser, coding, content, markup, money, original content, PBS, promotion, SEO, station, time, usability, podcasting, Movable Type, WTIU, Angela Jordan, CMS, plugins, RSS, feeds, WordPress, blogging tools, database, support, membership, value, local, URL, revenues, content distributors, SSI, self-sufficiency, maintenance, marketing, new tools, IE7, Firefox, Internet Explorer, XML, syndication, Please DO Feed the Sites Series, HTML to RSS, RSSxl Generator, WotZWot, XML Wrench, RSS Wizard, Extralabs Software, FeedForAll, PRESSfeed, Sally Falkow, ONIX, Newshour, Newshour RSS feed tool, Drupal, Joomla, Ang Zhuu Ming, blogHelper, Ross Johnson, 3.7 Designs, RSS specification, CDATA, auto-discovery, LINK tag, syndic8, FeedBurner, nonprofit</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>clean</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/please-do-feed-the-sites-creating-outgoing-feeds/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/57369273/ptvguy120306.mp3" length="3198676" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/70/0/ptvguy120306.mp3</feedburner:origEnclosureLink></item>
		<item>
		<title>Please DO Feed the Sites: What Is RSS?</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/51042094/</link>
		<comments>http://www.ptvguy.com/please-do-feed-the-sites-what-is-rss/#comments</comments>
		<pubDate>Sat, 18 Nov 2006 14:26:51 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>browser</dc:subject>
	<dc:subject>coding</dc:subject>
	<dc:subject>content</dc:subject>
	<dc:subject>money</dc:subject>
	<dc:subject>promotion</dc:subject>
	<dc:subject>search engine</dc:subject>
	<dc:subject>SEO</dc:subject>
	<dc:subject>station</dc:subject>
	<dc:subject>RSS</dc:subject>
	<dc:subject>feeds</dc:subject>
	<dc:subject>Web 2.0</dc:subject>
	<dc:subject>support</dc:subject>
	<dc:subject>membership</dc:subject>
	<dc:subject>value</dc:subject>
	<dc:subject>programs</dc:subject>
	<dc:subject>budget</dc:subject>
	<dc:subject>content distributors</dc:subject>
	<dc:subject>eGuide</dc:subject>
	<dc:subject>extensibility</dc:subject>
	<dc:subject>XML</dc:subject>
	<dc:subject>Creative Commons</dc:subject>
	<dc:subject>Tim O'Reilly</dc:subject>
	<dc:subject>Dave Winer</dc:subject>
	<dc:subject>Userland</dc:subject>
	<dc:subject>syndication</dc:subject>
	<dc:subject>Netscape</dc:subject>
	<dc:subject>Please DO Feed the Sites Series</dc:subject><dc:subject>browser</dc:subject><dc:subject>budget</dc:subject><dc:subject>coding</dc:subject><dc:subject>content</dc:subject><dc:subject>content distributors</dc:subject><dc:subject>Creative Commons</dc:subject><dc:subject>Dave Winer</dc:subject><dc:subject>eGuide</dc:subject><dc:subject>extensibility</dc:subject><dc:subject>feeds</dc:subject><dc:subject>membership</dc:subject><dc:subject>money</dc:subject><dc:subject>Netscape</dc:subject><dc:subject>Please DO Feed the Sites Series</dc:subject><dc:subject>programs</dc:subject><dc:subject>promotion</dc:subject><dc:subject>RSS</dc:subject><dc:subject>search engine</dc:subject><dc:subject>SEO</dc:subject><dc:subject>station</dc:subject><dc:subject>support</dc:subject><dc:subject>syndication</dc:subject><dc:subject>Tim OReilly</dc:subject><dc:subject>Userland</dc:subject><dc:subject>value</dc:subject><dc:subject>Web 2.0</dc:subject><dc:subject>xml</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/please-do-feed-the-sites-what-is-rss/</guid>
		<description>To explain what RSS is and why it has everyone so excited, let me just start out on common ground with something we already know, a traditional website. Traditionally, a website contained whatever content may have been put on it and that content may be static or may change constantly. The problem here has always been that a user had no way of knowing when or if that content had changed other than checking back periodically or being notified by someone.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=Rdw1VAoi"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=Rdw1VAoi" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=hKYs1ASA"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=hKYs1ASA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=EX7glM5a"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=EX7glM5a" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=HYWMm21k"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=HYWMm21k" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=5LgfCa7c"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=5LgfCa7c" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/please-do-feed-the-sites-what-is-rss/feed/</wfw:commentRSS>
			
<itunes:duration>11:43</itunes:duration>
		<itunes:subtitle>Before I begin this discussion explaining RSS to you as if I were this fount of knowledge that clearly recognized its value from the very ...</itunes:subtitle>
		<itunes:summary>Before I begin this discussion explaining RSS to you as if I were this fount of knowledge that clearly recognized its value from the very first moment I saw it, the fact is that my initial impression after a cursory look-over several years ago was that it was only useful to blogs and news-oriented sites. Outside of syndicating teasers of news headlines and blog posts, not a single aspect of its current usage occurred to me, and I never expected it to become an indispensable part of standard web development or to redefine the web as I knew it. So, if you can forgive me that incredible oversight, then we can get on with this...



To explain what RSS is and why it has everyone so excited, let me just start out on common ground with something we already know, a traditional website. Traditionally, a website contained whatever content may have been put on it and that content may be static or may change constantly. The problem here has always been that a user had no way of knowing when or if that content had changed other than checking back periodically or being notified by someone.


RSS solved that problem by "announcing" content updates. A site owner creates a special file called an RSS file along with a link to it, and this creates a "web feed." A web feed is a data format used for sending users content updates. Users have the option of "subscribing" to this feed either through a stand-alone desktop application called a "feed reader," through an online content aggregator like Newsburst, or, increasingly, directly through their standard web browser. Once subscribed, users are notified whenever there#39;s new content posted to the feed. That#39;s all well and good, but it doesn#39;t end there.

RSS Web Feeds


An RSS web feed is actually just an XML-based file that sits on a site like any other file and contains whatever content the site owner wants to put into it for distribution. It can be created and maintained manually or dynamically (preferably the latter.) Part 3 of this series will cover the creation of such feeds. There#39;s not really a lot to it.


I don#39;t want to lose you in the terminology or the acronyms here. An XML document--especially of the type we#39;re talking about here--is an extremely simple text document. The markup has certain similarities to HTML, but where HTML defines how to display the content, XML categorizes the content (for instance, identifying title, description, author, etc.) and does it in a machine-readable format which means that different software on different operating systems on different platforms can easily access and display that content. This is the part that allows for syndication. Numerous applications exist that look for such files, read the content, and parse it back out for use elsewhere.

RSS for Content Syndication


Content syndication is (by definition) the primary use of RSS. Originally, RSS files listed just the title of a piece, the author, the date of publication, a link back to the original content, and a quick summary to act as a kind of teaser to get you to go back to the original site to read the article--hence the mistaken view that it was only good for blog posts and news headlines. Now it includes syndication of full content--including HTML--along with "enclosures" to contain multimedia content like images, audio files, and video files and that content is being used in ever more imaginative ways. This needn#39;t scare you away from using it.

RSS Content Usage


Primarily, RSS syndicated web content simply turns up in some form of RSS reader for the usage of an individual who wants to remain informed of content updates on your site. However, this syndication of content along with the inherent extensibility of XML allows for a kind of web presence and sharing of content that was never available before. It#39;s the underlying workhorse or building block of the entire "Web 2.0" movement.
</itunes:summary>
		<itunes:keywords>All, browser, coding, content, money, promotion, search engine, SEO, station, RSS, feeds, Web 2.0, support, membership, value, programs, budget, content distributors, eGuide, extensibility, XML, Creative Commons, Tim O'Reilly, Dave Winer, Userland, syndication, Netscape, Please DO Feed the Sites Series</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>clean</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/please-do-feed-the-sites-what-is-rss/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/51618801/ptvguy111806.mp3" length="2816243" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/69/0/ptvguy111806.mp3</feedburner:origEnclosureLink></item>
		<item>
		<title>Please DO Feed the Sites: Introduction</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/43683413/</link>
		<comments>http://www.ptvguy.com/please-do-feed-the-sites-introduction/#comments</comments>
		<pubDate>Tue, 31 Oct 2006 14:23:16 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>content</dc:subject>
	<dc:subject>original content</dc:subject>
	<dc:subject>RSS</dc:subject>
	<dc:subject>feeds</dc:subject>
	<dc:subject>database</dc:subject>
	<dc:subject>Please DO Feed the Sites Series</dc:subject><dc:subject>content</dc:subject><dc:subject>database</dc:subject><dc:subject>feeds</dc:subject><dc:subject>original content</dc:subject><dc:subject>Please DO Feed the Sites Series</dc:subject><dc:subject>RSS</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/please-do-feed-the-sites-introduction/</guid>
		<description>It's been pointed out to me recently, and rightly so, that although I've been telling everyone how important it is to have and promote and use RSS feeds for their sites, I haven't stopped to explain anything about how one would actually go about doing that. Personally, I recommend the use of RSS Pixy Dust, but, if you don't happen to have that available, it gets a little more complicated.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=bL8sH6AZ"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=bL8sH6AZ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=4nV4Qas4"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=4nV4Qas4" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=vBNrtXRw"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=vBNrtXRw" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=7dc5ak8s"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=7dc5ak8s" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=1aHYpesr"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=1aHYpesr" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/please-do-feed-the-sites-introduction/feed/</wfw:commentRSS>
			
<itunes:duration>1:56</itunes:duration>
		<itunes:subtitle>It#39;s been pointed out to me recently, and rightly so, that although I#39;ve been telling everyone how important it is to have and promote and ...</itunes:subtitle>
		<itunes:summary>It#39;s been pointed out to me recently, and rightly so, that although I#39;ve been telling everyone how important it is to have and promote and use RSS feeds for their sites, I haven#39;t stopped to explain anything about how one would actually go about doing that. Personally, I recommend the use of RSS Pixy Dust, but, if you don#39;t happen to have that available, it gets a little more complicated.


I#39;ve decided that the best way to provide a useful explanation that will satisfy the most people is to break the whole thing up into a series of articles that I#39;m calling #8220;Please DO Feed the Sites.#8221; In this way, people can look for the parts they need, and, if I should miss something, I can just tag it on later as an extra part. Currently, I have it planned as follows:



Part 1: Introduction (You#39;re reading it now.)


Part 2: What Is RSS?


Part 3: Creating Outgoing Feeds


Part 4: Using Incoming Feeds




If I can get the time (and there#39;s enough interest,) I will continue the series by showing you the creation of a hand-coded and maintained RSS feed which may be a possible working solution for some sites. I will also try to move on to a walkthrough demonstration showing the creation of database-driven, dynamically maintained and updated RSS feeds. I may also add other parts later.


I#39;m aiming high with this, but, again, it depends on the kind of response I get. If this is the kind of useful content that you want to see here, then you gotta let me know.


Thank you all, code well, and good night.



  First

  Previous


Please DO Feed the Sites


Next 


Last 



</itunes:summary>
		<itunes:keywords>All, content, original content, RSS, feeds, database, Please DO Feed the Sites Series</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>clean</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/please-do-feed-the-sites-introduction/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/44180489/ptvguy103106.mp3" length="468880" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/67/0/ptvguy103106.mp3</feedburner:origEnclosureLink></item>
		<item>
		<title>Getting the Word Out On Web Standards and Accessibility</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/39236604/</link>
		<comments>http://www.ptvguy.com/getting-the-word-out-on-web-standards-and-accessibility/#comments</comments>
		<pubDate>Fri, 20 Oct 2006 09:37:25 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>accessibility</dc:subject>
	<dc:subject>browser</dc:subject>
	<dc:subject>coding</dc:subject>
	<dc:subject>compatibility</dc:subject>
	<dc:subject>content</dc:subject>
	<dc:subject>disabilities</dc:subject>
	<dc:subject>markup</dc:subject>
	<dc:subject>responsibility</dc:subject>
	<dc:subject>usability</dc:subject>
	<dc:subject>scripts</dc:subject>
	<dc:subject>Frontpage</dc:subject>
	<dc:subject>web standards</dc:subject>
	<dc:subject>DOCTYPE</dc:subject>
	<dc:subject>Accessibility Series</dc:subject><dc:subject>accessibility</dc:subject><dc:subject>Accessibility Series</dc:subject><dc:subject>browser</dc:subject><dc:subject>coding</dc:subject><dc:subject>compatibility</dc:subject><dc:subject>content</dc:subject><dc:subject>disabilities</dc:subject><dc:subject>DOCTYPE</dc:subject><dc:subject>Frontpage</dc:subject><dc:subject>markup</dc:subject><dc:subject>responsibility</dc:subject><dc:subject>scripts</dc:subject><dc:subject>usability</dc:subject><dc:subject>web standards</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/getting-the-word-out-on-web-standards-and-accessibility/</guid>
		<description>Let's face it, we live in a world where any high school kid with a semester course in "web design" (if even that much training) and a copy of Frontpage can hang out a virtual shingle calling himself (or herself) a "webmaster." Factor WordPress into that with its five-minute install and innumerable themes and you have a job title glutted with people who don't know the first thing about what they're doing. An amazingly large number of otherwise intelligent business people are entrusting their entire web presence to such as these. The general public's lack of knowledge in this area only serves to exacerbate the problem.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=ym5DsLz0"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=ym5DsLz0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=D8he43bL"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=D8he43bL" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=eDJLW4xt"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=eDJLW4xt" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=tCgERGMk"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=tCgERGMk" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=uOnHH9Q2"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=uOnHH9Q2" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/getting-the-word-out-on-web-standards-and-accessibility/feed/</wfw:commentRSS>
			
<itunes:duration>4:21</itunes:duration>
		<itunes:subtitle>Let#39;s face it, we live in a world where any high school kid with a semester course in "web design" (if even that much training) ...</itunes:subtitle>
		<itunes:summary>Let#39;s face it, we live in a world where any high school kid with a semester course in "web design" (if even that much training) and a copy of Frontpage can hang out a virtual shingle calling himself (or herself) a "webmaster." Factor WordPress into that with its five-minute install and innumerable themes and you have a job title glutted with people who don#39;t know the first thing about what they#39;re doing. An amazingly large number of otherwise intelligent business people are entrusting their entire web presence to such as these. The general public#39;s lack of knowledge in this area only serves to exacerbate the problem.


Without any foreseeable way to prevent this practice from continuing and growing exponentially, those of us who care are left with the onus of attempting to educate these fledgling webmasters about the need for good coding practices, accessibility, and web standards. I know, many of you have been doing that for years already, but this is an ongoing problem requiring constant reminders.



Now, before anyone gets in an uproar and thinks that I am perhaps mocking the document upon which this is based--The Declaration of Independence--I#39;m not. I don#39;t know of a clearer way to outline an ongoing problem and then express the need for action and the conviction to carry it out. As a pure study in writing, it#39;s one of the greatest essays ever written. I humbly borrow from the masters.


The need for web standards and accessibility cannot be understated. If you#39;re putting content out there for the world to see, use, and interact with, then there is a certain underlying responsibility to do it correctly. That requires some extra work and study. Fortunately, the web is full of people willing to share that knowledge. I#39;ve put together a list of such resources on my Anal Coding page to serve as a beginning point. The very abundance of this information made freely available to everyone everywhere is what makes the practice of bad coding so pointedly shameful.



One important thing to remember, however, is that the web is not a static technology. It is constantly growing, expanding, and evolving. New people, ideas, and technologies will come along and suddenly change everything we#39;ve taken for granted. (That may even include the aforementioned high school student.) The standards, therefore, that guide us in the creation of accessible and well-coded pages are themselves evolving and subject to change.


I encourage you to read the document itself, comment on it, and, if you agree with it, go to the declaration page and find out how to become a signatory of this important declaration and thereby further get the word out on the need for web standards and accessibility.


Thank you all, code well, and good night.




 First


 Previous


Web Accessibility


Next 


Last 



</itunes:summary>
		<itunes:keywords>All, accessibility, browser, coding, compatibility, content, disabilities, markup, responsibility, usability, scripts, Frontpage, web standards, DOCTYPE, Accessibility Series</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>clean</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/getting-the-word-out-on-web-standards-and-accessibility/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/41298371/ptvguy102006.mp3" length="1048798" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/65/0/ptvguy102006.mp3</feedburner:origEnclosureLink></item>
		<item>
		<title>Beta Testing and the New PBS Web Modules</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/35071313/</link>
		<comments>http://www.ptvguy.com/beta-testing-and-the-new-pbs-web-modules/#comments</comments>
		<pubDate>Wed, 04 Oct 2006 09:37:46 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>coding</dc:subject>
	<dc:subject>compatibility</dc:subject>
	<dc:subject>content</dc:subject>
	<dc:subject>PBS</dc:subject>
	<dc:subject>responsibility</dc:subject>
	<dc:subject>station</dc:subject>
	<dc:subject>TeacherSource</dc:subject>
	<dc:subject>time</dc:subject>
	<dc:subject>CSS</dc:subject>
	<dc:subject>staffing cuts</dc:subject>
	<dc:subject>PBS Interactive</dc:subject>
	<dc:subject>new tools</dc:subject>
	<dc:subject>beta testing</dc:subject>
	<dc:subject>content modules</dc:subject>
	<dc:subject>alpha testing</dc:subject>
	<dc:subject>feedback</dc:subject>
	<dc:subject>CLASS element</dc:subject>
	<dc:subject>ID element</dc:subject>
	<dc:subject>script triggers</dc:subject>
	<dc:subject>DOCTYPE</dc:subject>
	<dc:subject>liquid layout</dc:subject>
	<dc:subject>Pre-K Block</dc:subject>
	<dc:subject>sidebar content</dc:subject>
	<dc:subject>low-content pages</dc:subject>
	<dc:subject>filler</dc:subject>
	<dc:subject>visual impact</dc:subject>
	<dc:subject>content impact</dc:subject>
	<dc:subject>user interaction</dc:subject>
	<dc:subject>schedules modules</dc:subject><dc:subject>alpha testing</dc:subject><dc:subject>beta testing</dc:subject><dc:subject>CLASS element</dc:subject><dc:subject>coding</dc:subject><dc:subject>compatibility</dc:subject><dc:subject>content</dc:subject><dc:subject>content impact</dc:subject><dc:subject>content modules</dc:subject><dc:subject>CSS</dc:subject><dc:subject>DOCTYPE</dc:subject><dc:subject>feedback</dc:subject><dc:subject>filler</dc:subject><dc:subject>ID element</dc:subject><dc:subject>liquid layout</dc:subject><dc:subject>low content pages</dc:subject><dc:subject>new tools</dc:subject><dc:subject>PBS</dc:subject><dc:subject>PBS Interactive</dc:subject><dc:subject>Pre K Block</dc:subject><dc:subject>Pre K Block module</dc:subject><dc:subject>responsibility</dc:subject><dc:subject>schedules modules</dc:subject><dc:subject>script triggers</dc:subject><dc:subject>sidebar content</dc:subject><dc:subject>staffing cuts</dc:subject><dc:subject>station</dc:subject><dc:subject>TeacherSource</dc:subject><dc:subject>time</dc:subject><dc:subject>user interaction</dc:subject><dc:subject>visual impact</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/2006/10/04/beta-testing-and-the-new-pbs-web-modules/</guid>
		<description>Although most of the PBS member station websites routinely rely on the content they receive through PBS web modules to fill out their own sites, there is quite often a shortage of station web developers willing to help out in the beta-testing phase of their development. That's too bad since shortages of staff and time at PBS Interactive are already impacting development of new content. It's in our own best interest, if we're to remain relevant in the 21st-century, for us to be a willing part of this important aspect of content development.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=DoHREfth"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=DoHREfth" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=Tv2BJM60"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=Tv2BJM60" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=wFdBedQD"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=wFdBedQD" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=bSogLyRm"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=bSogLyRm" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=56JYW7DX"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=56JYW7DX" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/beta-testing-and-the-new-pbs-web-modules/feed/</wfw:commentRSS>
			
<itunes:duration>7:35</itunes:duration>
		<itunes:subtitle>The recent spate of new web content modules coming out of PBS (and beyond) has me thinking about the need for beta testers. For those ...</itunes:subtitle>
		<itunes:summary>The recent spate of new web content modules coming out of PBS (and beyond) has me thinking about the need for beta testers. For those of you that may never have given it a try, beta-testing is the process of testing something out before it#39;s ready for release to the general public. It can be quite interesting whether it#39;s software or a new web module. It gives you a chance to not only critique someone else#39;s work, but to sharpen your coding skills and offer suggestions for refinement. It makes you a part of the work. The biggest kick for me, however, is getting to play around with all the newest toys before anyone else even gets to see them.



There are a few important things to remember when beta-testing PBS modules for your station site. The first and most important of these is to test it on a working version of your actual station website as it would run under normal conditions (although in a nonpublic area protected from search bots and perhaps requiring a password to enter.) The idea here is to see how it functions on a real station website. The PBS Interactive in-house alpha testing should have already covered how it works under other conditions.


It must be allowed to interact with your usual station CSS in place on the page. No matter how narrow and focused the CSS for a new module may be, there may still be unforeseen interactions with already existing styles. That#39;s exactly the kind of stuff that PBS Interactive is looking for and needs to learn from your feedback, and that#39;s exactly why they have to have beta testers. I, for instance, have noticed the recurring use of common words (like "description") for CLASS or ID element names which virtually guarantees problematic interactions with already existing styles and script triggers.



The module should also be tested under the normal coding restrictions (or lack thereof) imposed by your site#39;s primary document type declaration. To make the modules as cross-platform, cross-server, and cross-browser compatible as they can possibly be, they need to be tested under differing document types. Ideally, the people at PBS Interactive should have picked their beta testers from a wide selection of stations representing as many different document types and servers as they possibly could to get the widest possible testing results and thereby eliminate the most possible errors. Therefore, the minimum testing that should be performed from our end is simply to set it up on a regular page of our site. We#39;re, of course, always welcome to test more beyond that.

The Process of Beta Testing

I don#39;t know how others do this--and I#39;d love to hear--but I generally start out by implementing a new web module in its raw state (no code or style modifications) in the widest possible section of a page. I usually pick a single-column page layout for this (no sidebars) in order to get a good 700 to 740 pixels of width to play in. A site with a non-fixed-width (or "liquid") layout will, of course, have variable outcomes for this. I do this even if the module is actually meant to be narrow sidebar content.


The idea here is twofold; first, to see if the module even works, and second, to see just how wide the module will go. After looking at the results of that--and assuming it works--I check the code and CSS to see if there#39;s anything in place that restricts the module from going even wider. Playing around with the Pre-K Block Module, for instance, shows that it can be used not only as sidebar content as it was originally intended, but also as a variable-width page filler wherever needed. That gives me a nice new tool for balancing out low-content pages.


The next test I do is to implement the module into a narrow, restricted space. The easiest way to do this is by putting it into a table and deliberately setting the width too low (like 10 pixels) and the border to zero. If your CSS has predefined table element padding </itunes:summary>
		<itunes:keywords>All, coding, compatibility, content, PBS, responsibility, station, TeacherSource, time, CSS, staffing cuts, PBS Interactive, new tools, beta testing, content modules, alpha testing, feedback, CLASS element, ID element, script triggers, DOCTYPE, liquid layout, Pre-K Block, sidebar content, low-content pages, filler, visual impact, content impact, user interaction, schedules modules</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>clean</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/beta-testing-and-the-new-pbs-web-modules/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/33149065/ptvguy100406.mp3" length="1909538" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/58/0/ptvguy100406.mp3</feedburner:origEnclosureLink></item>
		<item>
		<title>The Illusion of Accelerated Dialup</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/35071314/</link>
		<comments>http://www.ptvguy.com/the-illusion-of-accelerated-dialup/#comments</comments>
		<pubDate>Fri, 22 Sep 2006 10:53:52 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>advertising</dc:subject>
	<dc:subject>money</dc:subject>
	<dc:subject>pet peeves</dc:subject>
	<dc:subject>usability</dc:subject>
	<dc:subject>ISP</dc:subject>
	<dc:subject>accelerated dialup</dc:subject>
	<dc:subject>graphics</dc:subject>
	<dc:subject>deception</dc:subject>
	<dc:subject>illusion</dc:subject>
	<dc:subject>dialup</dc:subject>
	<dc:subject>graphic optimization</dc:subject><dc:subject>accelerated dialup</dc:subject><dc:subject>advertising</dc:subject><dc:subject>deception</dc:subject><dc:subject>dialup</dc:subject><dc:subject>graphic optimization</dc:subject><dc:subject>graphics</dc:subject><dc:subject>illusion</dc:subject><dc:subject>ISP</dc:subject><dc:subject>money</dc:subject><dc:subject>pet peeves</dc:subject><dc:subject>usability</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/2006/09/22/the-illusion-of-accelerated-dialup/</guid>
		<description>ISPs routinely sell the concept of "Accelerated Dialup" with ridiculous phrases promising "DSL-like speed from your dialup connection." The way it works is to remove some of the quality from all of the graphics they display so that the page loads faster. The problem here is that within a week or two of signing on, most users have forgotten (if they ever noticed in the first place) this aspect of their ISP's behavior, and they begin to think that what they're seeing is just the way the web looks.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=r7YyfFpV"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=r7YyfFpV" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=13z1gzFq"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=13z1gzFq" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=PDLVx7aW"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=PDLVx7aW" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=DOPvPt6F"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=DOPvPt6F" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=zS2v6K93"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=zS2v6K93" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/the-illusion-of-accelerated-dialup/feed/</wfw:commentRSS>
			
<itunes:duration>4:32</itunes:duration>
		<itunes:subtitle>BEWARE: Web developer letting off steam. Read at your own risk.



Okay, I#39;ve had it. I#39;m tired of telling people that what they#39;re seeing on their ...</itunes:subtitle>
		<itunes:summary>BEWARE: Web developer letting off steam. Read at your own risk.



Okay, I#39;ve had it. I#39;m tired of telling people that what they#39;re seeing on their screen isn#39;t really what my site looks like. I#39;m tired of explaining to site users that I did not populate my site with sucky graphics. In point of fact, I#39;m sick and tired of the entire concept of "Accelerated Dialup" that ISPs have been selling for years. It#39;s a myth, an illusion people; it doesn#39;t exist. Now, I realize, of course, that my audience here is primarily web developers and that this isn#39;t anything they don#39;t already know, but I just can#39;t stand it anymore. I#39;m sure you understand my need for a rant here.



I#39;m over at a friend#39;s house or a get-together or something. Someone walks up to me and says something like, "I just heard that you handle such-and-such website." I straighten up and get prepared to receive the unsolicited commendations I#39;m sure are forthcoming. The next thing I hear is something like, "You#39;d think they could afford some decent graphics." or, "Why does it look all crappy like that?" Then I have to spend the rest of my time there trying to save what#39;s left of my deflated ego and explain how they#39;ve been duped by their ISP.


ISPs routinely sell the concept of "Accelerated Dialup" with ridiculous phrases promising "DSL-like speed from your dialup connection." They#39;ll even explain how it works right on their homepages while knowing full well that the majority of their users don#39;t read anything past the lurid sales bullets and the stated price.


The way it works is to remove some of the quality from all of the graphics they display so that the page loads faster. Is it just me or does this strike you as the web equivalent of the potato-chip bag disclaimers that say, "Some settling may occur," as if that explains why the bag is more than half empty when you open it?



The problem here is that within a week or two of signing on, most users have forgotten (if they ever noticed in the first place) this aspect of their ISP#39;s behavior, and they begin to think that what they#39;re seeing is just the way the web looks. If you#39;re like me and you#39;ve taken the time to optimize your graphics as far as possible to achieve the fastest possible downloads for your users, then the extra filtering of "Accelerated Dialup" will result in graphics that look like they were created by a third-grader with a water-color set. The alternative is using higher-quality, slower-loading graphics to compensate.


Here#39;s how the ISP#39;s should explain it:


We know that your 56k-modem won#39;t go any faster than 56k, but, in order to get you to give us your money, we will gladly give you the illusion of faster web surfing by stripping 20% to 50% of the quality from even the most carefully crafted and optimized graphics before you view them.



To be slightly fair in my rant, "Accelerated Dialup" does have it#39;s place. There are times when a dialup user will want to surf the web faster without being that particular about graphics. However, this should be done knowingly.


Why can#39;t the ISPs, since they#39;re already processing the graphic anyway, brand it somehow to remind users that they#39;ve tampered with it and it#39;s not the original? I would offer some constructive ideas along these lines, but, in the mood I#39;m in right now, all I can picture is a toilet-seat cover and the words, "Optimized for your deception."


I really can#39;t believe that I#39;m the only person bothered by this. Anyway, I appreciate the chance to get that off my chest.


Thank you all, code well, and good night.

</itunes:summary>
		<itunes:keywords>All, advertising, money, pet peeves, usability, ISP, accelerated dialup, graphics, deception, illusion, dialup, graphic optimization</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>clean</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/the-illusion-of-accelerated-dialup/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/27046367/ptvguy092206.mp3" length="1181140" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/57/0/ptvguy092206.mp3</feedburner:origEnclosureLink></item>
		<item>
		<title>Internet Explorer 7: Is Your Site Ready?</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/35071315/</link>
		<comments>http://www.ptvguy.com/internet-explorer-7-is-your-site-ready/#comments</comments>
		<pubDate>Mon, 11 Sep 2006 14:23:06 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>browser</dc:subject>
	<dc:subject>browser version</dc:subject>
	<dc:subject>coding</dc:subject>
	<dc:subject>compatibility</dc:subject>
	<dc:subject>markup</dc:subject>
	<dc:subject>promotion</dc:subject>
	<dc:subject>scripts</dc:subject>
	<dc:subject>CSS</dc:subject>
	<dc:subject>plugins</dc:subject>
	<dc:subject>RSS</dc:subject>
	<dc:subject>feeds</dc:subject>
	<dc:subject>header</dc:subject>
	<dc:subject>membership</dc:subject>
	<dc:subject>cookies</dc:subject>
	<dc:subject>bookmark</dc:subject>
	<dc:subject>web standards</dc:subject>
	<dc:subject>IE7</dc:subject>
	<dc:subject>extensibility</dc:subject>
	<dc:subject>Firefox</dc:subject>
	<dc:subject>Opera</dc:subject>
	<dc:subject>Microsoft</dc:subject>
	<dc:subject>security</dc:subject>
	<dc:subject>ActiveX</dc:subject>
	<dc:subject>Windows XP</dc:subject>
	<dc:subject>tabbed browsing</dc:subject>
	<dc:subject>Atom</dc:subject>
	<dc:subject>Internet Explorer</dc:subject>
	<dc:subject>categories</dc:subject>
	<dc:subject>homepage</dc:subject>
	<dc:subject>BrowserShots.org</dc:subject>
	<dc:subject>Internet Explorer Developer Toolbar</dc:subject>
	<dc:subject>Chris Pederick</dc:subject>
	<dc:subject>Firefox Web Developer Toolbar</dc:subject>
	<dc:subject>Fiddler</dc:subject>
	<dc:subject>HTTP Debugger</dc:subject>
	<dc:subject>phishing</dc:subject>
	<dc:subject>popups</dc:subject>
	<dc:subject>privacy policy</dc:subject>
	<dc:subject>SSL</dc:subject>
	<dc:subject>WaSP</dc:subject>
	<dc:subject>CSS Hacks</dc:subject>
	<dc:subject>PositionIsEverything.net</dc:subject>
	<dc:subject>Genuine Microsoft Windows</dc:subject>
	<dc:subject>box-model problem</dc:subject>
	<dc:subject>Star-HTML Hack</dc:subject>
	<dc:subject>ALT attribute</dc:subject>
	<dc:subject>PNG</dc:subject>
	<dc:subject>DYNSRC</dc:subject>
	<dc:subject>IMG tag</dc:subject>
	<dc:subject>IE6</dc:subject>
	<dc:subject>John Mueller</dc:subject>
	<dc:subject>OLE</dc:subject>
	<dc:subject>user agent</dc:subject>
	<dc:subject>range checking</dc:subject>
	<dc:subject>JavaScript</dc:subject>
	<dc:subject>P3P</dc:subject><dc:subject>ActiveX</dc:subject><dc:subject>ALT attribute</dc:subject><dc:subject>Atom</dc:subject><dc:subject>bookmark</dc:subject><dc:subject>box model problem</dc:subject><dc:subject>browser</dc:subject><dc:subject>browser version</dc:subject><dc:subject>BrowserShots.org</dc:subject><dc:subject>categories</dc:subject><dc:subject>Chris Pederick</dc:subject><dc:subject>coding</dc:subject><dc:subject>compatibility</dc:subject><dc:subject>cookies</dc:subject><dc:subject>CSS</dc:subject><dc:subject>CSS Hacks</dc:subject><dc:subject>DYNSRC</dc:subject><dc:subject>extensibility</dc:subject><dc:subject>feeds</dc:subject><dc:subject>Fiddler</dc:subject><dc:subject>Firefox</dc:subject><dc:subject>Firefox Web Developer Toolbar</dc:subject><dc:subject>Genuine Microsoft Windows</dc:subject><dc:subject>header</dc:subject><dc:subject>homepage</dc:subject><dc:subject>HTTP Debugger</dc:subject><dc:subject>IE6</dc:subject><dc:subject>IE7</dc:subject><dc:subject>IMG tag</dc:subject><dc:subject>Internet Explorer</dc:subject><dc:subject>Internet Explorer Developer Toolbar</dc:subject><dc:subject>JavaScript</dc:subject><dc:subject>John Mueller</dc:subject><dc:subject>markup</dc:subject><dc:subject>membership</dc:subject><dc:subject>Microsoft</dc:subject><dc:subject>OLE</dc:subject><dc:subject>Opera</dc:subject><dc:subject>P3P</dc:subject><dc:subject>phishing</dc:subject><dc:subject>plugins</dc:subject><dc:subject>PNG</dc:subject><dc:subject>popups</dc:subject><dc:subject>PositionIsEverything.net</dc:subject><dc:subject>privacy policy</dc:subject><dc:subject>promotion</dc:subject><dc:subject>range checking</dc:subject><dc:subject>RSS</dc:subject><dc:subject>scripts</dc:subject><dc:subject>security</dc:subject><dc:subject>SSL</dc:subject><dc:subject>Star HTML Hack</dc:subject><dc:subject>tabbed browsing</dc:subject><dc:subject>user agent</dc:subject><dc:subject>WaSP</dc:subject><dc:subject>web standards</dc:subject><dc:subject>Windows XP</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/2006/09/11/internet-explorer-7-is-your-site-ready/</guid>
		<description>If you haven’t already heard about it–and I’m sure that most of you have–Microsoft is planning to release the first major upgrade to Internet Explorer since IE6 in 2001. With many new features, security upgrades, and changes to the core software itself, it’s a totally new browser that will suddenly be the primary browser of a good %70 or more of your audience. Is your site ready for that? If you don’t know for sure, now’s the time to find out.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=ZCP7DVS8"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=ZCP7DVS8" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=r7poIi4A"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=r7poIi4A" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=eDZmEsoS"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=eDZmEsoS" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=1QRKrFim"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=1QRKrFim" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=a5Xa6UIc"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=a5Xa6UIc" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/internet-explorer-7-is-your-site-ready/feed/</wfw:commentRSS>
			
<itunes:duration>20:07</itunes:duration>
		<itunes:subtitle>Potentially more exciting than the arrival of a new phonebook is the planned automatic update of Microsoft#39;s web browser, Internet Explorer. If you haven#39;t already ...</itunes:subtitle>
		<itunes:summary>Potentially more exciting than the arrival of a new phonebook is the planned automatic update of Microsoft#39;s web browser, Internet Explorer. If you haven#39;t already heard about it--and I#39;m sure that most of you have--Microsoft is planning to release the first major upgrade to Internet Explorer since IE6 in 2001. With many new features, security upgrades, and changes to the core software itself, it#39;s a totally new browser that will suddenly be the primary browser of a good 70% or more of your audience. Is your site ready for that? If you don#39;t know for sure, now#39;s the time to find out.



Those of us that routinely use other browsers or check our sites out in multiple browsers will find a lot of very familiar things integrated into IE7. I have mixed feelings about this. On the one hand, I#39;m happy for the changes and improvements they#39;ve made, but on the other, I find it annoying that a majority of non-technically-oriented web users will think of these as Microsoft innovations rather than Microsoft trying to catch up with everyone else#39;s innovations. Still, there is a lot to be happy about in this upgrade. Some of it--like improved web standards and CSS support--might require changes for some sites (That#39;s a good thing, really.) and some of it--like RSS integration--are an open opportunity to provide new services and gain a larger audience.

Tabbed Browsing

That#39;s right, tabbed browsing has finally made its way to Internet Explorer (boldly going where everyone else has been for quite some time.) If you#39;re like me and you regularly have to have a number of applications running simultaneously and then additionally have to open several different browsers to compare page layouts, then you#39;ll truly appreciate this addition. I can finally have ONE window of Internet Explorer open with a number of web pages displayed in different tabs (as I always could in other browsers.)


My only regret here is that there#39;s not yet a good, all-purpose, cross-browser compatible script to automatically open external links in new tabs rather than new windows. This would make a nice addition to Paul Boag#39;s External Links script that I (like many others) use so extensively. However, I#39;m sure that one will come along eventually.

RSS Integration


This is truly an awesome feature. I know that it#39;s already been a standard part of other browsers, but, because 70% to 90% of your users are surfing the web with nothing but Internet Explorer, the sudden ability to read and subscribe to RSS feeds right in their browser will be a totally new experience. If your site already has an RSS feed, then now#39;s the time to start planning how you might promote it to a more main-stream audience as well as how you might make it a more prominent part of your pages. If your site doesn#39;t, then now#39;s the time to start working on one.


The feed button for IE7 remains grayed out and inactive while viewing pages without a recognizable feed (RSS1, RSS2, Atom, etc.) and then springs to vivid, orange life when viewing a page that has one. I don#39;t know about you, but I#39;d like it to be one of MY sites that a user first notices this strange new button on. You know it has to be tried at least once just to see what it does, and what it does is tell your users that there#39;s even more content available from your site then they may have ever been aware of otherwise.



The drop-down list of available feeds and feed types next to the button is a potential source of confusion for non-technical users, but most will simply click the main button and get the topmost, default feed. Upon clicking it, however, they get not only a new feed page, but some helpful information about feeds and how to use them. My favorite part, though, is the bolded statement in the yellow box that says, "You are viewing a feed that contains frequently updated content." That#39;s practically an unsolic</itunes:summary>
		<itunes:keywords>All, browser, browser version, coding, compatibility, markup, promotion, scripts, CSS, plugins, RSS, feeds, header, membership, cookies, bookmark, web standards, IE7, extensibility, Firefox, Opera, Microsoft, security, ActiveX, Windows XP, tabbed browsing, Atom, Internet Explorer, categories, homepage, BrowserShots.org, Internet Explorer Developer Toolbar, Chris Pederick, Firefox Web Developer Toolbar, Fiddler, HTTP Debugger, phishing, popups, privacy policy, SSL, WaSP, CSS Hacks, PositionIsEverything.net, Genuine Microsoft Windows, box-model problem, Star-HTML Hack, ALT attribute, PNG, DYNSRC, IMG tag, IE6, John Mueller, OLE, user agent, range checking, JavaScript, P3P</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>clean</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/internet-explorer-7-is-your-site-ready/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/21507712/ptvguy091106.mp3" length="4829312" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/53/0/ptvguy091106.mp3</feedburner:origEnclosureLink></item>
		<item>
		<title>Frontline's Frontline Video</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/35071316/</link>
		<comments>http://www.ptvguy.com/frontlines-frontline-video/#comments</comments>
		<pubDate>Sun, 13 Aug 2006 09:38:22 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>accessibility</dc:subject>
	<dc:subject>content</dc:subject>
	<dc:subject>education</dc:subject>
	<dc:subject>original content</dc:subject>
	<dc:subject>PBS</dc:subject>
	<dc:subject>promotion</dc:subject>
	<dc:subject>public television</dc:subject>
	<dc:subject>WGBH</dc:subject>
	<dc:subject>Frontline</dc:subject>
	<dc:subject>public broadcasting</dc:subject>
	<dc:subject>keyboard navigation</dc:subject>
	<dc:subject>localization</dc:subject>
	<dc:subject>membership</dc:subject>
	<dc:subject>value</dc:subject>
	<dc:subject>programs</dc:subject>
	<dc:subject>programming</dc:subject>
	<dc:subject>nationally distributed programming</dc:subject>
	<dc:subject>local</dc:subject>
	<dc:subject>national</dc:subject>
	<dc:subject>content distributors</dc:subject>
	<dc:subject>PBS Interactive</dc:subject>
	<dc:subject>Access</dc:subject>
	<dc:subject>Frontline Video</dc:subject>
	<dc:subject>Frontline Headlines</dc:subject>
	<dc:subject>David Fanning</dc:subject>
	<dc:subject>Sam Bailey</dc:subject>
	<dc:subject>Waco Siege</dc:subject>
	<dc:subject>program content</dc:subject>
	<dc:subject>streaming</dc:subject>
	<dc:subject>video</dc:subject>
	<dc:subject>video streaming</dc:subject>
	<dc:subject>Frontline Player</dc:subject>
	<dc:subject>Frontline/World</dc:subject>
	<dc:subject>public media</dc:subject>
	<dc:subject>public library</dc:subject>
	<dc:subject>intellectual commons</dc:subject>
	<dc:subject>video player</dc:subject>
	<dc:subject>marketing</dc:subject>
	<dc:subject>objectionable content</dc:subject>
	<dc:subject>FCC</dc:subject>
	<dc:subject>webcasting</dc:subject>
	<dc:subject>captioning</dc:subject>
	<dc:subject>NCAM</dc:subject>
	<dc:subject>revolution</dc:subject>
	<dc:subject>renaissance</dc:subject>
	<dc:subject>the great promise</dc:subject>
	<dc:subject>new tools</dc:subject><dc:subject>Access</dc:subject><dc:subject>accessibility</dc:subject><dc:subject>captioning</dc:subject><dc:subject>content</dc:subject><dc:subject>content distributors</dc:subject><dc:subject>David Fanning</dc:subject><dc:subject>education</dc:subject><dc:subject>FCC</dc:subject><dc:subject>Frontline</dc:subject><dc:subject>Frontline Headlines</dc:subject><dc:subject>Frontline Player</dc:subject><dc:subject>Frontline Video</dc:subject><dc:subject>Frontline/World</dc:subject><dc:subject>intellectual commons</dc:subject><dc:subject>keyboard navigation</dc:subject><dc:subject>local</dc:subject><dc:subject>localization</dc:subject><dc:subject>marketing</dc:subject><dc:subject>membership</dc:subject><dc:subject>national</dc:subject><dc:subject>nationally distributed programming</dc:subject><dc:subject>NCAM</dc:subject><dc:subject>new tools</dc:subject><dc:subject>objectionable content</dc:subject><dc:subject>original content</dc:subject><dc:subject>PBS</dc:subject><dc:subject>PBS Interactive</dc:subject><dc:subject>program content</dc:subject><dc:subject>programming</dc:subject><dc:subject>programs</dc:subject><dc:subject>promotion</dc:subject><dc:subject>public broadcasting</dc:subject><dc:subject>public library</dc:subject><dc:subject>public media</dc:subject><dc:subject>public television</dc:subject><dc:subject>renaissance</dc:subject><dc:subject>revolution</dc:subject><dc:subject>Sam Bailey</dc:subject><dc:subject>streaming</dc:subject><dc:subject>the great promise</dc:subject><dc:subject>value</dc:subject><dc:subject>video</dc:subject><dc:subject>video player</dc:subject><dc:subject>video streaming</dc:subject><dc:subject>Waco Siege</dc:subject><dc:subject>webcasting</dc:subject><dc:subject>WGBH</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/2006/08/09/frontlines-frontline-video/</guid>
		<description>Sam Bailey, Frontline’s Director of New Media and Technology, has spent the last two years developing a new, enhanced web video player designed specifically to play high-quality, large-frame video of full Frontline programs directly off of local station web sites. The new player will be able to play at a bitrate of 350k–a considerable increase over the current 220k–in a fairly large and customizable playing window, and PBS is providing the bandwidth for it. The only downside is that it’s available for broadband only.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=ZhXWe8bJ"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=ZhXWe8bJ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=T1HQfCaZ"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=T1HQfCaZ" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=tMD6YQea"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=tMD6YQea" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=O1bM8RXN"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=O1bM8RXN" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=62v7j919"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=62v7j919" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/frontlines-frontline-video/feed/</wfw:commentRSS>
			
<itunes:duration>13:38</itunes:duration>
		<itunes:subtitle>It was a turning point in Internet history, and it happened in October of 1995. Frontline had been investigating the 1993 Waco siege for an ...</itunes:subtitle>
		<itunes:summary>It was a turning point in Internet history, and it happened in October of 1995. Frontline had been investigating the 1993 Waco siege for an upcoming report when David Fanning, the Executive Producer of Frontline, made the decision to put a good deal of the material derived from their research and reporting (photos, FBI surveillance audiotapes, reporting notes, interviews) on the web for everyone to see. It was their very first website and done with a staff of just two people. That single act not only created the concept of open (or transparent) journalism but forever changed the way we look at and what we expect out of the World Wide Web.



You may be wondering what this has to do with your local station website. After all, it#39;s been a while since we#39;ve had Frontline content available to us as local web content--not counting RSS feeds. The original Frontline Video module that some of us once utilized on our local sites was a rather short-lived experiment, and even the more long-term Headlines module (much lamented in its passing) eventually faded into history. So what is there now that could inspire a public television station web developer like myself to bring up such a sore subject? Well, you#39;re not going to believe this, but Frontline Video is back, and it#39;s all grown up now.


Sam Bailey, Frontline#39;s Director of New Media and Technology, has spent the last two years developing a new, enhanced web video player designed specifically to play high-quality, large-frame video of full Frontline programs directly off of local station web sites. The new player will be able to play at a bitrate of 350k--a considerable increase over the current 220k--in a fairly large and customizable playing window, and PBS is providing the bandwidth for it. The only downside is that it#39;s available for broadband only.


We#39;re going for incremental improvements here. I think eventually the bitrates will go higher, but, right now, 350k is a good number for us (and for PBS who has to pay the bill.) Frankly the quality of many broadband connections and general latency is such that higher bitrates can sometimes not work so smoothly.
-- Sam Bailey, Director of New Media and Technology, Frontline


One exciting aspect of this delivery system is the distinct possibility that West Coast station sites could actually receive the latest program through their website prior to the on-air broadcast. Frontline#39;s current plan is to make the shows available online on the same day they#39;re broadcast which means that West Coast station sites will have direct access to the shows three hours earlier in the day (in terms of local time) than East Coast stations. This aspect of the player#39;s behavior is still under consideration but probably won#39;t change.

But Wait, There#39;s More...

I know it sounds like a bad commercial, but this player has a lot of other innovations that will make it indispensable to your station website. It appears initially as a small piece of page content (probably sidebar,) but what it does next is controllable by you. There are two different options that you can set up to control what happens when a user clicks the link; it can open a player window or a menu page.

The Player Window

The Player Window is the heart and soul of this new module. It#39;s designed to open as a small, popup window over your page and begin playing a Frontline program of your choice. The real innovation, however, is that there#39;s a space around the window that can be customized for station logo and messaging that you can control. If only CSS control could be built into the final version (which is not currently planned,) then this player could be reskinned locally as each station sees fit.  Still, it#39;s definitely going to be an important part of the local station site and yet one more really awesome service to offer to the community.

The Menu Page

The Menu Page option opens as a new page.  It c</itunes:summary>
		<itunes:keywords>All, accessibility, content, education, original content, PBS, promotion, public television, WGBH, Frontline, public broadcasting, keyboard navigation, localization, membership, value, programs, programming, nationally distributed programming, local, national, content distributors, PBS Interactive, Access, Frontline Video, Frontline Headlines, David Fanning, Sam Bailey, Waco Siege, program content, streaming, video, video streaming, Frontline Player, Frontline/World, public media, public library, intellectual commons, video player, marketing, objectionable content, FCC, webcasting, captioning, NCAM, revolution, renaissance, the great promise, new tools</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>no</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/frontlines-frontline-video/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/12030041/ptvguy081306.mp3" length="3277252" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/47/0/ptvguy081306.mp3</feedburner:origEnclosureLink></item>
		<item>
		<title>KIXE Redesign: Frontpage and the Anal Coder</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/35071317/</link>
		<comments>http://www.ptvguy.com/kixe-redesign-frontpage-and-the-anal-coder/#comments</comments>
		<pubDate>Mon, 31 Jul 2006 06:03:37 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>coding</dc:subject>
	<dc:subject>compatibility</dc:subject>
	<dc:subject>content</dc:subject>
	<dc:subject>education</dc:subject>
	<dc:subject>markup</dc:subject>
	<dc:subject>original content</dc:subject>
	<dc:subject>real world</dc:subject>
	<dc:subject>station</dc:subject>
	<dc:subject>teachers</dc:subject>
	<dc:subject>PBS station prototype website</dc:subject>
	<dc:subject>CSS</dc:subject>
	<dc:subject>database</dc:subject>
	<dc:subject>server</dc:subject>
	<dc:subject>KIXE</dc:subject>
	<dc:subject>header</dc:subject>
	<dc:subject>footer</dc:subject>
	<dc:subject>SSI</dc:subject>
	<dc:subject>SHTML</dc:subject>
	<dc:subject>ASP</dc:subject>
	<dc:subject>redesign</dc:subject>
	<dc:subject>Frontpage</dc:subject>
	<dc:subject>Microsoft Bashing</dc:subject>
	<dc:subject>Redding</dc:subject>
	<dc:subject>California</dc:subject>
	<dc:subject>isolated communities</dc:subject>
	<dc:subject>web standards</dc:subject>
	<dc:subject>content rescue</dc:subject>
	<dc:subject>Windows 2003 Server</dc:subject>
	<dc:subject>auction</dc:subject>
	<dc:subject>eGuide</dc:subject>
	<dc:subject>maintenance</dc:subject>
	<dc:subject>column layout</dc:subject>
	<dc:subject>Piefecta</dc:subject>
	<dc:subject>tableless layout</dc:subject>
	<dc:subject>faux columns</dc:subject>
	<dc:subject>htaccess</dc:subject>
	<dc:subject>Apache Server</dc:subject>
	<dc:subject>Access</dc:subject>
	<dc:subject>KIXE redesign</dc:subject><dc:subject>Access</dc:subject><dc:subject>Apache Server</dc:subject><dc:subject>ASP</dc:subject><dc:subject>auction</dc:subject><dc:subject>California</dc:subject><dc:subject>coding</dc:subject><dc:subject>column layout</dc:subject><dc:subject>compatibility</dc:subject><dc:subject>content</dc:subject><dc:subject>content rescue</dc:subject><dc:subject>CSS</dc:subject><dc:subject>database</dc:subject><dc:subject>education</dc:subject><dc:subject>eGuide</dc:subject><dc:subject>faux columns</dc:subject><dc:subject>footer</dc:subject><dc:subject>Frontpage</dc:subject><dc:subject>header</dc:subject><dc:subject>htaccess</dc:subject><dc:subject>isolated communities</dc:subject><dc:subject>KIXE</dc:subject><dc:subject>KIXE redesign</dc:subject><dc:subject>maintenance</dc:subject><dc:subject>markup</dc:subject><dc:subject>Microsoft Bashing</dc:subject><dc:subject>original content</dc:subject><dc:subject>PBS station prototype website</dc:subject><dc:subject>Piefecta</dc:subject><dc:subject>real world</dc:subject><dc:subject>Redding</dc:subject><dc:subject>redesign</dc:subject><dc:subject>server</dc:subject><dc:subject>SHTML</dc:subject><dc:subject>SSI</dc:subject><dc:subject>station</dc:subject><dc:subject>tableless layout</dc:subject><dc:subject>teachers</dc:subject><dc:subject>web standards</dc:subject><dc:subject>Windows 2003 Server</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/2006/07/30/kixe-redesign-frontpage-and-the-anal-coder/</guid>
		<description>I bring you the KIXE redesign. I have maintained the KIXE website (such as it is) for several years now with a complete redesign always pending but never approved. It's horrible design and coding has always been a thorn in my side and, with the launch of their new logo and look, I've finally gotten the go-ahead.&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=56RVA7CH"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=56RVA7CH" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=GvQjkFep"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=GvQjkFep" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=cQPmZQJF"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=cQPmZQJF" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=5UrjrmvT"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=5UrjrmvT" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=SkpxvHwX"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=SkpxvHwX" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/kixe-redesign-frontpage-and-the-anal-coder/feed/</wfw:commentRSS>
			
<itunes:duration>5:24</itunes:duration>
		<itunes:subtitle>I apologize to everyone for having been too busy to post anything here for the last month, but many of my projects will be coming ...</itunes:subtitle>
		<itunes:summary>I apologize to everyone for having been too busy to post anything here for the last month, but many of my projects will be coming your way as new station web content very soon. However, to get back into the swing of things, I bring you the KIXE redesign. I have maintained the KIXE website (such as it is) for several years now with a complete redesign always pending but never approved. It#39;s horrible design and coding has always been a thorn in my side and, with the launch of their new logo and look, I#39;ve finally gotten the go-ahead.



There are a number of challenges to be met in getting KIXE#39;s site up to standards. There#39;s the usual content rescue wherein I have to find all of the actually useful content and extract it from the coding nightmare that it#39;s currently buried in. There#39;s the fact that it#39;s hosted on a Windows 2003 server with a number of other sites, and I don#39;t have the usual server control that I#39;ve been getting so spoiled on. There#39;s the addition of an online auction and an eGuide that will require initial setup and long-term maintenance--probably with Microsoft Access interaction. However, the greatest challenge here--and I#39;m gritting my teeth and going forward anyway--is the absolute reliance on Microsoft Frontpage.


I#39;m not a Microsoft basher, so if you were hoping for a tirade on that subject, you#39;ll have to look elsewhere. The web is full of them; they#39;re not hard to find.


That kind of stuff always reminds me of those guys that see you putting a tiny nail in the wall with a little utility hammer and start in making derisive comments about what they call "housewife hammers." You have to cut off people like that before they start telling you how many ounces their "real hammer" is and let them know that the point is the job and not the tool. Best answer for that kind of stuff: "I could do it with a rock; I#39;m sorry that it requires so much more for you to accomplish the same thing."



So, how does one go about creating an accessible, standards-based, cross-browser compatible, dynamic website with a tool like Frontpage? Frankly, you cheat. You do as much as possible directly in the code, and you start with a standards-based design and rework it to fit your job. KIXE wants a site based on the PBS Be More Station Website Prototype which varies between differing static pages having one- to three-column rigid layouts and a header and footer. Therefore, I#39;ve decided to adapt the Piefecta layout to the prototype to achieve a standards-based, rigid-column design. [Thank you John and Holly.]


Piefecta is a beautiful piece of coding and highly adaptable. I#39;ve reworked it to cover one-, two-, and three-column layout from a single CSS file and even added in support for the three faux columns found in the center column of the homepage. If you#39;d like to see where this is at right now, then visit the KIXE test page. There are still a lot of internal styles to work in, but the primary layout is there and waiting to be filled.



If you look closely, then you#39;ll see that I#39;ve actually used a few proprietary Frontpage extensions for server side includes. This makes up for the fact that I don#39;t have the .htaccess control of an Apache server here to hide my server processing in a plain HTML file. I don#39;t want to create a site laid out with all the files having SHTML or ASP extensions as those tend to confuse people, so I will be making use of what the server offers me. I will be using both standard and timed Frontpage includes to run basic server preprocessing from a plain HTML file.


Keep checking back here as I update you not only on the progress of this redesign, but also on some great new tools that you#39;ll be wanting to add to your station website soon.


Thank you all, code well, and good night.

</itunes:summary>
		<itunes:keywords>All, coding, compatibility, content, education, markup, original content, real world, station, teachers, PBS station prototype website, CSS, database, server, KIXE, header, footer, SSI, SHTML, ASP, redesign, Frontpage, Microsoft Bashing, Redding, California, isolated communities, web standards, content rescue, Windows 2003 Server, auction, eGuide, maintenance, column layout, Piefecta, tableless layout, faux columns, htaccess, Apache Server, Access, KIXE redesign</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>clean</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/kixe-redesign-frontpage-and-the-anal-coder/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/7649950/ptvGuy073006.mp3" length="1298482" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/43/0/ptvGuy073006.mp3</feedburner:origEnclosureLink></item>
		<item>
		<title>Localizing Beyond PBS: An Open Proposal</title>
		<link>http://feeds.feedburner.com/~r/ptvguy/~3/35071318/</link>
		<comments>http://www.ptvguy.com/localizing-beyond-pbs-an-open-proposal/#comments</comments>
		<pubDate>Wed, 28 Jun 2006 07:07:57 +0000</pubDate>
		<dc:creator>ptvGuy</dc:creator>
		
	<dc:subject>All</dc:subject>
	<dc:subject>coding</dc:subject>
	<dc:subject>content</dc:subject>
	<dc:subject>markup</dc:subject>
	<dc:subject>original content</dc:subject>
	<dc:subject>PBS</dc:subject>
	<dc:subject>promotion</dc:subject>
	<dc:subject>public television</dc:subject>
	<dc:subject>SOPTV</dc:subject>
	<dc:subject>station</dc:subject>
	<dc:subject>WGBH</dc:subject>
	<dc:subject>scripts</dc:subject>
	<dc:subject>site navigation</dc:subject>
	<dc:subject>interactivity</dc:subject>
	<dc:subject>Frontline</dc:subject>
	<dc:subject>public broadcasting</dc:subject>
	<dc:subject>public radio</dc:subject>
	<dc:subject>server</dc:subject>
	<dc:subject>localization</dc:subject>
	<dc:subject>KIXE</dc:subject>
	<dc:subject>Nova</dc:subject>
	<dc:subject>station-linking code</dc:subject>
	<dc:subject>Web 2.0</dc:subject>
	<dc:subject>PBS navbar</dc:subject>
	<dc:subject>header</dc:subject>
	<dc:subject>footer</dc:subject>
	<dc:subject>internal navigation</dc:subject>
	<dc:subject>navbar</dc:subject>
	<dc:subject>support</dc:subject>
	<dc:subject>membership</dc:subject>
	<dc:subject>value</dc:subject>
	<dc:subject>programs</dc:subject>
	<dc:subject>programming</dc:subject>
	<dc:subject>nationally distributed programming</dc:subject>
	<dc:subject>local</dc:subject>
	<dc:subject>national</dc:subject>
	<dc:subject>Cindy Johanson</dc:subject>
	<dc:subject>budget</dc:subject>
	<dc:subject>staffing cuts</dc:subject>
	<dc:subject>Sierra Center Stage</dc:subject>
	<dc:subject>Online Xtras</dc:subject>
	<dc:subject>PBS station remote control</dc:subject>
	<dc:subject>cookies</dc:subject>
	<dc:subject>URL</dc:subject>
	<dc:subject>parameters</dc:subject>
	<dc:subject>bookmark</dc:subject>
	<dc:subject>revenues</dc:subject>
	<dc:subject>income</dc:subject>
	<dc:subject>producers</dc:subject>
	<dc:subject>content distributors</dc:subject>
	<dc:subject>SSI</dc:subject>
	<dc:subject>SHTML</dc:subject>
	<dc:subject>PHP</dc:subject>
	<dc:subject>ASP</dc:subject>
	<dc:subject>downloads</dc:subject>
	<dc:subject>portal pages</dc:subject>
	<dc:subject>Global Connections</dc:subject>
	<dc:subject>African American World</dc:subject>
	<dc:subject>LiteracyLink</dc:subject>
	<dc:subject>PBS Campus</dc:subject>
	<dc:subject>PBS YOU</dc:subject>
	<dc:subject>KET</dc:subject>
	<dc:subject>PBS Interactive</dc:subject>
	<dc:subject>interconnectedness</dc:subject>
	<dc:subject>CURRENT</dc:subject>
	<dc:subject>self-sufficiency</dc:subject>
	<dc:subject>Redding</dc:subject>
	<dc:subject>California</dc:subject>
	<dc:subject>Oregon</dc:subject>
	<dc:subject>Medford</dc:subject><dc:subject>African American World</dc:subject><dc:subject>ASP</dc:subject><dc:subject>bookmark</dc:subject><dc:subject>budget</dc:subject><dc:subject>California</dc:subject><dc:subject>Cindy Johanson</dc:subject><dc:subject>coding</dc:subject><dc:subject>content</dc:subject><dc:subject>content distributors</dc:subject><dc:subject>cookies</dc:subject><dc:subject>CURRENT</dc:subject><dc:subject>downloads</dc:subject><dc:subject>footer</dc:subject><dc:subject>Frontline</dc:subject><dc:subject>Global Connections</dc:subject><dc:subject>header</dc:subject><dc:subject>income</dc:subject><dc:subject>interactivity</dc:subject><dc:subject>interconnectedness</dc:subject><dc:subject>internal navigation</dc:subject><dc:subject>KET</dc:subject><dc:subject>KIXE</dc:subject><dc:subject>LiteracyLink</dc:subject><dc:subject>local</dc:subject><dc:subject>localization</dc:subject><dc:subject>markup</dc:subject><dc:subject>Medford</dc:subject><dc:subject>membership</dc:subject><dc:subject>national</dc:subject><dc:subject>nationally distributed programming</dc:subject><dc:subject>navbar</dc:subject><dc:subject>Nova</dc:subject><dc:subject>Online Xtras</dc:subject><dc:subject>Oregon</dc:subject><dc:subject>original content</dc:subject><dc:subject>parameters</dc:subject><dc:subject>PBS</dc:subject><dc:subject>PBS Campus</dc:subject><dc:subject>PBS Interactive</dc:subject><dc:subject>PBS navbar</dc:subject><dc:subject>PBS station remote control</dc:subject><dc:subject>PBS YOU</dc:subject><dc:subject>PHP</dc:subject><dc:subject>portal pages</dc:subject><dc:subject>producers</dc:subject><dc:subject>programming</dc:subject><dc:subject>programs</dc:subject><dc:subject>promotion</dc:subject><dc:subject>public broadcasting</dc:subject><dc:subject>public radio</dc:subject><dc:subject>public television</dc:subject><dc:subject>Redding</dc:subject><dc:subject>revenues</dc:subject><dc:subject>scripts</dc:subject><dc:subject>self sufficiency</dc:subject><dc:subject>server</dc:subject><dc:subject>SHTML</dc:subject><dc:subject>Sierra Center Stage</dc:subject><dc:subject>site navigation</dc:subject><dc:subject>SOPTV</dc:subject><dc:subject>SSI</dc:subject><dc:subject>staffing cuts</dc:subject><dc:subject>station</dc:subject><dc:subject>station linking code</dc:subject><dc:subject>support</dc:subject><dc:subject>URL</dc:subject><dc:subject>value</dc:subject><dc:subject>Web 2.0</dc:subject><dc:subject>WGBH</dc:subject>
		<guid isPermaLink="false">http://www.ptvguy.com/2006/06/28/localizing-beyond-pbs-an-open-proposal/</guid>
		<description>&lt;p&gt;&lt;!-- google_ad_section_start --&gt;&lt;/p&gt;
&lt;h3&gt;Introduction&lt;/h3&gt;

&lt;p&gt;
&lt;span class="dropcap"&gt;I&lt;/span&gt;n one of its most brilliant decisions ever, &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; decided to downplay itself as a national entity in favor of extending the perceived reach of every one of its local member stations. (&lt;em&gt;&lt;a href="http://www.current.org/in/in919p.html" class="externalLink" title="CURRENT: Web: best medium for local/national convergence?"&gt;Web: best medium for local/national convergence?&lt;/a&gt;&lt;/em&gt;) In other words, &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; in Medford, Oregon IS &lt;a href="http://www.soptv.org/" class="externalLink" title="Southern Oregon Public Television"&gt;SOPTV&lt;/a&gt;, &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; in Redding, California IS &lt;a href="http://www.kixe.org/" class="externalLink" title="KIXE"&gt;KIXE&lt;/a&gt;, and &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; in your local town or city IS your local station. This doesn&amp;#39;t just happen on-air, it extends online as well.
&lt;/p&gt;

&lt;p&gt;
When a local station website links to a &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; program site like &lt;a href="http://www.pbs.org/wgbh/pages/frontline/" class="externalLink" title="Frontline"&gt;Frontline&lt;/a&gt; or &lt;a href="http://www.pbs.org/wgbh/nova/" class="externalLink" title="Nova"&gt;Nova&lt;/a&gt;, it uses station-linking code to pass its station identification to that site which in turn dynamically generates a localized version of that page complete with a backlinked station logo and localized broadcast information. The end result for the user is that their local station website and the &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service website"&gt;PBS.org&lt;/a&gt; national site (the most popular dot org site on the planet) work together as a single, cohesive unit creating the perception that they are one whole site. In fact, some studies have shown that many users are totally unaware of ever having left the local station site.
&lt;/p&gt;
&lt;p&gt;
&lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; localization has added to the perceived value of the local station site as a community resource. It extends the perceived reach of the local station into vast resources and archives of information that no one station could ever achieve. Basically, &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; was a &lt;dfn title="Refers to a second generation of services available on the World Wide Web that lets people collaborate and share information online."&gt;Web 2.0&lt;/dfn&gt; resource long before anyone conceived of such a term to describe that kind of online interaction and interconnectedness. Now, while the rest of the web tries to catch up to even that level, the time has come for us to extend this even further.
&lt;/p&gt;

&lt;p&gt;
Individual stations across the country have for years been creating small (and some very large) pieces of original web content. Some of these are tied to local productions or events and hold little interest outside the local community, but many are very interesting slices of local history, art, and culture and have value to the system as a whole. This kind of web content along with content tied to nationally distributed programs would be ideal for localization.
&lt;/p&gt;
&lt;h3&gt;The Proposal&lt;/h3&gt;

&lt;p&gt;
I propose the creation of localized versions of such pages set up to take advantage of and function similarly to the already existing localization system in place on &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service website"&gt;PBS.org&lt;/a&gt;. The beauty of this system is that it&amp;#39;s so easy to tap into from outside sources. Actually, if you think about it, that&amp;#39;s exactly what it was designed for.
&lt;/p&gt;
&lt;p&gt;
In point of fact, creating such a localized page requires only a few things:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
the addition of the standard localized &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; &lt;abbr class="description" title="Navigation Bar"&gt;navbar&lt;/abbr&gt; to the top of the page to carry users back to their local station or pass them on to &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt;,
&lt;/li&gt;
&lt;li&gt;
a reworking of the page header to showcase the specific logo or content of the page rather than the organization behind it,
&lt;/li&gt;
&lt;li&gt;
the elimination of any internal site navigation, search boxes, or links meant to get site users around that specific site rather than just the specifically localized content,
&lt;/li&gt;
&lt;li&gt;
the elimination of any internal support link coupled with the addition of a &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; localized station support link (and this is very important to make it valuable to other stations,)
&lt;/li&gt;
&lt;li&gt;
a reworking of the page footer to again eliminate any standard internal site links and the addition of a sublimated organization logo, credit, link, and copyright/trademark statement,&lt;/li&gt;
&lt;li&gt;and, finally, a way to receive the station identification parameter through the &lt;acronym title="Uniform Resource Locator"&gt;URL&lt;/acronym&gt; and pass it into all of the &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; links.
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
It&amp;#39;s really a lot less complicated than it sounds.
&lt;/p&gt;
&lt;h3&gt;Reasons For Doing This&lt;/h3&gt;

&lt;p&gt;
If you&amp;#39;re wondering why a station would want to do this with their own content, there are a number of reasons:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
Showcasing your local art, history, culture, entertainment, and educational resources to stations and web users across the rest of the country is yet one more way of adding value to YOUR station as a modern and relevant connection to the rest of the world.
&lt;/li&gt;
&lt;li&gt;
It makes YOUR local station a more attractive and valuable outlet for the people who create this kind of content to bring it to.
&lt;/li&gt;
&lt;li&gt;
It supports and adds value to the system as a whole.
&lt;/li&gt;
&lt;li&gt;
It adds some small bit of value to your nationally distributed programs when stations considering running them know that there&amp;#39;s localized content that they can link into.
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;Station Example&lt;/h3&gt;
&lt;p&gt;
&lt;a href="http://www.soptv.org/scs/" title="SOPTV Presents...Sierra Center Stage" class="externalLink"&gt;&lt;img class="imgright" width="180" height="244" src="http://www.ptvguy.com/wp-content/uploads/2006/06/scs.jpg" alt="Sierra Center Stage Logo" /&gt;&lt;/a&gt;If you&amp;#39;re tired of just hearing about this and you&amp;#39;d rather see it in action, then check out &lt;em&gt;&lt;a href="http://www.soptv.org/scs/" class="externalLink" title="Sierra Center Stage"&gt;Sierra Center Stage&lt;/a&gt;&lt;/em&gt;, a new program being distributed by &lt;a href="http://www.soptv.org/" class="externalLink" title="Southern Oregon Public Television"&gt;Southern Oregon Public Television&lt;/a&gt;. To reach that page normally as a part of the &lt;a href="http://www.soptv.org/" class="externalLink" title="Southern Oregon Public Television"&gt;SOPTV&lt;/a&gt; website, you would go to &lt;a href="http://www.soptv.org/scs/" class="externalLink" title="Sierra Center Stage page on the Southern Oregon Public Television website."&gt;www.soptv.org/scs&lt;/a&gt;. That takes you to the non-localized version of that page meant for users of the &lt;a href="http://www.soptv.org/" class="externalLink" title="Southern Oregon Public Television"&gt;SOPTV&lt;/a&gt; site. However, with the simple addition of a question mark and your station&amp;#39;s call letters (try &lt;a href="http://www.soptv.org/scs?wnet" class="externalLink" title="Sierra Center Stage on the Southern Oregon Public Television website localized to member station WNET."&gt;www.soptv.org/scs?wnet&lt;/a&gt;) you get a localized version of the page complete with station logo and a support link tied to your local station&amp;#39;s membership page (provided your membership link is current with &lt;a href="http://www.pbs.org/remotecontrol/" class="externalLink" title="Public Broadcasting Service Station Remote Control"&gt;PBS Station Remote Control&lt;/a&gt;.)
&lt;/p&gt;
&lt;h3&gt;Potential Worries&lt;/h3&gt;

&lt;p&gt;
If you&amp;#39;re worried that this could somehow affect currently localized users and perhaps &amp;quot;relocalize&amp;quot; them to a different station, it can&amp;#39;t. The already existing &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; localization cookie system is not affected in any way by this kind of &amp;quot;homemade localization.&amp;quot; Since it doesn&amp;#39;t store anything on the client computer, it&amp;#39;s temporary and page-specific. When an already localized user clicks through to the &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; main site-even on the support link-the already existing &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; localization cookie will override any parameters passed in the &lt;acronym title="Uniform Resource Locator"&gt;URL&lt;/acronym&gt; and localize them accordingly. Therefore, you can&amp;#39;t lose already localized viewers though you might potentially gain a few.
&lt;/p&gt;
&lt;p&gt;
If you&amp;#39;re worried about what will happen to users who bookmark a page like this, they&amp;#39;ll bookmark your localization code along with the site &lt;acronym title="Uniform Resource Locator"&gt;URL&lt;/acronym&gt;. That means that unless they alter the properties of their bookmark, it will always open localized to you.
&lt;/p&gt;
&lt;p&gt;
If you&amp;#39;re worried that localizing your content for other stations could cut into potential revenues by turning the support links away from you, then this one you&amp;#39;ll actually have to weigh against your own records. For the most part, stations do not make support money from web content linked into by other stations. However, if your station actually does, then that content would not be a good candidate for localization. No one should lose money or users by doing this.
&lt;/p&gt;
&lt;h3&gt;Beyond Even The Stations Themselves&lt;/h3&gt;

&lt;p&gt;
This kind of extension of station localization and what it can do goes even beyond public television station websites. Any piece of web content on any site can be localized to make it useful and valuable to &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; member stations that want to link into it. That means that any organization or individual out there with a website can make localized content available to stations to use or not use as they see fit. I don&amp;#39;t think that it takes a major stretch of the imagination to envision a time when web producers and web content distributors will approach public broadcasting stations in much the same way as program producers and distributors with the hope of having their content featured by those stations.
&lt;/p&gt;
&lt;h3&gt;Non-Station Example&lt;/h3&gt;
&lt;p&gt;
&lt;a href="http://www.ptvguy.com/xtras/" class="externalLink" title="Online Xtras"&gt;&lt;img id="image38" class="imgleft" width="203" height="203" src="http://www.ptvguy.com/wp-content/uploads/2006/06/onlineXtras.jpg" alt="Online Xtras cutaway view" /&gt;&lt;/a&gt;If you&amp;#39;re wondering how even a non-station website could manage this, then check out &lt;em&gt;&lt;a href="http://www.ptvguy.com/xtras/" class="externalLink" title="Online Xtras"&gt;Online Xtras&lt;/a&gt;&lt;/em&gt;, a page I created on my &lt;a href="http://www.ptvguy.com/" title="ptvGuy website located at www.ptvguy.com"&gt;ptvguy.com&lt;/a&gt; website as a collection of links to &lt;a href="http://www.ptvguy.com/2006/03/23/local-station-promotion-of-pbs-online-only-content/" title="Previous ptvGuy post on local station promotion of Public Broadcasting Service online-only content."&gt;PBS online-only content&lt;/a&gt; (and, yes, I still hate the name, but I can&amp;#39;t think of anything better.) If you go to the page directly at &lt;a href="http://www.ptvguy.com/xtras/" class="externalLink" title="Online Xtras"&gt;www.ptvguy.com/xtras/&lt;/a&gt; (spelled without the &amp;quot;e&amp;quot; as x-t-r-a-s,) then you&amp;#39;ll see that it wasn&amp;#39;t designed to be used as anything other than a localized page. All the localized station linking ends up missing the station identification and the &lt;abbr class="description" title="Navigation Bar"&gt;navbar&lt;/abbr&gt; at the top is taller than it should be, because there&amp;#39;s no image where the station logo goes. However, if you go to the page with station linking by adding a question mark, the word &amp;quot;station,&amp;quot; an equal sign, and your station&amp;#39;s call letters (as in &lt;a href="http://www.ptvguy.com/xtras?station=wyes" class="externalLink" title="Online Xtras located on the ptvGuy website and localized for member station WYES." &gt;www.ptvguy.com/xtras?station=wyes&lt;/a&gt;) then you&amp;#39;ll see a version of the page localized to your station. If you&amp;#39;d rather see how an actual station website might link into this, then have a look at the left sidebar on the homepage of &lt;a href="http://www.soptv.org/" class="externalLink" title="Southern Oregon Public Television"&gt;SOPTV&lt;/a&gt; and click through to &lt;em&gt;&lt;a href="http://www.ptvguy.com/xtras/" class="externalLink" title="Online Xtras" &gt;Online Xtras&lt;/a&gt;&lt;/em&gt;. It not only can be done, it IS being done.
&lt;/p&gt;
&lt;h3&gt;How To Do It&lt;/h3&gt;

&lt;p&gt;
If you&amp;#39;re wondering why my two examples use different station-linking code, it&amp;#39;s because I set them up using two different server technologies. One utilizes simple &lt;acronym title="Server-Side Include"&gt;SSI&lt;/acronym&gt; directives that you&amp;#39;d normally see on an &lt;acronym title="Server-parsed HyperText Markup Language"&gt;SHTML&lt;/acronym&gt; page and the other utilizes &lt;acronym title="A recursive acronym that stands for PHP: Hypertext Preprocessor and originally meant Personal Home Page."&gt;PHP&lt;/acronym&gt;. The point I wanted to make with this is that it doesn&amp;#39;t really matter how you set it up as long as it localizes correctly and you make the method clear. I kept it as simple as possible. The only reason that I didn&amp;#39;t create an &lt;acronym title="Active Server Page"&gt;ASP&lt;/acronym&gt; example is that I don&amp;#39;t have anything available on a Microsoft Windows server worth localizing.
&lt;/p&gt;
&lt;p&gt;
I&amp;#39;ve put together a &lt;a href="http://www.ptvguy.com/downloads/localization.zip" class="externalLink" title="Downloadable file containing the original code behind the two localization examples." &gt;downloadable file&lt;/a&gt; with all the pertinent underlying code and included content from both of these examples, so that you can look it over and see how simple it is. If you have content that could be used in this way, why not give it a try. If you know of content that could be used in this way, why not suggest it. You don&amp;#39;t lose anything by doing this. You do, however, have a potential to increase your audience while simultaneously supporting &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; member stations everywhere.
&lt;/p&gt;
&lt;h3&gt;How Will We Use It&lt;/h3&gt;

&lt;p&gt;
If we can get enough localized content together to justify the effort, then we could create portal pages (like my &lt;em&gt;&lt;a href="http://www.ptvguy.com/xtras/" class="externalLink" title="Online Xtras" &gt;Online Xtras&lt;/a&gt;&lt;/em&gt; example) to organize or categorize the content and create a single link-in point for stations to connect to. Who knows, maybe we can get enough high-quality content together to get &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; itself interested in creating more portal collections like &lt;a href="http://www.pbs.org/wgbh/globalconnections/" class="externalLink" title="Global Connections"&gt;Global Connections&lt;/a&gt; or &lt;a href="http://www.pbs.org/wnet/aaworld/" class="externalLink" title="African American World"&gt;African American World&lt;/a&gt;. I already know of some more local content that could be added into this, and I bet you do to.
&lt;/p&gt;
&lt;p&gt;
&amp;quot;&lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service website"&gt;PBS.org&lt;/a&gt;&amp;#39;s top priority is presenting content that supports the broadcast schedule,&amp;quot; said Cindy Johanson, Senior Vice President, &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; Interactive and Education during &lt;a href="http://www.current.org/web/web0219portals.html" class="externalLink" title="CURRENT: New doors to old content: CPB backs web portals about Middle East, Afro-America"&gt;an interview&lt;/a&gt; back in 2002. Although many aspects of the web itself and how &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; uses it have changed and evolved since then, budget and staffing cuts have forced &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; to be extremely selective in what they put out and support on their website. Witness the move of &lt;a href="http://litlink.ket.org/" class="externalLink" title="Public Broadcasting Service LiteracyLink"&gt;PBS LiteracyLink&lt;/a&gt;&amp;trade; from &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; to &lt;a href="http://www.ket.org/" class="externalLink" title="Kentucky Educational Television"&gt;KET&lt;/a&gt; (speaking of which, there&amp;#39;s a broadly used resource that I&amp;#39;d love to see localized,) and the cutting of &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; Campus, &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; YOU, and a number of other &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; resources. Frankly, good content is not always supportable content.
&lt;/p&gt;

&lt;p&gt;
I don&amp;#39;t believe that local stations can or should be solely dependent on &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; to provide original web content any longer-which is not to say that we don&amp;#39;t still need them. However, we are more than capable of (and in fact already are) producing such content. It amazes me that we are not tapping into ourselves as the incredible resource that we are. We are an already existing network of interconnected content providers and developers. If we open up our own resources to each other and tap into other organizations and individuals willing share their content with us, then, in combination with &lt;a href="http://www.pbs.org/" class="externalLink" title="Public Broadcasting Service"&gt;PBS&lt;/a&gt; itself, we will become something greater than the sum total of our parts and, in fact, something greater than anything else on the web.
&lt;/p&gt;
&lt;p&gt;
&amp;quot;Can we build it? Yes, we can.&amp;quot;
&lt;/p&gt;
&lt;p&gt;
Thank you all, code well, and good night.
&lt;/p&gt;
&lt;p&gt;&lt;!-- google_ad_section_end --&gt;
&lt;/p&gt;
&lt;a href="http://www.ptvguy.com/tag/african-american-world/" rel="tag"&gt;African American World&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/asp/" rel="tag"&gt;ASP&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/bookmark/" rel="tag"&gt;bookmark&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/budget/" rel="tag"&gt;budget&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/california/" rel="tag"&gt;California&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/cindy-johanson/" rel="tag"&gt;Cindy Johanson&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/coding/" rel="tag"&gt;coding&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/content/" rel="tag"&gt;content&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/content-distributors/" rel="tag"&gt;content distributors&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/cookies/" rel="tag"&gt;cookies&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/current/" rel="tag"&gt;CURRENT&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/downloads/" rel="tag"&gt;downloads&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/footer/" rel="tag"&gt;footer&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/frontline/" rel="tag"&gt;Frontline&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/global-connections/" rel="tag"&gt;Global Connections&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/header/" rel="tag"&gt;header&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/income/" rel="tag"&gt;income&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/interactivity/" rel="tag"&gt;interactivity&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/interconnectedness/" rel="tag"&gt;interconnectedness&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/internal-navigation/" rel="tag"&gt;internal navigation&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/ket/" rel="tag"&gt;KET&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/kixe/" rel="tag"&gt;KIXE&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/literacylink/" rel="tag"&gt;LiteracyLink&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/local/" rel="tag"&gt;local&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/localization/" rel="tag"&gt;localization&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/markup/" rel="tag"&gt;markup&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/medford/" rel="tag"&gt;Medford&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/membership/" rel="tag"&gt;membership&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/national/" rel="tag"&gt;national&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/nationally-distributed-programming/" rel="tag"&gt;nationally distributed programming&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/navbar/" rel="tag"&gt;navbar&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/nova/" rel="tag"&gt;Nova&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/online-xtras/" rel="tag"&gt;Online Xtras&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/oregon/" rel="tag"&gt;Oregon&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/original-content/" rel="tag"&gt;original content&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/parameters/" rel="tag"&gt;parameters&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/pbs/" rel="tag"&gt;PBS&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/pbs-campus/" rel="tag"&gt;PBS Campus&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/pbs-interactive/" rel="tag"&gt;PBS Interactive&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/pbs-navbar/" rel="tag"&gt;PBS navbar&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/pbs-station-remote-control/" rel="tag"&gt;PBS station remote control&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/pbs-you/" rel="tag"&gt;PBS YOU&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/php/" rel="tag"&gt;PHP&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/portal-pages/" rel="tag"&gt;portal pages&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/producers/" rel="tag"&gt;producers&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/programming/" rel="tag"&gt;programming&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/programs/" rel="tag"&gt;programs&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/promotion/" rel="tag"&gt;promotion&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/public-broadcasting/" rel="tag"&gt;public broadcasting&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/public-radio/" rel="tag"&gt;public radio&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/public-television/" rel="tag"&gt;public television&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/redding/" rel="tag"&gt;Redding&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/revenues/" rel="tag"&gt;revenues&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/scripts/" rel="tag"&gt;scripts&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/self-sufficiency/" rel="tag"&gt;self sufficiency&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/server/" rel="tag"&gt;server&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/shtml/" rel="tag"&gt;SHTML&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/sierra-center-stage/" rel="tag"&gt;Sierra Center Stage&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/site-navigation/" rel="tag"&gt;site navigation&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/soptv/" rel="tag"&gt;SOPTV&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/ssi/" rel="tag"&gt;SSI&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/staffing-cuts/" rel="tag"&gt;staffing cuts&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/station/" rel="tag"&gt;station&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/station-linking-code/" rel="tag"&gt;station linking code&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/support/" rel="tag"&gt;support&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/url/" rel="tag"&gt;URL&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/value/" rel="tag"&gt;value&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/web-2.0/" rel="tag"&gt;Web 2.0&lt;/a&gt;, &lt;a href="http://www.ptvguy.com/tag/wgbh/" rel="tag"&gt;WGBH&lt;/a&gt;African American World, ASP, bookmark, budget, California, Cindy Johanson, coding, content, content distributors, cookies, CURRENT, downloads, footer, Frontline, Global Connections, header, income, interactivity, interconnectedness, internal navigation, KET, KIXE, LiteracyLink, local, localization, markup, Medford, membership, national, nationally distributed programming, navbar, Nova, Online Xtras, Oregon, original content, parameters, PBS, PBS Campus, PBS Interactive, PBS navbar, PBS station [...]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=mxmCYouy"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=mxmCYouy" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=rLwHfC5J"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=rLwHfC5J" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=Kxg97maK"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=Kxg97maK" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=PHWmBjoj"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=PHWmBjoj" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~f/ptvguy?a=fwr5e7xy"&gt;&lt;img src="http://feeds.feedburner.com/~f/ptvguy?i=fwr5e7xy" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;</description>
		<wfw:commentRSS>http://www.ptvguy.com/localizing-beyond-pbs-an-open-proposal/feed/</wfw:commentRSS>
			
<itunes:duration>14:03</itunes:duration>
		<itunes:subtitle>Introduction


In one of its most brilliant decisions ever, PBS decided to downplay itself as a national entity in favor of extending the perceived reach of ...</itunes:subtitle>
		<itunes:summary>Introduction


In one of its most brilliant decisions ever, PBS decided to downplay itself as a national entity in favor of extending the perceived reach of every one of its local member stations. (Web: best medium for local/national convergence?) In other words, PBS in Medford, Oregon IS SOPTV, PBS in Redding, California IS KIXE, and PBS in your local town or city IS your local station. This doesn#39;t just happen on-air, it extends online as well.



When a local station website links to a PBS program site like Frontline or Nova, it uses station-linking code to pass its station identification to that site which in turn dynamically generates a localized version of that page complete with a backlinked station logo and localized broadcast information. The end result for the user is that their local station website and the PBS.org national site (the most popular dot org site on the planet) work together as a single, cohesive unit creating the perception that they are one whole site. In fact, some studies have shown that many users are totally unaware of ever having left the local station site.


PBS localization has added to the perceived value of the local station site as a community resource. It extends the perceived reach of the local station into vast resources and archives of information that no one station could ever achieve. Basically, PBS was a Web 2.0 resource long before anyone conceived of such a term to describe that kind of online interaction and interconnectedness. Now, while the rest of the web tries to catch up to even that level, the time has come for us to extend this even further.



Individual stations across the country have for years been creating small (and some very large) pieces of original web content. Some of these are tied to local productions or events and hold little interest outside the local community, but many are very interesting slices of local history, art, and culture and have value to the system as a whole. This kind of web content along with content tied to nationally distributed programs would be ideal for localization.

The Proposal


I propose the creation of localized versions of such pages set up to take advantage of and function similarly to the already existing localization system in place on PBS.org. The beauty of this system is that it#39;s so easy to tap into from outside sources. Actually, if you think about it, that#39;s exactly what it was designed for.


In point of fact, creating such a localized page requires only a few things:



the addition of the standard localized PBS navbar to the top of the page to carry users back to their local station or pass them on to PBS,


a reworking of the page header to showcase the specific logo or content of the page rather than the organization behind it,


the elimination of any internal site navigation, search boxes, or links meant to get site users around that specific site rather than just the specifically localized content,


the elimination of any internal support link coupled with the addition of a PBS localized station support link (and this is very important to make it valuable to other stations,)


a reworking of the page footer to again eliminate any standard internal site links and the addition of a sublimated organization logo, credit, link, and copyright/trademark statement,
and, finally, a way to receive the station identification parameter through the URL and pass it into all of the PBS links.



It#39;s really a lot less complicated than it sounds.

Reasons For Doing This


If you#39;re wondering why a station would want to do this with their own content, there are a number of reasons:



Showcasing your local art, history, culture, entertainment, and educational resources to stations and web users across the rest of the country is yet one more way of adding value to YOUR station as a modern and relevant connection to the rest of the world.


It makes YOUR local </itunes:summary>
		<itunes:keywords>All, coding, content, markup, original content, PBS, promotion, public television, SOPTV, station, WGBH, scripts, site navigation, interactivity, Frontline, public broadcasting, public radio, server, localization, KIXE, Nova, station-linking code, Web 2.0, PBS navbar, header, footer, internal navigation, navbar, support, membership, value, programs, programming, nationally distributed programming, local, national, Cindy Johanson, budget, staffing cuts, Sierra Center Stage, Online Xtras, PBS station remote control, cookies, URL, parameters, bookmark, revenues, income, producers, content distributors, SSI, SHTML, PHP, ASP, downloads, portal pages, Global Connections, African American World, LiteracyLink, PBS Campus, PBS YOU, KET, PBS Interactive, interconnectedness, CURRENT, self-sufficiency, Redding, California, Oregon, Medford</itunes:keywords>
		<itunes:author>ptvGuy</itunes:author>
		<itunes:explicit>no</itunes:explicit>
		<itunes:block>No</itunes:block>
	<feedburner:origLink>http://www.ptvguy.com/localizing-beyond-pbs-an-open-proposal/</feedburner:origLink><enclosure url="http://feeds.feedburner.com/~r/ptvguy/~5/76625539/ptvguy062706.mp3" length="3375232" type="audio/mpeg" /><feedburner:origEnclosureLink>http://www.ptvguy.com/podpress_trac/feed/39/0/ptvguy062706.mp3</feedburner:origEnclosureLink></item>
	<feedburner:awareness>http://api.feedburner.com/awareness/1.0/GetFeedData?uri=ptvguy</feedburner:awareness></channel>
</rss>
