Why Your Next Product Should be Semantic by Dr. David Wood
1 like845 views
The document discusses the critical business benefits of semantic technology, emphasizing improved speed to market, lower operational costs, and greater market opportunities. It highlights how structured data and linked data contribute to better data management and integration. The text also mentions that semantic technology serves as a catalyst for advanced data analytics in conjunction with other technologies like machine learning and databases.
![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](https://image.slidesharecdn.com/whyyournextproductshouldbesemanticbydavidwoodfrom3roundstones-140820135429-phpapp01/85/Why-Your-Next-Product-Should-be-Semantic-by-Dr-David-Wood-14-320.jpg)
![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](https://image.slidesharecdn.com/whyyournextproductshouldbesemanticbydavidwoodfrom3roundstones-140820135429-phpapp01/85/Why-Your-Next-Product-Should-be-Semantic-by-Dr-David-Wood-15-320.jpg)
![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
]
}
}](https://image.slidesharecdn.com/whyyournextproductshouldbesemanticbydavidwoodfrom3roundstones-140820135429-phpapp01/85/Why-Your-Next-Product-Should-be-Semantic-by-Dr-David-Wood-19-320.jpg)
![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](https://image.slidesharecdn.com/whyyournextproductshouldbesemanticbydavidwoodfrom3roundstones-140820135429-phpapp01/85/Why-Your-Next-Product-Should-be-Semantic-by-Dr-David-Wood-22-320.jpg)
Why Your Next Product Should be Semantic by Dr. David Wood
- 1. @prototypo [email protected] David Wood, PhD Why Your Next Product Should Be Semantic
- 2. Critical Business Benefits • Better speed to market • Lower running costs • Increased market opportunities
- 4. 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
- 5. YouTube HDTV watch videos watch Better videos Publish videos Share videos Rate videos Discuss videos
- 6. Linked Data RDBMS Use data Use data Publish data Share data Rate data Discuss data
- 7. Data is easier and faster to change than code
- 8. “(Software development) cost estimation literally boils down to "how long and how many people?"” -- Philippe Kruchten
- 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. 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
- 13. “Computer Science is the only discipline in which we view adding a new wing to a building as being maintenance.” -- Jim Horning
- 14. 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
- 15. 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
- 16. SQ L generators client = Client.find(1, 10) equivalent to: SELECT * FROM clients WHERE (clients.id IN (1,10))
- 17. SQ L generators client = Client.find(1, 10) equivalent to: SELECT * FROM clients WHERE (clients.id IN (1,10)) SQL! generator
- 18. 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?
- 19. 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 ] } }
- 20. Why?
- 21. Why? • It is the tight coupling of DB+schema that causes tight code integration.
- 22. 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
- 23. “Perfection is achieved, not when there is nothing left to add, but when there is nothing left to remove.” -- Antoine de Saint-Exupéry
- 30. Bonobos!
- 31. Bonobos!
- 33. Animal Pants Label Label Comment Comment Depiction Depiction Order page Color Gender pronoun Address
- 35. Lack of Context
- 36. Required Context
- 39. carrelet@fr plaice@en_gb sand dab@en_us lemon dab@en_us lemon sole@en_us
- 40. carrelet@fr plaice@en_gb sand dab@en_us lemon dab@en_us lemon sole@en_us limande@fr calimande@fr plie@fr
- 41. 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
- 43. 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
- 44. @prototypo [email protected] David Wood, PhD Why Your Next Product Should Be Semantic
- 45. 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.