<?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/"
		>
<channel>
	<title>Comments on: Calais: Free Semantic Tagger</title>
	<atom:link href="http://arnoldit.com/wordpress/2008/04/22/calais-free-semantic-tagger/feed/" rel="self" type="application/rss+xml" />
	<link>http://arnoldit.com/wordpress/2008/04/22/calais-free-semantic-tagger/</link>
	<description>by Stephen E. Arnold</description>
	<lastBuildDate>Tue, 22 May 2012 06:55:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Media Cloud: Foggy Payoff : Beyond Search</title>
		<link>http://arnoldit.com/wordpress/2008/04/22/calais-free-semantic-tagger/comment-page-1/#comment-44346</link>
		<dc:creator>Media Cloud: Foggy Payoff : Beyond Search</dc:creator>
		<pubDate>Thu, 12 Mar 2009 18:46:39 +0000</pubDate>
		<guid isPermaLink="false">http://arnoldit.com/wordpress/?p=301#comment-44346</guid>
		<description>[...] I wrote about Calais in 2008. You can find that article here. Calais makes use of ClearForest technology to perform semantic tagging. I am cautious when large [...]</description>
		<content:encoded><![CDATA[<p>[...] I wrote about Calais in 2008. You can find that article here. Calais makes use of ClearForest technology to perform semantic tagging. I am cautious when large [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen E. Arnold</title>
		<link>http://arnoldit.com/wordpress/2008/04/22/calais-free-semantic-tagger/comment-page-1/#comment-7682</link>
		<dc:creator>Stephen E. Arnold</dc:creator>
		<pubDate>Wed, 23 Apr 2008 22:10:11 +0000</pubDate>
		<guid isPermaLink="false">http://arnoldit.com/wordpress/?p=301#comment-7682</guid>
		<description>Thanks for taking the time to respond. In my experience, roll ups that control diverse media properties can change direction quickly. Examples include Rupert Murdoch&#039;s shift in the New York media market, Thomson&#039;s divestiture of newspapers, and Reed Elsevier&#039;s sale of uninteresting properties. Therefore, an initiative--no matter how well thought through or well intentioned--can be redirected, sold, or shut down deus ex machina. This was thrilling to a Greek theater goer, but not much fun for the hapless victim of a god&#039;s whimsy. The senior management of the information companies dominating certain content spaces like law, technical information, and business information have to answer to shareholders first, market realities second, and then new, high-technology initiatives. I understand your comments, but I stand by admonition for users of any &quot;free&quot; or &quot;new&quot; service from today&#039;s version of Ling-Temco-Vought-type companies to exercise prudence.
Stephen Arnold, April 23, 2008</description>
		<content:encoded><![CDATA[<p>Thanks for taking the time to respond. In my experience, roll ups that control diverse media properties can change direction quickly. Examples include Rupert Murdoch&#8217;s shift in the New York media market, Thomson&#8217;s divestiture of newspapers, and Reed Elsevier&#8217;s sale of uninteresting properties. Therefore, an initiative&#8211;no matter how well thought through or well intentioned&#8211;can be redirected, sold, or shut down deus ex machina. This was thrilling to a Greek theater goer, but not much fun for the hapless victim of a god&#8217;s whimsy. The senior management of the information companies dominating certain content spaces like law, technical information, and business information have to answer to shareholders first, market realities second, and then new, high-technology initiatives. I understand your comments, but I stand by admonition for users of any &#8220;free&#8221; or &#8220;new&#8221; service from today&#8217;s version of Ling-Temco-Vought-type companies to exercise prudence.<br />
Stephen Arnold, April 23, 2008</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Tague</title>
		<link>http://arnoldit.com/wordpress/2008/04/22/calais-free-semantic-tagger/comment-page-1/#comment-7647</link>
		<dc:creator>Thomas Tague</dc:creator>
		<pubDate>Wed, 23 Apr 2008 15:45:39 +0000</pubDate>
		<guid isPermaLink="false">http://arnoldit.com/wordpress/?p=301#comment-7647</guid>
		<description>Stephen:

Tom Tague, leader of the Calais Initiative at Thomson Reuters here.

First, thank you for taking the time to investigate Calais and write such a thoughtful posting. 99% of what we see is some flavor of &quot;Cool..here&#039;s a link&quot; - you actually take the time to address some substantive points.

I&#039;m going to respond with a few observations.

First, Calais and its associated tools are in a period of extended &quot;hyperdevelopment&quot;. We released the first version of Calais in late January and have released two significant updates since that time. We also have a major update scheduled for release on 5 May. That&#039;s the commitment we&#039;ve made to ourselves - new functionality delivered to the end user every month without fail. Our development activities focus on two core elements: 1) developing or sponsoring the development of an entire ecosystems of tools from sample applications to WordPress and Drupal modules to code libraries - all with the intention of making Calais accessible and relevant to a broader audience, and  2) Improvements in the core service itself. With each release of Calais we add a significant number of new entities, facts and events in existing and new domains. Starting with our next release the rate at which we roll out new elements and domains will begin to accelerate even faster.

Second, you bring up the point of commitment on the part of Thomson Reuters. As you mention you&#039;d be reluctant to build a business on top of the service. We&#039;ve learned something interesting over our first few months of operation: you can deploy a free service, you can deploy it for &quot;web scale&quot; volumes, you can tell people you&#039;re committed for the long run - it just doesn&#039;t matter. Unless you&#039;re prepared to back that with contractual commitments of performance and availability prudent organizations are not going to bet their businesses on it. We heard. We get it.

So - we&#039;re going to do just that in the very near future. In addition to the current service we will offer a version backed by a contractual agreement specifying reliability and long term availability. We haven&#039;t settled on pricing - but it will be modest. Very modest.

Before a few thousand people say &quot;Aha.. I knew the free service was too good to be true!&quot; let me make a few important points: The free service remains unchanged. The free service will have 100% of the functionality of the contractual service. The free service will continue to have generous usage limits (currently 40,000 transactions per day and increasing regularly). The free service is still available for commercial and non-commercial use. Period. No ifs ands or buts. The contractual service will provide an SLA - and more importantly the confidence to bet your business on Calais. 

We&#039;re incredibly excited about the level of attention Calais has received. Besides blog postings and articles in the Economist - over 3,000 developers have signed up to use the Calais service. The fact that 3,000 people are willing to spend time to develop innovative applications that have the potential to impact hundreds of thousands (can we say millions?) of end users is extraordinary. That its happened in a little under 90 days is amazing.

So, in summary. We&#039;re serious. We&#039;re here to stay. The capabilities and tools delivered by Calais will continue to grow every single month. We have some amazingly exciting stuff in the pipeline we can&#039;t talk about yet. And, I&#039;ll echo your suggestion - jump in and start experimenting. There&#039;s some great stuff to be built.

Regards,

Tom</description>
		<content:encoded><![CDATA[<p>Stephen:</p>
<p>Tom Tague, leader of the Calais Initiative at Thomson Reuters here.</p>
<p>First, thank you for taking the time to investigate Calais and write such a thoughtful posting. 99% of what we see is some flavor of &#8220;Cool..here&#8217;s a link&#8221; &#8211; you actually take the time to address some substantive points.</p>
<p>I&#8217;m going to respond with a few observations.</p>
<p>First, Calais and its associated tools are in a period of extended &#8220;hyperdevelopment&#8221;. We released the first version of Calais in late January and have released two significant updates since that time. We also have a major update scheduled for release on 5 May. That&#8217;s the commitment we&#8217;ve made to ourselves &#8211; new functionality delivered to the end user every month without fail. Our development activities focus on two core elements: 1) developing or sponsoring the development of an entire ecosystems of tools from sample applications to WordPress and Drupal modules to code libraries &#8211; all with the intention of making Calais accessible and relevant to a broader audience, and  2) Improvements in the core service itself. With each release of Calais we add a significant number of new entities, facts and events in existing and new domains. Starting with our next release the rate at which we roll out new elements and domains will begin to accelerate even faster.</p>
<p>Second, you bring up the point of commitment on the part of Thomson Reuters. As you mention you&#8217;d be reluctant to build a business on top of the service. We&#8217;ve learned something interesting over our first few months of operation: you can deploy a free service, you can deploy it for &#8220;web scale&#8221; volumes, you can tell people you&#8217;re committed for the long run &#8211; it just doesn&#8217;t matter. Unless you&#8217;re prepared to back that with contractual commitments of performance and availability prudent organizations are not going to bet their businesses on it. We heard. We get it.</p>
<p>So &#8211; we&#8217;re going to do just that in the very near future. In addition to the current service we will offer a version backed by a contractual agreement specifying reliability and long term availability. We haven&#8217;t settled on pricing &#8211; but it will be modest. Very modest.</p>
<p>Before a few thousand people say &#8220;Aha.. I knew the free service was too good to be true!&#8221; let me make a few important points: The free service remains unchanged. The free service will have 100% of the functionality of the contractual service. The free service will continue to have generous usage limits (currently 40,000 transactions per day and increasing regularly). The free service is still available for commercial and non-commercial use. Period. No ifs ands or buts. The contractual service will provide an SLA &#8211; and more importantly the confidence to bet your business on Calais. </p>
<p>We&#8217;re incredibly excited about the level of attention Calais has received. Besides blog postings and articles in the Economist &#8211; over 3,000 developers have signed up to use the Calais service. The fact that 3,000 people are willing to spend time to develop innovative applications that have the potential to impact hundreds of thousands (can we say millions?) of end users is extraordinary. That its happened in a little under 90 days is amazing.</p>
<p>So, in summary. We&#8217;re serious. We&#8217;re here to stay. The capabilities and tools delivered by Calais will continue to grow every single month. We have some amazingly exciting stuff in the pipeline we can&#8217;t talk about yet. And, I&#8217;ll echo your suggestion &#8211; jump in and start experimenting. There&#8217;s some great stuff to be built.</p>
<p>Regards,</p>
<p>Tom</p>
]]></content:encoded>
	</item>
</channel>
</rss>

