the provenance of madame bonnier: museum linked data
TRANSCRIPT
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Robert Sanderson
The Provenance of Madame Bonnier:Museum Linked Data
With Thanks To:
Ruth CuadraBrenda PodemskiDavid Newbury
Kelly DavisJoan Cobb
Vladimir Alexiev…
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance • Case Study: Madame Bonnier
• Data Models: Integration of Object and Provenance• Lessons Learnt• Data Ownership vs Stewardship• Data Quality• Model Alignment• Structure or Interaction?
Overview
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance Portrait of Madame Bonnier de
la Mosson as DianaPaintingJean-Marc Nattier (1685 – 1766)France, 1742Oil on Canvas129.5 x 96.8 cm77.PA.87Getty MuseumOn View: South Pavilion, S202
Madame Bonnier
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Madame Bonnier: Provenance
Museum Provenance Index
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Madame Bonnier: Provenance?
Provenance Index Provenance Index
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
anceEveryone As
Diana At Some Point
Ran out of red paint?
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance Portrait of Madame Bonnier de
la Mosson as DianaPaintingJean-Marc Nattier (1685 – 1766)France, 1742Oil on Canvas129.5 x 96.8 cm77.PA.87Getty MuseumOn View: South Pavilion, S202
Madame Bonnier
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Object Data Model: Complete
Start of Provenance
Current Provenance
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Data Ownership vs StewardshipProvenance Index makes assertions about others’
objects (including Museum)
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Data Ownership vs StewardshipProvenance Index makes assertions about others’
objects (including Museum)
Authoritative about the documents … … but not about the objects’ provenance
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Data Ownership vs StewardshipProvenance Index makes assertions about others’
objects (including Museum)
Authoritative about the documents … … but not about the objects’ provenance
=> Acting as a steward for the provenance, not the owner of it
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
anceData Quality
Linked Data makes errors easier to find … … but doesn’t correct them for you
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
anceData Quality
Linked Data makes errors easier to find … … but doesn’t correct them for you
Quality of LOD is limited by quality of non LOD input, for purpose of linking
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
anceData Quality
Linked Data makes errors easier to find … … but doesn’t correct them for you
Quality of LOD is limited by quality of non LOD input, for purpose of linking
Beware false precision=> Automatic inferencing is risky
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Model AlignmentAligning models is hard, while avoiding false
precision!
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Model AlignmentAligning models is hard, while avoiding false
precision!
Need to get over “need” for 100% precision, 100% coverage, 100% completeness
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Model AlignmentAligning models is hard, while avoiding false
precision!
Need to get over “need” for 100% precision, 100% coverage, 100% completeness
=> Start somewhere, then implement, learn, correct, and iterate
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Structure or InteractionLinked Data as a Data Model … provides single structure to implement, query … acceptable if complete and accurate
Linked Data as an API … provides data to integrate, use … acceptable if understandable and usable
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
Structure or InteractionLinked Data as a Data Model … provides single structure to implement, query … acceptable if complete and accurate
Linked Data as an API … provides data to integrate, use … acceptable if understandable and usable
=> As completeness increases, usability decreases
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
ance
If it’s not usable, why are we doing it?
@azaroth42
LOD
Less
ons L
earn
t: Pr
oven
anceFinal Thoughts
Need to focus on our goals … not on religious wars around ontologies
Need to find the balance between accuracy and usability
Need to recognize this is HARD and we’re not going to get it right the first time. Or the second.
Need to keep on keeping on :)