<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Further Major Kudos to Adobe on Open PDF, AJAX</title>
	<atom:link href="http://www.redmonk.com/jgovernor/2007/02/01/further-major-kudos-to-adobe-on-open-pdf-ajax/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/jgovernor/2007/02/01/further-major-kudos-to-adobe-on-open-pdf-ajax/</link>
	<description>An industry analyst blog looking at software ecosystems and convergence</description>
	<pubDate>Sat, 22 Nov 2008 20:15:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Andrew Shebanow</title>
		<link>http://www.redmonk.com/jgovernor/2007/02/01/further-major-kudos-to-adobe-on-open-pdf-ajax/#comment-18978</link>
		<dc:creator>Andrew Shebanow</dc:creator>
		<pubDate>Sat, 03 Feb 2007 16:49:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/02/01/further-major-kudos-to-adobe-on-open-pdf-ajax/#comment-18978</guid>
		<description>I think that at this point there are enough implementations of PDF to qualify under Sam Ruby's definition. He doesn't say that all those implementations must be open source, just one of them. I personally think iText qualifies - I've used it myself before I came to Adobe.

As for conformance suites, I agree this is an area where more work is needed. That is why I brought up the issue in response to Rosyna's question. I personally look forward to seeing a good conformance solution come out of the ISO effort.</description>
		<content:encoded><![CDATA[<p>I think that at this point there are enough implementations of PDF to qualify under Sam Ruby&#8217;s definition. He doesn&#8217;t say that all those implementations must be open source, just one of them. I personally think iText qualifies - I&#8217;ve used it myself before I came to Adobe.</p>
<p>As for conformance suites, I agree this is an area where more work is needed. That is why I brought up the issue in response to Rosyna&#8217;s question. I personally look forward to seeing a good conformance solution come out of the ISO effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis Villa</title>
		<link>http://www.redmonk.com/jgovernor/2007/02/01/further-major-kudos-to-adobe-on-open-pdf-ajax/#comment-17915</link>
		<dc:creator>Luis Villa</dc:creator>
		<pubDate>Fri, 02 Feb 2007 04:48:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/02/01/further-major-kudos-to-adobe-on-open-pdf-ajax/#comment-17915</guid>
		<description>A full open source community pdf implementation seems unlikely; lots of open source apps implement partial pdf support (abiword, evince/kpdf, OOo all come to mind), but I'd guess that most people just don't find pdf interesting enough to justify implementing the entire spec. If it does happen, it'll be from someone like Novell or IBM who has a corporate itch to scratch.</description>
		<content:encoded><![CDATA[<p>A full open source community pdf implementation seems unlikely; lots of open source apps implement partial pdf support (abiword, evince/kpdf, OOo all come to mind), but I&#8217;d guess that most people just don&#8217;t find pdf interesting enough to justify implementing the entire spec. If it does happen, it&#8217;ll be from someone like Novell or IBM who has a corporate itch to scratch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Ward</title>
		<link>http://www.redmonk.com/jgovernor/2007/02/01/further-major-kudos-to-adobe-on-open-pdf-ajax/#comment-17680</link>
		<dc:creator>James Ward</dc:creator>
		<pubDate>Thu, 01 Feb 2007 20:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/02/01/further-major-kudos-to-adobe-on-open-pdf-ajax/#comment-17680</guid>
		<description>Hi James,

There are numerous Open Source libraries that read and write PDF.  I use a number of them on Linux - Evince most frequently to view PDFs.

I don't totally buy that definition of Open Standards though.  While I agree that Open Standards work best when there is an Open Source RI (see Geir's recently blog on this), there are/were plenty of "Open Standards" without Open Source implementations.  With the exception of the Lynx browser (which no one really used at the time), before Netscape went Open Source, were there any Open Source Browsers?  Would this have made the W3C's HTML standard not an Open Standard?

Geir's Blog:
http://blogs.codehaus.org/people/geir/archives/001507_another_example_of_why_open_source_ris_for_specs_is_a_good_thing.html

-James</description>
		<content:encoded><![CDATA[<p>Hi James,</p>
<p>There are numerous Open Source libraries that read and write PDF.  I use a number of them on Linux - Evince most frequently to view PDFs.</p>
<p>I don&#8217;t totally buy that definition of Open Standards though.  While I agree that Open Standards work best when there is an Open Source RI (see Geir&#8217;s recently blog on this), there are/were plenty of &#8220;Open Standards&#8221; without Open Source implementations.  With the exception of the Lynx browser (which no one really used at the time), before Netscape went Open Source, were there any Open Source Browsers?  Would this have made the W3C&#8217;s HTML standard not an Open Standard?</p>
<p>Geir&#8217;s Blog:<br />
<a href="http://blogs.codehaus.org/people/geir/archives/001507_another_example_of_why_open_source_ris_for_specs_is_a_good_thing.html" rel="nofollow">http://blogs.codehaus.org/people/geir/archives/001507_another_example_of_why_open_source_ris_for_specs_is_a_good_thing.html</a></p>
<p>-James</p>
]]></content:encoded>
	</item>
</channel>
</rss>
