<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://community.openamplify.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Amplitude</title><link>http://community.openamplify.com/blogs/amplitude/default.aspx</link><description>Amplify’s CIO and co-founder holds forth on the company, the market, and the business of the “Comprehensive Web”</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40402.4139)</generator><item><title>Measuring ROI on Semantics</title><link>http://community.openamplify.com/blogs/amplitude/archive/2010/03/01/measuring-roi-on-semantics.aspx</link><pubDate>Mon, 01 Mar 2010 18:18:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:1812</guid><dc:creator>mikepetit</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=1812</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2010/03/01/measuring-roi-on-semantics.aspx#comments</comments><description>&lt;p&gt;We know, implicitly, that understanding the meaning of web content must make it easier to classify, to monetize, and to accomplish whatever mission we&amp;#39;re on. I mean, how can you use it if you don&amp;#39;t understand it? That&amp;#39;s obvious.&lt;/p&gt;...(&lt;a href="http://community.openamplify.com/blogs/amplitude/archive/2010/03/01/measuring-roi-on-semantics.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=1812" width="1" height="1"&gt;</description><category domain="http://community.openamplify.com/blogs/amplitude/archive/tags/semantic/default.aspx">semantic</category><category domain="http://community.openamplify.com/blogs/amplitude/archive/tags/click/default.aspx">click</category><category domain="http://community.openamplify.com/blogs/amplitude/archive/tags/metrics/default.aspx">metrics</category></item><item><title>Your Sick Isn't My Sick</title><link>http://community.openamplify.com/blogs/amplitude/archive/2010/03/01/your-sick-isn-t-my-sick.aspx</link><pubDate>Mon, 01 Mar 2010 18:02:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:1811</guid><dc:creator>mikepetit</dc:creator><slash:comments>3</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=1811</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2010/03/01/your-sick-isn-t-my-sick.aspx#comments</comments><description>&lt;p&gt;Even a word like &amp;quot;sick&amp;quot; can have both positive and negative associations, depending upon context. So how can an automated service like OpenAmplify hope to address the fact that one man&amp;#39;s bad sick is another man&amp;#39;s good sick? That&amp;#39;s one of the big challenges on the table for upcoming versions.&lt;/p&gt;...(&lt;a href="http://community.openamplify.com/blogs/amplitude/archive/2010/03/01/your-sick-isn-t-my-sick.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=1811" width="1" height="1"&gt;</description><category domain="http://community.openamplify.com/blogs/amplitude/archive/tags/context/default.aspx">context</category><category domain="http://community.openamplify.com/blogs/amplitude/archive/tags/sick/default.aspx">sick</category><category domain="http://community.openamplify.com/blogs/amplitude/archive/tags/audi/default.aspx">audi</category></item><item><title>Why this stuff is hard :-)</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/11/19/why-this-stuff-is-hard.aspx</link><pubDate>Thu, 19 Nov 2009 21:38:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:1467</guid><dc:creator>mikepetit</dc:creator><slash:comments>4</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=1467</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/11/19/why-this-stuff-is-hard.aspx#comments</comments><description>We just convened a team in New York City for three days of software design sessions. Way fun. On Monday night, we went down to NuBlu, a cool club on Avenue C, to hear some jazz. Some of you may know that I&amp;#39;ve been a jazz musician for most of my life;...(&lt;a href="http://community.openamplify.com/blogs/amplitude/archive/2009/11/19/why-this-stuff-is-hard.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=1467" width="1" height="1"&gt;</description></item><item><title>The Evolution of Web Search: Part III</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/11/17/the-evolution-of-web-search-part-iii.aspx</link><pubDate>Tue, 17 Nov 2009 18:55:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:1309</guid><dc:creator>mikepetit</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=1309</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/11/17/the-evolution-of-web-search-part-iii.aspx#comments</comments><description>In Part II, I opined about the limits of topical search, and said we need web search that truly informs us, rather than just overwhelms us. To support our decisions, we need search that brings in attitudes, emotions, and all the other aspects of the decision...(&lt;a href="http://community.openamplify.com/blogs/amplitude/archive/2009/11/17/the-evolution-of-web-search-part-iii.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=1309" width="1" height="1"&gt;</description></item><item><title>The Evolution of Web Search: Part II</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/10/29/the-evolution-of-web-search-part-ii.aspx</link><pubDate>Thu, 29 Oct 2009 17:50:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:1308</guid><dc:creator>mikepetit</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=1308</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/10/29/the-evolution-of-web-search-part-ii.aspx#comments</comments><description>&lt;p&gt;Really, what we want is for search to provide us not just with content,
but with some up-front understanding of the content. We want to make
decisions with the full meaning of the content: the attitudes, the
quality, the emotions, all of it. Just as we do with any important
decision, we want to make it by becoming &lt;i&gt;informed&lt;/i&gt;, not overwhelmed.&lt;/p&gt;...(&lt;a href="http://community.openamplify.com/blogs/amplitude/archive/2009/10/29/the-evolution-of-web-search-part-ii.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=1308" width="1" height="1"&gt;</description></item><item><title>The Evolution of Web Search: Part I</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/10/19/the-evolution-of-web-search-part-i.aspx</link><pubDate>Mon, 19 Oct 2009 17:45:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:1307</guid><dc:creator>mikepetit</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=1307</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/10/19/the-evolution-of-web-search-part-i.aspx#comments</comments><description>Life used to be so simple. You had only one choice for a telephone company; you picked up the phone and it just worked. Toothpaste was just toothpaste, and once you picked one, that was it, pretty much for life. It wasn&amp;#39;t that long ago when we only...(&lt;a href="http://community.openamplify.com/blogs/amplitude/archive/2009/10/19/the-evolution-of-web-search-part-i.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=1307" width="1" height="1"&gt;</description></item><item><title>Online Advertising Can Make Us All Cool</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/10/16/online-advertising-can-make-us-all-cool.aspx</link><pubDate>Fri, 16 Oct 2009 18:01:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:1310</guid><dc:creator>mikepetit</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=1310</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/10/16/online-advertising-can-make-us-all-cool.aspx#comments</comments><description>We all deal with online ads. Few of us would say that we want them; almost none of us would say that we like them. But, what if ads could make us cool ? I&amp;#39;ve mentioned my old Saab once or twice. It&amp;#39;s actually a pretty special Saab, a 1991 limited...(&lt;a href="http://community.openamplify.com/blogs/amplitude/archive/2009/10/16/online-advertising-can-make-us-all-cool.aspx"&gt;read more&lt;/a&gt;)&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=1310" width="1" height="1"&gt;</description></item><item><title>Eight Years Later</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/09/14/eight-years-later.aspx</link><pubDate>Mon, 14 Sep 2009 15:33:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:1067</guid><dc:creator>mikepetit</dc:creator><slash:comments>3</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=1067</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/09/14/eight-years-later.aspx#comments</comments><description>&lt;p&gt;I was in Stockholm on 9/11, eight years ago. Hapax was a new company, with a brand new product called FindEngine, an NLP-based search engine. I was sitting in a board meeting when Emil, our long-time Senior SysAdmin, stuck his head in the door, and said, &amp;quot;Mike, I thought I should tell you: it looks like a plane hit one of the World Trade Center Towers.&amp;quot;&lt;/p&gt;
&lt;p&gt;Bummer, I thought. Hope it&amp;#39;s nothing too bad. &amp;quot;Thanks, Emil, appreciate the heads-up.&amp;quot; After all, I was in a board meeting. Let&amp;#39;s get our priorities straight, I was thinking.&lt;/p&gt;
&lt;p&gt;A little while later, Emil interrupted again. His face said that something was wrong, very wrong. &amp;quot;Mike, another jet hit the other tower. They&amp;#39;re both burning.&amp;quot;&lt;/p&gt;
&lt;p&gt;Meeting adjourned. We ran downstairs to the TV room, and sat in utter disbelief as it all unfolded. My friends and colleagues, among them current colleagues Sandra, Emil, Kalle and Mark, could only sit helplessly, shocked themselves, but also aware of what I was going through. They knew I was from New York. They knew that my brother was in New York, and most of my best friends, too. They knew something bigger than just two burning buildings was taking place. Nobody said much, but we all knew. And we were all so helpless.&lt;/p&gt;
&lt;p&gt;The three days we all spent right after 9/11, working all-nighters at the request of the Swedish Secret Police to analyze a huge body of web intelligence, made us feel a little less powerless. My brother escaped the carnage, as did my friends, but every one of us knows somebody who lost somebody.&lt;/p&gt;
&lt;p&gt;Eight years later, Emil, Kalle, Sandra and many ex-Hapaxians are still my friends
and colleagues. We inhabit a different world, but the basic ties that
bind us all together are intact and, if anything, more important than
ever.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=1067" width="1" height="1"&gt;</description></item><item><title>Oracle/Calais a Good Example of What We Must Do</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/09/04/oracle-calais-a-good-example-of-what-we-must-do.aspx</link><pubDate>Fri, 04 Sep 2009 16:22:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:989</guid><dc:creator>mikepetit</dc:creator><slash:comments>1</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=989</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/09/04/oracle-calais-a-good-example-of-what-we-must-do.aspx#comments</comments><description>&lt;p&gt;Oracle&amp;#39;s announcement that it can access Calais data and tag rows in its RDF-oriented database system is a great example of something I&amp;#39;ve believed for some time: for the Semantic Web to deliver benefits, it must become part of the workflow. As more and more tools of the trade (in this case, a prominent DBMS) integrate semantic data into their fabric, the value of better classification and deeper machine understanding of content becomes more apparent. Bravo, Oracle, and bravo, Calais. This is the way forward.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=989" width="1" height="1"&gt;</description></item><item><title>Dorthy.com serves up the dreamscape</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/09/01/dorothy-com-serves-up-the-dreamscape.aspx</link><pubDate>Tue, 01 Sep 2009 13:20:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:948</guid><dc:creator>mikepetit</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=948</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/09/01/dorothy-com-serves-up-the-dreamscape.aspx#comments</comments><description>&lt;p&gt;A new site, &lt;a target="_blank" href="http://Dorthy.com"&gt;Dorthy.com&lt;/a&gt;, is getting ready to deliver your dreams, along with some pertinent advertising :-)&lt;/p&gt;
&lt;p&gt;They claim to be using, among other things, NLP to relate content conceptually, delivering that content to &amp;quot;dreampages&amp;quot; that you set up. Always wanted to sail around the globe? They&amp;#39;ll feed the dream, along with brand-oriented advertising to help you gear up for the trip.&lt;/p&gt;
&lt;p&gt;According to their press release, which you can read at &lt;a target="_blank" href="http://www.reuters.com/article/pressRelease/idUS49708%2B01-Sep-2009%2BBW20090901"&gt;http://www.reuters.com/article/pressRelease/idUS49708%2B01-Sep-2009%2BBW20090901&lt;/a&gt;, more than 90% of us have dreams we&amp;#39;d like to realize, and a goodly percentage of us use the Internet to figure out how to pursue them. Dorothy has a few ideas for us...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=948" width="1" height="1"&gt;</description></item><item><title>Cloud Computing Works!</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/08/20/cloud-computing-works.aspx</link><pubDate>Thu, 20 Aug 2009 15:50:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:825</guid><dc:creator>mikepetit</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=825</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/08/20/cloud-computing-works.aspx#comments</comments><description>&lt;p&gt;We got hit pretty hard last night. Somebody (or somebodies) really had some stuff to analyze! That&amp;#39;s great, of course, but it does pose a challenge to the infrastructure that underpins OpenAmplify, a challenge that requires management.&lt;/p&gt;
&lt;p&gt;For most of the history of computing, that management required significant planning: for average load, peaks, failover, etc. It also required that one purchase, lease or otherwise make available the hardware and software needed to handle the peaks, etc. Since the hardware was obsolete the moment it was procured, one was always compromising on cost/performance. &amp;quot;TIme sharing&amp;quot; was an alternative, but didn&amp;#39;t really scale very well. You just had to bite the bullet and write the checks. Big checks.&lt;/p&gt;
&lt;p&gt;Ah, the good old days: I would spend weeks, or even months, preparing plans, RFP&amp;#39;s, checklists...I could count on a bunch of really good, free lunches as I pitted the various vendors against each other. Eventually, I&amp;#39;d have an infrastructure that would suffice...for awhile.&lt;/p&gt;
&lt;p&gt;Those days are gone, at least for me. OpenAmplify is built on the Amazon EC2 cloud. No more free lunches. But, no more headaches, either (or, at least, far less of them). Our infrastructure makes itself bigger when the load increases, makes itself smaller when the load decreases, senses when a server is unhappy and simply replaces it with a new one. Presto! All automatic, no muss, no fuss. I get a monthly bill from Amazon, and they manage all the servers, networks, power supplies, and all the rest. I don&amp;#39;t even know what hardware they&amp;#39;re running.&lt;/p&gt;
&lt;p&gt;So when we got slammed last night, I got the best possible news: none. I didn&amp;#39;t even know about it until Ram mentioned it to me in today&amp;#39;s Managers Meeting.&lt;/p&gt;
&lt;p&gt;Cloud computing rules.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=825" width="1" height="1"&gt;</description></item><item><title>Triangulating Partnerships (Welcome, Glen!)</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/08/11/triangulating-partnerships-welcome-glen.aspx</link><pubDate>Tue, 11 Aug 2009 19:55:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:760</guid><dc:creator>mikepetit</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=760</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/08/11/triangulating-partnerships-welcome-glen.aspx#comments</comments><description>&lt;p&gt;We&amp;#39;ve recently had the good fortune to convince Glen Kushner to join the OpenAmplify team as VP for Business Development. In that role, Glen will build our business relationships, both bilaterally (that is, B2B, case by case) and more broadly as part of a partnership process.&lt;/p&gt;
&lt;p&gt;That partnership process is deeply interwoven with our Community. We&amp;#39;ve said, many times, that one of the primary objectives of the OpenAmplify community is to encourage and support the development of real-world applications that extend the benefits of the Semantic Web to all. This implies cooperation: someone needs to define what is needed, someone needs to describe how to meet that need, and someone needs to build it to that specification. Sometimes, one person can cover all three bases; more frequently, it&amp;#39;s a combination of talents that get the job done. We call it &amp;quot;triangulation&amp;quot;: OpenAmplify at one point of the triangle, a customer or user at another, and someone (or some ones) at the third point to make it happen.&lt;/p&gt;
&lt;p&gt;We try to encourage such collaboration at community.openamplify.com. The ability to create Web 3.0 projects, attract people to them, and take them over the finish line requires a certain kind of entrepreneur, and we want folks like that to make our Community their home. We underwrite that by providing a venue, a set of tools and, importantly, a meeting place for talent. We hope you&amp;#39;ll create Projects from your best ideas, or add your abilities to other peoples&amp;#39; Projects.&lt;/p&gt;
&lt;p&gt;Glen, in the meantime, will be &amp;quot;triangulating&amp;quot; all over the country, and, concurrently, keeping an eye on the Community to see what promising Projects we should put extra horsepower behind. You never know when or where Glen might pop up...&lt;/p&gt;
&lt;p&gt;Welcome, Glen, VP of Triangles.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=760" width="1" height="1"&gt;</description></item><item><title>What do Twitter Users Actually DO?</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/07/15/what-do-twitter-users-actually-do.aspx</link><pubDate>Wed, 15 Jul 2009 20:38:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:594</guid><dc:creator>mikepetit</dc:creator><slash:comments>2</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=594</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/07/15/what-do-twitter-users-actually-do.aspx#comments</comments><description>&lt;p&gt;I&amp;#39;m really gratified by the number of apps being developed using OpenAmplify to mine sentiment from Twitter. Clearly, there&amp;#39;s a perceived need, and, as I recall, the folks at Twitter themselves have encouraged it.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m curious, though, as to what Twitter reveals about actions. Can it profile the Twitter community by career? Can we figure out how much intent there is to change things, or fix things, or...?&lt;/p&gt;
&lt;p&gt;The new TopicIntentions analysis could give us some answers. Since it groups the actions of each major topic by ActionType (buy, sell, read, build...) it should provide a really easy way to see what Twitter users intend to do about things. I&amp;#39;ll probably take a shot at mashing something up, but I&amp;#39;m betting the Community can do more, better than I can, and certainly faster.&lt;/p&gt;
&lt;p&gt;So, tell me, what do Twitterers actually &lt;i&gt;do&lt;/i&gt;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=594" width="1" height="1"&gt;</description></item><item><title>Now Available: TopicIntentions </title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/07/09/topicintentions.aspx</link><pubDate>Thu, 09 Jul 2009 13:36:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:504</guid><dc:creator>mikepetit</dc:creator><slash:comments>3</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=504</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/07/09/topicintentions.aspx#comments</comments><description>&lt;p&gt;Version 1.1 of OpenAmplify is now in production! It offers lots of good, new things and improved performance. One thing, however, merits particular attention in this blog, as it meaningfully advances the state of the Semantic Web.&lt;/p&gt;
&lt;p&gt;TopicIntentions is a new analysis, selectable via the standard API. It&amp;#39;s designed to make Actions much easier to consume at scale, as it directly relates each topic to its associated actions, via ActionType. It will tell you:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The most significant types of actions related to the topic (buy, sell, build, vote, whatever...)&lt;/li&gt;
&lt;li&gt;Whether the topic in question is the subject or object of that action (is the bear doing the chasing, or is the bear being chased?)&lt;/li&gt;
&lt;li&gt;The associated decisiveness and guidance scores for that ActionType as they relate to the topic in question.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All this in a single XML structure that includes all the other topic-related signals, such as Polarity.&lt;/p&gt;
&lt;p&gt;Why is this important? Because it permits users to focus, directly and efficiently, on what the author of the content is doing, did, or intends to do, and whether that decision can be influenced. Imagine being able to target online advertising directly to users whose posts or comments indicate an intent to take a desired action (buy or vote...) and who are seeking advice on it. Or imagine law enforcement being able to determine that certain conversations strongly advocate taking violent action against certain groups or persons. TopicIntentions makes these and limitless other uses of Actions possible, practical and scaleable.&lt;/p&gt;
&lt;p&gt;Only from OpenAmplify!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=504" width="1" height="1"&gt;</description></item><item><title>Wicked Difficult to Handle Dialect</title><link>http://community.openamplify.com/blogs/amplitude/archive/2009/06/29/wicked-difficult-to-handle-dialect.aspx</link><pubDate>Mon, 29 Jun 2009 13:10:00 GMT</pubDate><guid isPermaLink="false">3a1dd6da-b05c-4d0a-978a-930a9f8f3d2f:438</guid><dc:creator>mikepetit</dc:creator><slash:comments>1</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://community.openamplify.com/blogs/amplitude/rsscomments.aspx?PostID=438</wfw:commentRss><comments>http://community.openamplify.com/blogs/amplitude/archive/2009/06/29/wicked-difficult-to-handle-dialect.aspx#comments</comments><description>&lt;p&gt;I just returned from a few days on Cape Cod. Notwithstanding the weather, it was a nice time. There were, however, some comprehension issues.&lt;/p&gt;
&lt;p&gt;In a chocolate store, from the shopkeeper to a local customer: &amp;quot;Gift box is ready. Didja find the cod you needed?&amp;quot; I&amp;#39;m thinking, cod in a chocolate store? Of course, the reference was to a &amp;quot;card&amp;quot;, specifically a Happy Anniversary card, and I kind of knew that, but it still caught me off balance. It was the first day, after all: my ears hadn&amp;#39;t adjusted.&lt;/p&gt;
&lt;p&gt;On a t-shirt: &amp;quot;Welcome to the Lawbsta Bah&amp;quot;. Cute, but tough to parse, at least for a computer.&lt;/p&gt;
&lt;p&gt;My point? We can, and we will, always try to close the gap between human understanding and machine understanding, but the limitless variety of spoken and written dialect pretty much guarantees that humans will always stay ahead of the software.&lt;/p&gt;
&lt;p&gt;That means we&amp;#39;ll never run out of challenges. And that&amp;#39;s the good paht. Ain&amp;#39;t life a howlah?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://community.openamplify.com/aggbug.aspx?PostID=438" width="1" height="1"&gt;</description></item></channel></rss>