Muutke küpsiste eelistusi

Semantic Modeling for Data: Avoiding Pitfalls and Breaking Dilemmas [Pehme köide]

  • Formaat: Paperback / softback, 306 pages, kõrgus x laius: 233x178 mm
  • Ilmumisaeg: 04-Sep-2020
  • Kirjastus: O'Reilly Media
  • ISBN-10: 1492054275
  • ISBN-13: 9781492054276
  • Pehme köide
  • Hind: 84,99 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Tavahind: 99,99 €
  • Säästad 15%
  • Raamatu kohalejõudmiseks kirjastusest kulub orienteeruvalt 2-4 nädalat
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Tellimisaeg 2-4 nädalat
  • Lisa soovinimekirja
  • Formaat: Paperback / softback, 306 pages, kõrgus x laius: 233x178 mm
  • Ilmumisaeg: 04-Sep-2020
  • Kirjastus: O'Reilly Media
  • ISBN-10: 1492054275
  • ISBN-13: 9781492054276

What value does semantic data modeling offer? As an information architect or data science professional, let&;s say you have an abundance of the right data and the technology to extract business gold&;but you still fail. The reason? Bad data semantics.

In this practical and comprehensive field guide, author Panos Alexopoulos takes you on an eye-opening journey through semantic data modeling as applied in the real world. You&;ll learn how to master this craft to increase the usability and value of your data and applications. You&;ll also explore the pitfalls to avoid and dilemmas to overcome for building high-quality and valuable semantic representations of data.

  • Understand the fundamental concepts, phenomena, and processes related to semantic data modeling
  • Examine the quirks and challenges of semantic data modeling and learn how to effectively leverage the available frameworks and tools
  • Avoid mistakes and bad practices that can undermine your efforts to create good data models
  • Learn about model development dilemmas, including representation, expressiveness and content, development, and governance
  • Organize and execute semantic data initiatives in your organization, tackling technical, strategic, and organizational challenges
