Why Your Next Product Should be Semantic by Dr. David Wood

682 views

Published on

David Wood, co-founder & CTO of 3 Round Stones, author & pioneer on Data Exchange Standards for the Web speaks at the 10th Anniversary Semantic Technology & Business Conference in San Jose California on 20-August 2014. Dr. Wood will describe how data is core to your organization's effectiveness and efficiency. He'll describe why and how to make your next product semantically-enhanced for increased speed to market & responsiveness to your customers.

Published in: Internet
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
682
On SlideShare
0
From Embeds
0
Number of Embeds
85
Actions
Shares
0
Downloads
5
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Why Your Next Product Should be Semantic by Dr. David Wood

  1. 1. @prototypo david@3RoundStones.com David Wood, PhD Why Your Next Product Should Be Semantic
  2. 2. Critical Business Benefits • Better speed to market • Lower running costs • Increased market opportunities
  3. 3. M A N N I N G David Wood Marsha Zaidman Luke Ruth WITH Michael Hausenblas FOREWORD BY Tim Berners-Lee Structured data on the Web 2 D oorPrizes
  4. 4. YouTube HDTV watch videos watch Better videos Publish videos Share videos Rate videos Discuss videos
  5. 5. Linked Data RDBMS Use data Use data Publish data Share data Rate data Discuss data
  6. 6. Data is easier and faster to change than code
  7. 7. “(Software development) cost estimation literally boils down to "how long and how many people?"” -- Philippe Kruchten
  8. 8. 0 10 20 30 40 50 60 70 Retail Bars BuildingFood ServiceAccountingSoftw are (trad)Legal/TaxH ealthcareEducation C hildcare Softw are (rem ote) SHRM 2008US Census 2007 Survey 2014 Payroll,%ofTotal
  9. 9. 0 10 20 30 40 50 60 70 Retail Bars BuildingFood ServiceAccountingSoftw are (trad)Legal/TaxH ealthcareEducation C hildcare Softw are (rem ote) SHRM 2008US Census 2007 Survey 2014 Payroll,%ofTotal
  10. 10. “Computer Science is the only discipline in which we view adding a new wing to a building as being maintenance.” -- Jim Horning
  11. 11. class Language < ActiveRecord::Base ! has_many :examinations has_many :project_languages has_many :projects, :through => :project_languages ! attr_accessible :source, :target, :price ! validates :source, :target, :price, :presence => true ! def self.source_languages Language.find_by_sql("select * from languages group by source").map{| lang| [lang.source, lang.source] } end ! def self.target_languages Language.select(:target).uniq.map{|lang| [lang.target, lang.target]} end ! end SQ L em bedded in code
  12. 12. class Language < ActiveRecord::Base ! has_many :examinations has_many :project_languages has_many :projects, :through => :project_languages ! attr_accessible :source, :target, :price ! validates :source, :target, :price, :presence => true ! def self.source_languages Language.find_by_sql("select * from languages group by source").map{| lang| [lang.source, lang.source] } end ! def self.target_languages Language.select(:target).uniq.map{|lang| [lang.target, lang.target]} end ! end SQ L em bedded in code SQL
  13. 13. SQ L generators client = Client.find(1, 10) equivalent to: SELECT * FROM clients WHERE (clients.id IN (1,10))
  14. 14. SQ L generators client = Client.find(1, 10) equivalent to: SELECT * FROM clients WHERE (clients.id IN (1,10)) SQL! generator
  15. 15. SQ L generators client = Client.find(1, 10) equivalent to: SELECT * FROM clients WHERE (clients.id IN (1,10)) SQL! generator That’s good, right?
  16. 16. SQ L generators class Amenity < ActiveRecord::Base has_many :amenity_lists ! named_scope :available, lambda { |start_date, end_date| { :select => 'amenities.*', :order => 'id', :conditions => [" amenities.id NOT IN (! SELECT aa.id from amenities aa, amenity_lists al WHERE! amenities.id = al.amenity_id AND! (! (? BETWEEN al.checkin AND al.checkout) OR! (? BETWEEN al.checkin AND al.checkout)! )! )", start_date, end_date ] } }
  17. 17. Why?
  18. 18. Why? • It is the tight coupling of DB+schema that causes tight code integration.
  19. 19. Back to the future q = """SELECT ?x ?z ?y! WHERE {! course:%s course:termName ?x;! ?s ?t.! ?s ?d ?z.! ?t course:termName ?y.! FILTER (regex(?z,'[^a-z0-9]','i') && isLiteral(?z) )! }ORDER BY ASC(?s) """%var_value schema ontology inference schema SPARQL
  20. 20. “Perfection is achieved, not when there is nothing left to add, but when there is nothing left to remove.” -- Antoine de Saint-Exupéry
  21. 21. N ext schema ontology Application relationships Data structure
  22. 22. N ext schema ontology
  23. 23. N ext inference schema ontology
  24. 24. N ext inference schema ontology SPARQL! generator
  25. 25. N ext generic code inference schema ontology SPARQL! generator
  26. 26. SQL SQL 1960s 1970s 1980s 1990s 2000s 2010s SQL! generator schema ontology inference schema SPARQL SPARQL! generator schema ontology inference generic code inference schema ontology
  27. 27. Bonobos!
  28. 28. Bonobos!
  29. 29. Animal Pants Label Label Comment Comment Depiction Depiction Order page Color Gender pronoun Address
  30. 30. Label Comment Depiction Depiction Label Comment Gender pronoun Address Color Order page
  31. 31. Lack of Context
  32. 32. Required Context
  33. 33. carrelet@fr plaice@en_gb sand dab@en_us lemon dab@en_us lemon sole@en_us
  34. 34. carrelet@fr plaice@en_gb sand dab@en_us lemon dab@en_us lemon sole@en_us limande@fr calimande@fr plie@fr
  35. 35. Dr. Chris Welty “Semantic Technology is not an end in itself, it is a means to an end, a set of tools and techniques for supporting modern data analytics. It goes alongside other essential technologies like machine learning, databases, information retrieval, etc.” IBM Watson Team
  36. 36. M A N N I N G David Wood Marsha Zaidman Luke Ruth WITH Michael Hausenblas FOREWORD BY Tim Berners-Lee Structured data on the Web 2 D oorPrizes
  37. 37. @prototypo david@3RoundStones.com David Wood, PhD Why Your Next Product Should Be Semantic
  38. 38. This work is Copyright © 2011 3 Round Stones Inc. It is licensed under the Creative Commons Attribution 3.0 Unported License
 Full details at: http://creativecommons.org/licenses/by/3.0/ You are free: to Share — to copy, distribute and transmit the work to Remix — to adapt the work Under the following conditions: Attribution. You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.

×