OpenAmplify V 2.0 Webinar

679 views

Published on

OpenAmplify is proud to release Version 2.0 to the world’s first comprehensive semantic platform. Full of new features, but still compatible with V1.1, OpenAmplify 2.0 reflects our commitment to delivering real-world, groundbreaking advances to the Semantic Web community.

As part of our latest release, OpenAmplify version 2.0, we offered a live webinar on January 21. 2010. OpenAmplify CIO Mike Petit led an informative short session about this new release and answered community questions.

Published in: Technology, Education
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
679
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

OpenAmplify V 2.0 Webinar

  1. 1. Introduction to Version 2.0 Webinar January 21, 2009
  2. 2. Webinar Agenda <ul><li>Introductions </li></ul><ul><li>Background: OpenAmplify History, Facts and Figures </li></ul><ul><li>2010: Semantic Metadata Breaks Out </li></ul><ul><ul><li>Challenges: understanding, implementation, measurement </li></ul></ul><ul><ul><li>OpenAmplify’s strategy </li></ul></ul><ul><ul><li>Version 2.0 in that strategic context </li></ul></ul><ul><li>Version 2.0 </li></ul><ul><ul><li>PinPoint Scoring </li></ul></ul><ul><ul><li>Text-level Polarity, Guidance, Decisiveness and Temporality </li></ul></ul><ul><ul><li>New signal: Contrast </li></ul></ul><ul><ul><li>Named Entity Recognition (NER) </li></ul></ul><ul><li>Futures </li></ul><ul><li>Q&A (Your Questions Addressed) </li></ul>
  3. 3. Background: OpenAmplify History, Facts and Figures <ul><li>Version 1.0 in February, 2009 </li></ul><ul><li>Developers in USA and Sweden Teamed Up </li></ul><ul><ul><li>Weeks in “Hotel Hapax” </li></ul></ul><ul><ul><li>Intensive sessions defining First “PV’s” </li></ul></ul><ul><ul><li>“ The Profs”: top-notch advisors </li></ul></ul><ul><ul><li>Mix of perfectionism and pragmatism: creative tension </li></ul></ul><ul><ul><li>Outcome: 11 “Signals” (cuter name than PV) to be in Version 1.0 </li></ul></ul>
  4. 4. Background: OpenAmplify History, Facts and Figures <ul><li>Version 1.0 in February, 2009 </li></ul><ul><li>Developers in USA and Sweden Teamed Up </li></ul><ul><ul><li>Weeks in “Hotel Hapax” </li></ul></ul><ul><ul><li>Intensive sessions defining First “PV’s” </li></ul></ul><ul><ul><li>“ The Profs”: top-notch advisors </li></ul></ul><ul><ul><li>Mix of perfectionism and pragmatism: creative tension </li></ul></ul><ul><ul><li>Outcome: 11 “Signals” (cuter name than PV) to be in Version 1.0 </li></ul></ul><ul><li>Since then </li></ul><ul><ul><li>Over 20 million analyses processed </li></ul></ul><ul><ul><li>Over 1500 developers with API keys </li></ul></ul><ul><ul><li>Two major releases (1.1 and 2.0) </li></ul></ul>
  5. 5. Background: OpenAmplify History, Facts and Figures <ul><li>How It Looks Now: Totally Cloud-based </li></ul><ul><ul><li>Amazon EC2 Cloud: massively scalable/dependable </li></ul></ul><ul><ul><li>Linux-based (mostly CentOS) </li></ul></ul><ul><ul><li>Apache/C++ application </li></ul></ul><ul><ul><li>Load-balanced using HAProxy </li></ul></ul><ul><ul><li>Tomcat support for spidering, etc. </li></ul></ul><ul><ul><li>Homogeneous applications architecture </li></ul></ul><ul><ul><li>mySQL for back-end (caching, transaction accounting, etc.) </li></ul></ul>
  6. 6. Background: OpenAmplify History, Facts and Figures <ul><li>Architecture Overview </li></ul><ul><ul><li>Each OA app server contains all functions in blue </li></ul></ul><ul><ul><li>App Servers “divide and conquer” each transaction for speed (provides failover too) </li></ul></ul><ul><ul><li>OA App Servers self-create/destroy on “voting” model according to load </li></ul></ul><ul><ul><li>Databases are replicated master/slave clusters with scalability </li></ul></ul><ul><ul><li>No single point of failure </li></ul></ul><ul><ul><li>If Amazon is up, we’re up (comfortable bet…) </li></ul></ul><ul><ul><li>US and EU Zones, replicated infrastructure </li></ul></ul>
  7. 7. 2010: Semantic Data Breaks Out <ul><li>People are starting to understand the potential </li></ul><ul><li>Three Major Challenges to Breakout </li></ul><ul><ul><li>Understanding: we’re moving along, but education curve remains </li></ul></ul><ul><ul><li>Implementation: “Great, but how do I do it?” </li></ul></ul><ul><ul><li>Measurement: “How well is this working?” </li></ul></ul>
  8. 8. 2010: Semantic Data Breaks Out <ul><li>People are starting to understand the potential </li></ul><ul><li>Three Major Challenges to Breakout </li></ul><ul><ul><li>Understanding: we’re moving along, but education curve remains </li></ul></ul><ul><ul><li>Implementation: “Great, but how do I do it?” </li></ul></ul><ul><ul><li>Measurement: “How well is this working?” </li></ul></ul><ul><li>OpenAmplify’s Strategy </li></ul><ul><ul><li>Continue to educate (community, webinars, conferences…) </li></ul></ul><ul><ul><li>Make it easy to use (simple API was first step) </li></ul></ul><ul><ul><li>Observe/measure/assess case studies to help develop success metrics </li></ul></ul><ul><ul><ul><li>ROI: the business view </li></ul></ul></ul><ul><ul><ul><li>Precision/Recall (very subjective): the scientific view </li></ul></ul></ul><ul><ul><ul><li>Community feedback (YOU are the benchmark): users’ view </li></ul></ul></ul>
  9. 9. Version 2.0 New Features <ul><li>PinPoint </li></ul><ul><ul><li>Scores topics based upon “engagement”: what is the text truly about? </li></ul></ul><ul><ul><li>A “better keyword” since it brings in sentiment, guidance, intent and more </li></ul></ul><ul><ul><li>Easy to implement for keyword-based applications: no changes, just better results </li></ul></ul><ul><ul><li>The first “SuperSignal”: combines other signals </li></ul></ul><ul><ul><li>Demo video: about 4 minutes </li></ul></ul>
  10. 10. Version 2.0 New Features <ul><li>Text-level Polarity, Guidance, Decisiveness and Temporality </li></ul><ul><ul><li>Another implementation aid especially for Social Media </li></ul></ul><ul><ul><li>A useful result from “That’s awesome. I think we should definitely do it. Now.” </li></ul></ul><ul><ul><ul><li>Has definite sentiment, but no topic </li></ul></ul></ul><ul><ul><ul><li>Definitely offers guidance, but about what? </li></ul></ul></ul><ul><ul><ul><li>Has definite intention, but no specific action </li></ul></ul></ul><ul><ul><ul><li>Has definite temporality, but related to what? </li></ul></ul></ul><ul><ul><li>“ Raises a flag”: something’s going on here. Perhaps it needs a further look. </li></ul></ul>
  11. 11. Version 2.0 New Features <ul><li>Text-level Polarity, Guidance, Decisiveness and Temporality </li></ul><ul><ul><li>Another implementation aid especially for Social Media </li></ul></ul><ul><ul><li>A useful result from “That’s awesome. I think we should definitely do it. Now.” </li></ul></ul><ul><ul><ul><li>Has definite sentiment, but no topic </li></ul></ul></ul><ul><ul><ul><li>Definitely offers guidance, but about what? </li></ul></ul></ul><ul><ul><ul><li>Has definite intention, but no specific action </li></ul></ul></ul><ul><ul><ul><li>Has definite temporality, but related to what? </li></ul></ul></ul><ul><ul><li>“ Raises a flag”: something’s going on here. Perhaps it needs a further look. </li></ul></ul><ul><ul><li>Helps Identify characteristics of the author </li></ul></ul><ul><ul><ul><li>A doer or a thinker? </li></ul></ul></ul><ul><ul><ul><li>A fan or a naysayer? </li></ul></ul></ul><ul><ul><ul><li>A leader or a follower? </li></ul></ul></ul><ul><ul><li>You’ll love this for analysis of Twitter, Facebook, etc. </li></ul></ul><ul><ul><ul><li>Short, “dirty” texts </li></ul></ul></ul><ul><ul><ul><li>Identify key threads even without knowing topic </li></ul></ul></ul><ul><ul><ul><li>See where the action is: “What do Twitter Users actually Do ?” </li></ul></ul></ul>
  12. 12. Version 2.0 New Features <ul><li>A New Signal: Contrast </li></ul><ul><ul><li>Specially requested by moderation/law enforcement users </li></ul></ul><ul><ul><li>Part of the Styles Analysis </li></ul></ul><ul><ul><li>Detects degree of disagreement in the text: none, some, lots. </li></ul></ul><ul><ul><li>Precursor to a more comprehensive “controversy” signal later on </li></ul></ul><ul><ul><li>Possible uses: </li></ul></ul><ul><ul><ul><li>Identify “hotspots” where debate is occurring </li></ul></ul></ul><ul><ul><ul><li>Raise a flag where things may be getting heated (combine with Flamboyance?) </li></ul></ul></ul><ul><ul><ul><li>Permit intervention in brand conversations, or in forums/social media venues </li></ul></ul></ul><ul><ul><li>Very new and will be steadily refined: your observations and input gratefully received :-) </li></ul></ul>
  13. 13. Version 2.0 New Features <ul><li>Named Entity Recognition </li></ul><ul><ul><li>The first step in something much bigger: co-reference </li></ul></ul><ul><ul><li>Identifies persons, organizations and locations </li></ul></ul><ul><ul><li>Subtypes also identified where possible: gender of person, type of organization, type of location </li></ul></ul><ul><ul><li>First cut is pretty good; will get steadily better. Let us know if you see a NE that we don’t nail </li></ul></ul><ul><ul><li>Let’s use NER to talk about the future… </li></ul></ul><Topic> <Name>Johnny</Name> <Value>7.000000</Value> </Topic> <NamedEntityType> <Result> <Name>Type</Name> <Value>Person</Value> </Result> <Result> <Name>SubType</Name> <Value>male</Value> </Result> </NamedEntityType>
  14. 14. Futures <ul><li>After NER…Co-reference </li></ul><ul><ul><li>Connects sentences and references more meaningfully </li></ul></ul><ul><ul><li>Connect “He said” to a prior male NE </li></ul></ul><ul><ul><li>Allow the statement “Federer is still the best” to add to polarity score of “Roger Federer” </li></ul></ul><ul><ul><li>Allow “I’m going to buy it” to create a TopicIntention for “car” mentioned earlier… </li></ul></ul><ul><ul><li>… and lots more. </li></ul></ul><ul><ul><li>All signals will be better with co-reference! </li></ul></ul><ul><ul><li>We’ll go after the high-certainty rules first; co-reference is hard </li></ul></ul><ul><ul><li>Get into the discussion on the forums </li></ul></ul>
  15. 15. Futures <ul><li>After NER…Co-reference </li></ul><ul><ul><li>Connects sentences and references more meaningfully </li></ul></ul><ul><ul><li>Connect “He said” to a prior male NE </li></ul></ul><ul><ul><li>Allow the statement “Federer is still the best” to add to polarity score of “Roger Federer” </li></ul></ul><ul><ul><li>Allow “I’m going to buy it” to create a TopicIntention for “car” mentioned earlier… </li></ul></ul><ul><ul><li>… and lots more. </li></ul></ul><ul><ul><li>All signals will be better with co-reference! </li></ul></ul><ul><ul><li>We’ll go after the high-certainty rules first; co-reference is hard </li></ul></ul><ul><li>In General </li></ul><ul><ul><li>Lots of Social Media Support </li></ul></ul><ul><ul><ul><li>Emoticon/slang handling </li></ul></ul></ul><ul><ul><ul><li>“ Dirty” text handling </li></ul></ul></ul><ul><ul><ul><li>Identification of fans, detractors, influencers, intenders, etc. </li></ul></ul></ul><ul><ul><li>More useful constructs that are easy to implement, like PinPoint </li></ul></ul>
  16. 16. Futures: a Hint <ul><li>Between Us: Something Big is Coming around Taxonomy </li></ul><ul><ul><li>We all see the universe differently: my “bat” flies through the air, yours hits a ball </li></ul></ul><ul><ul><li>We’re both right… </li></ul></ul><ul><ul><li>You need a means of applying your view of the universe to your amp analyses </li></ul></ul><ul><ul><li>You’ll need tools to help you to codify that view </li></ul></ul><ul><ul><li>Coming soon: Ampliverse . Stay tuned ;-) </li></ul></ul>
  17. 17. Time for Your Questions <ul><li>Dave will read, Mike will (try to) answer </li></ul><ul><li>We’ll select questions that reflect broadest interest </li></ul><ul><li>If you don’t hear your question answered, let us know afterwards and we’ll follow up </li></ul>
  18. 18. Final Thoughts <ul><li>We value your participation and ideas </li></ul><ul><li>We’d like to say “thanks”…please send an email to [email_address] with the word “OAWebinar ” in the subject line and your API key in the body, and we’ll bump you up to 5K/day </li></ul><ul><li>This is only for those who attended today, so please don’t pass it on ;-) </li></ul><ul><li>We want to help you build apps using OpenAmplify, so keep us in the loop via the forums </li></ul><ul><li>Cool apps are welcomed in our Showcase…and we’ll help you get the word out about them too </li></ul><ul><li>See you in the Community! </li></ul>
  19. 19. Thanks for Joining Us! <ul><li>http://community.openamplify.com </li></ul>

×