Preface xi
Part I The Basics
1 Mind The Semantic Gap
3(10)
What Is Semantic Data Modeling?
4(3)
Why Develop and Use a Semantic Data Model?
7(1)
Bad Semantic Modeling
8(2)
Avoiding Pitfalls
10(1)
Breaking Dilemmas
11(2)
2 Semantic Modeling Elements
13(22)
General Elements
14(9)
Entities
14(2)
Relations
16(1)
Classes and Individuals
17(2)
Attributes
19(2)
Complex Axioms, Constraints, and Rules
21(1)
Terms
22(1)
Common and Standardized Elements
23(9)
Lexicalization and Synonymy
24(1)
Instantiation
25(1)
Meaning Inclusion and Class/Relation Subsumption
26(1)
Part-Whole Relation
26(2)
Semantic Relatedness
28(1)
Mapping and Interlinking Relations
28(1)
Documentation Elements
29(3)
Summary
32(3)
3 Semantic And Linguistic Phenomena
35(14)
Ambiguity
35(2)
Uncertainty
37(1)
Vagueness
38(3)
Rigidity, Identity, Unity, and Dependence
41(1)
Symmetry, Inversion, and Transitivity
42(1)
Closed- and Open-World Assumptions
43(1)
Semantic Change
43(3)
Summary
46(3)
4 Semantic Model Quality
49(14)
Semantic Accuracy
50(2)
Completeness
52(2)
Consistency
54(1)
Conciseness
55(2)
Timeliness
57(1)
Relevancy
57(1)
Understandability
58(1)
Trustworthiness
59(1)
Availability, Versatility, and Performance
60(1)
Summary
61(2)
5 Semantic Model Development
63(24)
Development Activities
63(8)
Setting the Stage
64(3)
Deciding What to Build
67(1)
Building It
68(1)
Ensuring It's Good
69(1)
Making It Useful
69(1)
Making It Last
70(1)
Vocabularies, Patterns, and Exemplary Models
71(5)
Upper Ontologies
71(1)
Design Patterns
72(2)
Standard and Reference Models
74(1)
Public Models and Datasets
74(2)
Semantic Model Mining
76(8)
Mining Tasks
76(3)
Mining Methods and Techniques
79(5)
Summary
84(3)
Part II The Pitfalls
6 Bad Descriptions
87(22)
Giving Bad Names
87(5)
Setting a Bad Example
89(1)
Why We Give Bad Names
90(1)
Pushing for Clarity
91(1)
Omitting Definitions or Giving Bad Ones
92(5)
When You Need Definitions
93(1)
Why We Omit Definitions
94(1)
Good and Bad Definitions
95(1)
How to Get Definitions
96(1)
Ignoring Vagueness
97(10)
Vagueness Is a Feature, Not a Bug
99(1)
Detecting and Describing Vagueness
100(7)
Not Documenting Biases and Assumptions
107(1)
Keeping Your Enemies Close
107(1)
Summary
108(1)
7 Bad Semantics
109(16)
Bad Identity
109(6)
Bad Synonymy
110(3)
Bad Mapping and Interlinking
113(2)
Bad Subclasses
115(4)
Instantiation as Subclassing
115(2)
Parts as Subclasses
117(1)
Rigid Classes as Subclasses of Nonrigid Classes
118(1)
Common Superclasses with Incompatible Identity Criteria
119(1)
Bad Axioms and Rules
119(4)
Defining Hierarchical Relations as Transitive
119(2)
Defining Vague Relations as Transitive
121(1)
Complementary Vague Classes
121(1)
Mistaking Inference Rules for Constraints
122(1)
Summary
123(2)
8 Bad Model Specification And Knowledge Acquisition
125(30)
Building the Wrong Thing
125(8)
Why We Get Bad Specifications
126(2)
How to Get the Right Specifications
128(5)
Bad Knowledge Acquisition
133(13)
Wrong Knowledge Sources
134(6)
Wrong Acquisition Methods and Tools
140(6)
A Specification and Knowledge Acquisition Story
146(7)
Model Specification and Design
146(3)
Model Population
149(4)
Summary
153(2)
9 Bad Quality Management
155(14)
Not Treating Quality as a Set of Trade-Offs
155(3)
Semantic Accuracy Versus Completeness
156(1)
Conciseness Versus Completeness
156(1)
Conciseness Versus Understandability
157(1)
Relevancy to Context A Versus Relevancy to Context B
157(1)
Not Linking Quality to Risks and Benefits
158(2)
Not Using the Right Metrics
160(7)
Using Metrics with Misleading Interpretations
160(2)
Using Metrics with Little Comparative Value
162(1)
Using Metrics with Arbitrary Value Thresholds
162(2)
Using Metrics That Are Actually Quality Signals
164(1)
Measuring Accuracy of Vague Assertions in a Crisp Way
165(1)
Equating Model Quality with Information Extraction Quality
166(1)
Summary
167(2)
10 Bad Application
169(20)
Bad Entity Resolution
169(12)
How Entity Resolution Systems Use Semantic Models
170(1)
When Knowledge Can Hurt You
171(1)
How to Select Disambiguation-Useful Knowledge
172(6)
Two Entity Resolution Stories
178(3)
Bad Semantic Relatedness
181(6)
Why Semantic Relatedness Is Tricky
182(1)
How to Get the Semantic Relatedness You Really Need
183(1)
A Semantic Relatedness Story
184(3)
Summary
187(2)
11 Bad Strategy And Organization
189(16)
Bad Strategy
189(7)
What Is a Semantic Model Strategy About?
190(2)
Buying into Myths and Half-Truths
192(1)
Underestimating Complexity and Cost
193(2)
Not Knowing or Applying Your Context
195(1)
Bad Organization
196(6)
Not Building the Right Team
196(4)
Underestimating the Need for Governance
200(2)
Summary
202(3)
Part III The Dilemmas
12 Representation Dilemmas
205(22)
Class or Individual?
205(3)
To Subclass or Not to Subclass?
208(3)
Attribute or Relation?
211(1)
To Fuzzify or Not to Fuzzify?
212(13)
What Fuzzification Involves
212(8)
When to Fuzzify
220(2)
Two Fuzzification Stories
222(3)
Summary
225(2)
13 Expressiveness And Content Dilemmas
227(16)
What Lexicalizations to Have?
227(4)
How Granular to Be?
231(2)
How General to Be?
233(2)
How Negative to Be?
235(2)
How Many Truths to Handle?
237(1)
How Interlinked to Be?
238(3)
Summary
241(2)
14 Evolution And Governance Dilemmas
243(18)
Model Evolution
243(12)
Remember or Forget?
244(1)
Run or Pace?
244(2)
React or Prevent?
246(3)
Knowing and Acting on Your Semantic Drift
249(6)
Model Governance
255(3)
Democracy, Oligarchy, or Dictatorship?
255(2)
A Centralization Story
257(1)
Summary
258(3)
15 Looking Ahead
261(8)
The Map Is Not the Territory
261(1)
Being an Optimist, but Not Naive
262(1)
Avoiding Tunnel Vision
263(1)
Avoiding Distracting Debates
263(3)
Semantic Versus Nonsemantic Frameworks
263(2)
Symbolic Knowledge Representation Versus Machine Learning
265(1)
Doing No Harm
266(1)
Bridging the Semantic Gap
267(2)
Bibliography 269(22)
Glossary 291(4)
Index 295
Panos Alexopoulos has been working since 2006 at the intersection of data, semantics and software, contributing in building intelligent systems that deliver value to business and society. Born and raised in Athens, Greece, he currently works as Head of Ontology at Textkernel BV, in Amsterdam, Netherlands, leading a team of data professionals in developing and delivering a large cross-lingual Knowledge Graph in the HR and Recruitment domain.

Panos has published several papers at international conferences, journals and books, and he is a regular speaker and trainer in both academic and industry venues, striving to bridge the gap between academia and industry so that they can benefit from each other.