<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: A Standard REST API for Public Broadcasting?</title>
	<atom:link href="http://johntynan.com/archives/29/feed" rel="self" type="application/rss+xml" />
	<link>http://johntynan.com/archives/29</link>
	<description>A friendly journal for introspection, wonder and bliss.</description>
	<lastBuildDate>Sun, 29 Nov 2009 12:12:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: John Tynan</title>
		<link>http://johntynan.com/archives/29/comment-page-1#comment-1711</link>
		<dc:creator>John Tynan</dc:creator>
		<pubDate>Wed, 23 May 2007 20:35:35 +0000</pubDate>
		<guid isPermaLink="false">http://johntynan.com/archives/29#comment-1711</guid>
		<description>From Jack Brighton at WILL - http://www.will.uiuc.edu/

On your pondering of Atom, it seems like RSS on steroids to me, and
could be very useful for sharing content in a structured, cohesive way.
(I think you&#039;re right about PBCore being better for digital asset
management, especially as Content Depot and NGIS come on line, and with
the MXF file format...)

Seems like there are several or many ways to expose content and
metadata, including RSS, Atom, etc.  So the question might be: What are
we trying to do or enable with content-sharing?  If we can answer that,
we might find it easier to zero in on the best solution.  

I&#039;m not sure I know what everybody else in the public media system wants
to do, so I&#039;m trying to prepare WILL to participate in whatever solution
eventually emerges.  We&#039;re trying to master the exposure of content and
expression of metadata in whatever format might be useful.  We can now
produce full PBCore records, RSS, and Atom feeds direct from the content
management system.  We can express in any XML format desired, so if
there&#039;s a media microformat that emerges, we could probably speak that
language pretty quickly.  What you&#039;re suggesting makes a great deal of
sense to me, and I want to think about it some more.</description>
		<content:encoded><![CDATA[<p>From Jack Brighton at WILL &#8211; <a href="http://www.will.uiuc.edu/" rel="nofollow">http://www.will.uiuc.edu/</a></p>
<p>On your pondering of Atom, it seems like RSS on steroids to me, and<br />
could be very useful for sharing content in a structured, cohesive way.<br />
(I think you&#8217;re right about PBCore being better for digital asset<br />
management, especially as Content Depot and NGIS come on line, and with<br />
the MXF file format&#8230;)</p>
<p>Seems like there are several or many ways to expose content and<br />
metadata, including RSS, Atom, etc.  So the question might be: What are<br />
we trying to do or enable with content-sharing?  If we can answer that,<br />
we might find it easier to zero in on the best solution.  </p>
<p>I&#8217;m not sure I know what everybody else in the public media system wants<br />
to do, so I&#8217;m trying to prepare WILL to participate in whatever solution<br />
eventually emerges.  We&#8217;re trying to master the exposure of content and<br />
expression of metadata in whatever format might be useful.  We can now<br />
produce full PBCore records, RSS, and Atom feeds direct from the content<br />
management system.  We can express in any XML format desired, so if<br />
there&#8217;s a media microformat that emerges, we could probably speak that<br />
language pretty quickly.  What you&#8217;re suggesting makes a great deal of<br />
sense to me, and I want to think about it some more.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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