<?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: Use of JPEG2000 for Broadcast Video Transmission</title> <atom:link href="http://dltj.org/article/hbo-jpeg2000/feed/" rel="self" type="application/rss+xml" /><link>http://dltj.org/article/hbo-jpeg2000/</link> <description>We&#039;re Disrupted, We&#039;re Librarians, and We&#039;re Not Going to Take It Anymore</description> <lastBuildDate>Tue, 22 May 2012 19:03:41 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <item><title>By: infopeep</title><link>http://dltj.org/article/hbo-jpeg2000/comment-page-1/#comment-162513</link> <dc:creator>infopeep</dc:creator> <pubDate>Fri, 15 May 2009 19:39:21 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/?p=958#comment-162513</guid> <description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Murray, Peter: Use of JPEG2000 for Broadcast Video Transmission http://snipurl.com/i2xfs&lt;/span&gt;&lt;/span&gt;</description> <content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Murray, Peter: Use of JPEG2000 for Broadcast Video Transmission <a href="http://snipurl.com/i2xfs" rel="nofollow">http://snipurl.com/i2xfs</a></span></span></span></p> ]]></content:encoded> </item> <item><title>By: Peter Murray</title><link>http://dltj.org/article/hbo-jpeg2000/comment-page-1/#comment-162514</link> <dc:creator>Peter Murray</dc:creator> <pubDate>Fri, 15 May 2009 18:17:04 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/?p=958#comment-162514</guid> <description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;New blog post: Use of JPEG2000 for Broadcast Video Transmission http://dltj.org/article/hbo-jpeg2000/&lt;/span&gt;&lt;/span&gt;</description> <content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">New blog post: Use of JPEG2000 for Broadcast Video Transmission <a href="http://dltj.org/article/hbo-jpeg2000/" rel="nofollow">http://dltj.org/article/hbo-jpeg2000/</a></span></span></span></p> ]]></content:encoded> </item> <item><title>By: Ron Murray</title><link>http://dltj.org/article/hbo-jpeg2000/comment-page-1/#comment-35910</link> <dc:creator>Ron Murray</dc:creator> <pubDate>Fri, 15 May 2009 17:30:09 +0000</pubDate> <guid isPermaLink="false">http://dltj.org/?p=958#comment-35910</guid> <description>A reassuring interpretation of this article is that JPEG 2000 is solidifying its in those arenas where quality and cost considerations must simultaneously be satisfied.The backend/Last Mile comments about content delivery relates directly to concerns that because browser support is withheld by the major operating system manufacturer, archival operations that use JPEG 2000 are problematic. It is possible to have tunable, high-quality archive content and from that to deliver quality/format imagery on demand. This is consistent with the OAIS model.What we also see here is that the engineering community (programmers, hardware manufacturers) is taking JEPG 2000 to heart and that format sustainability - for them - will not be a problem.Results of a recent U. Conn survey indicate that local, in-depth knowledge about JPEG 2000 capabilities within *our* community is still lacking. Perhaps a community-sponsored training/education program for Cultural Heritage hardcore techies in JPEG 2000 application programming is justified now?</description> <content:encoded><![CDATA[<p>A reassuring interpretation of this article is that JPEG 2000 is solidifying its in those arenas where quality and cost considerations must simultaneously be satisfied.</p><p>The backend/Last Mile comments about content delivery relates directly to concerns that because browser support is withheld by the major operating system manufacturer, archival operations that use JPEG 2000 are problematic. It is possible to have tunable, high-quality archive content and from that to deliver quality/format imagery on demand. This is consistent with the OAIS model.</p><p>What we also see here is that the engineering community (programmers, hardware manufacturers) is taking JEPG 2000 to heart and that format sustainability &#8211; for them &#8211; will not be a problem.</p><p>Results of a recent U. Conn survey indicate that local, in-depth knowledge about JPEG 2000 capabilities within *our* community is still lacking. Perhaps a community-sponsored training/education program for Cultural Heritage hardcore techies in JPEG 2000 application programming is justified now?</p> ]]></content:encoded> </item> </channel> </rss>
<!-- Served from: dltj.org @ 2012-05-23 04:23:29 by W3 Total Cache -->
