ontology and
TRANSCRIPT
•
•
•
•
•
•
•
•
•
•
•
Pump: “A mechanical device for raising, compressing,
or transferring fluids”
Engine: “a machine that turns energy into
mechanical motion”
Mechanical Device: “a physical device with parts that
move relative to each other”
Page 5
Hydraulic Pump
Aircraft Engine Driven Pump
Pump
Mechanical Device
Engine
Jet EngineFuel Pump
= Generalization
•
•
•
Page 6
Hydraulic System
Fuel System
Pumping
Hydraulic Pump
Aircraft Engine Driven Pump
Pump
Mechanical Device
Engine
Jet EngineFuel Pump
Fuel Filter
= Broader Term
= Related Term
•
•
•
•
Hydraulic System
Fuel System
Pumping
Hydraulic Pump
Aircraft Engine Driven Pump
Pump
Mechanical Device
Engine
Jet EngineFuel Pump
Fuel Filter
has-part
done-by
part-of connected-to
supplies-fuel-to
Ontology: Strict Taxonomy + Formal Relationships
= Generalization
= Other
Relationships
•
•
•
•
Page 8
•
•
•
•
•
•
•
•
•
•
•
•
•
•
URIs: globally unique identifiers
Data
Metadata
•Existing Data Schema hard to understand contain wide variety of non-core information
hard to use and evolve(poor flexibility)
hard to integrate
•How to Proceeddistill the essential elementsdon’t look at the data model focus on the real world, not the application world
learn the subject matter, talk to the experts
Power productsCompany A
(relational)
Power productsCompany B
(relational)
?Data schema Data schema
A Case Study in Database Integration
Power productsCompany A
(relational)
Power productsCompany B
(relational)
A Case Study in Database Integration
?
Power products
(triple store)
Ontology
Data schema Data schema
Power productsIntegrated
•
•
•
•
A Case Study in Database Integration
AllegroGraph
Database ……..
Ontology as data schemaLoaded with the data.
Protege
Build ontology
Ontology (text file)
Other sources:Web pages, XML, Social media, Text documents,
spreadsheets
RDBUltrawrap
R2RMLMapping
AllegroGraph
Database ……..
User Interface
SPARQL Queries Results
Program Logic
User input
Dynamic UI
•
•
•
•
•
(rinse & repeat)
•
•
•
•
Communicating to Developers
<Customer>{
rdf:type (mns:Customer)
, mns:hasAddress @<Address>*
, mns:hasLifeTimeSales xsd:float
}
• Customer, in the ontology will have any number of
relationships and attributes.
• Customer in the application, only needs an Address and a
floating point number for lifetime sales.
• Informs developers about what is in the Triple Store
• Basis for integrity checking (can be automated)
Cardinality0 or more, 1 or more, exactly 1, etc
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
••
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
