principles for knowledge engineering on the web
DESCRIPTION
Keynote ICK3 conference, Paris, 2011TRANSCRIPT
![Page 1: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/1.jpg)
Principles for knowledge engineering on the Web
Guus Schreiber
VU University Amsterdam
Computer Science, Web & Media
![Page 2: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/2.jpg)
Overview of this talk
• Semantic Web: the digital heritage case
• Knowledge-engineering principles
• Challenges for Web KE
![Page 3: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/3.jpg)
My journeyknowledge engineering
• design patterns for problem solving
• methodology for knowledge systems
• models of domain knowledge
• ontology engineering
![Page 4: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/4.jpg)
My journeyaccess to digital heritage
![Page 5: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/5.jpg)
My journeyWeb standards
• Web metadata: RDF
• OWL Web Ontology Language
• SKOS model for publishing vocabularies on the Web
![Page 6: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/6.jpg)
SEMANTIC WEB: THE DIGITAL-HERITAGE CASE
![Page 7: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/7.jpg)
The Web: resources and links
URL URL
Web link
![Page 8: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/8.jpg)
The Semantic Web: typed resources and links
URL URL
Web link
ULAN
Henri Matisse
Dublin Core
creator
Painting“Woman with hat”SFMOMA
![Page 9: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/9.jpg)
![Page 10: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/10.jpg)
![Page 11: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/11.jpg)
Vocabulary interoperability: SKOS
![Page 12: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/12.jpg)
Vocabulary representations
• SKOS has been a major success
• Easy to understand and create
• LCSH publication set important example
![Page 13: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/13.jpg)
![Page 14: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/14.jpg)
The myth of a unified vocabulary
• In large virtual collections there are always multiple vocabularies – In multiple languages
• Every vocabulary has its own perspective– You can’t just merge them
• But you can use vocabularies jointly by defining a limited set of links– “Vocabulary alignment”
• It is surprising what you can do with just a few links
![Page 15: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/15.jpg)
Example use of vocabulary alignment
“Tokugawa”
SVCN period Edo
SVCN is local in-house ethnology thesaurus
AAT style/period Edo (Japanese period) Tokugawa
AAT is Getty’s Art & Architecture Thesaurus
![Page 16: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/16.jpg)
![Page 17: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/17.jpg)
Enriching metadata with concepts
![Page 18: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/18.jpg)
Learning vocabulary alignments
• Example: learning relations between art styles and artists through NLP of art historic texts– “Who are Impressionist painters?”
![Page 19: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/19.jpg)
Semantic search: result clustering based on retrieval path
![Page 20: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/20.jpg)
Research issues
• Information retrieval as graph search– more semantics => more paths– finding optimal graph patterns
• Vocabulary alignment
• Information extraction– recognizing people, locations, …– identity resolution
• Multi-lingual resources
![Page 21: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/21.jpg)
Personalized Rijksmuseum
• Interactive user modeling
•Recommendations of artworks and art topics
![Page 22: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/22.jpg)
Mobile museum tour
![Page 23: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/23.jpg)
KNOWLEDGE ENGINEERING PRINCIPLES
Lessons I learned
![Page 24: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/24.jpg)
Principle 1: Be modest!
• Ontology engineers should refrain from developing their own idiosyncratic ontologies
• Instead, they should make the available rich vocabularies, thesauri and databases available in an interoperable (web) format
• Initially, only add the originally intended semantics
![Page 25: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/25.jpg)
Principle 2: Think large!
"Once you have a truly massive amount of information integrated as knowledge, then the human-software system will be superhuman, in the same sense that mankind with writing is superhuman compared to mankind before writing."
Doug Lenat
![Page 26: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/26.jpg)
Principle 3: Develop and use patterns!
• Don’t try to be (too) creative
• Ontology engineering should not be an art but a discipline
• Patterns play a key role in methodology for ontology engineering
• See for example patterns developed by the W3C Semantic Web Best Practices group
http://www.w3.org/2001/sw/BestPractices/
• SKOS can also be considered a pattern
![Page 27: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/27.jpg)
Principle 4: Don’t recreate, but enrich and align
• Techniques:– Learning ontology relations/mappings– Semantic analysis, e.g. OntoClean– Processing of scope notes in thesauri
![Page 28: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/28.jpg)
Principle 5: Beware of ontologicalover-commitment!
![Page 29: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/29.jpg)
Principle 6: writing in an ontology language doesn’t make it an ontology!
• Ontology is vehicle for sharing
• Papers about your own idiosyncratic “university ontology” should be rejected at conferences
• The quality of an ontology does not depend on the number of, for example, OWL constructs used
![Page 30: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/30.jpg)
Principle 7: Required level of formal semantics depends on the domain!
• In our semantic search we use three OWL constructs:– owl:sameAs, owl:TransitiveProperty,
owl:SymmetricProperty
• But cultural heritage has is very different from medicine and bioinformatics– Don’t over-generalize on requirements for
e.g. OWL
![Page 31: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/31.jpg)
CHALLENGES FOR WEB KE
![Page 32: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/32.jpg)
Challenge: Linked Open Data
![Page 33: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/33.jpg)
Availability of government data: http://data.gov.uk
![Page 34: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/34.jpg)
The fight for “standard” semantics Schema.org
![Page 35: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/35.jpg)
Challenge: vocabulary alignment methodology
• Multitude of alignment techniques available– Direct syntactic match– Lexical manipulation– Structured, ….
• Precision & recall varies
• Large evaluation initiative– OAEI http://oaei.ontologymatching.org/
![Page 36: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/36.jpg)
Limitations of categorical thinking
• The set theory on which ontology languages are built is inadequate for modelling how people think about categories (Lakoff)– Category boundaries are not hard: cf. art styles– People think of prototypes; some examples are
very prototypical, others less
• We also need to make meta-distinctions explicit– organizing class: “furniture”– base-level class: “chair”– domain-specific: “Windsor chair”
![Page 37: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/37.jpg)
Challenge: new types of search exploiting semantics
![Page 38: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/38.jpg)
Relation search: Picasso, Matisse & Braque
![Page 39: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/39.jpg)
Challenge: combining professional annotations with public “tags”
![Page 40: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/40.jpg)
![Page 41: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/41.jpg)
Challenge: data trust issues
• How can a museum trust annotations of outsiders?
• Need to adapt techniques from closed world to open world
• Ongoing case studies study reputation assessment, use of probability theories, ….
![Page 42: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/42.jpg)
Challenge: event-centred approach => people like narratives
![Page 43: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/43.jpg)
Extracting piracy eventsfrom piracy reports & Web sources
![Page 44: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/44.jpg)
Visualising piracy events
![Page 45: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/45.jpg)
Large-scale experimentation!
![Page 46: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/46.jpg)
TOWARDS WEB SCIENCE
![Page 47: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/47.jpg)
We need to study the Web as a phenomenon
• Web dynamics• Collective intelligence• Privacy, trust and
security• Linked open data• Universal access
![Page 48: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/48.jpg)
Web for Social
Development
48
![Page 49: Principles for knowledge engineering on the Web](https://reader038.vdocuments.net/reader038/viewer/2022103110/547a9b61b4af9ff31b8b45d3/html5/thumbnails/49.jpg)
Acknowledgements
• Long list of people
• Projects: MIA, MultiemdiaN E-Culture, CHOICE, MunCH, CHIP, Agora, PrestoPrime, NoTube, EuropeanaConnect, Poseidon