Top Banner
How to De-engineer a How to De-engineer a Semantic Web: Semantic Web: Some thoughts on Linking Some thoughts on Linking Archaeological Data Archaeological Data Leif Isaksen, Graeme Earl & Kirk Martinez Leif Isaksen, Graeme Earl & Kirk Martinez University of Southampton University of Southampton
26

How to De-engineer a Semantic Web:

Jan 13, 2016

Download

Documents

sanaa

How to De-engineer a Semantic Web:. Some thoughts on Linking Archaeological Data. Leif Isaksen, Graeme Earl & Kirk Martinez University of Southampton. The Problem. Summary data. Fragments of Meaning. Instance data. Type. Relationship. Mixing Models. Type. Relationship. Mixing Models. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: How to De-engineer a Semantic Web:

How to De-engineer a How to De-engineer a Semantic Web:Semantic Web:Some thoughts on Linking Archaeological Some thoughts on Linking Archaeological DataData

Leif Isaksen, Graeme Earl & Kirk MartinezLeif Isaksen, Graeme Earl & Kirk MartinezUniversity of SouthamptonUniversity of Southampton

Page 2: How to De-engineer a Semantic Web:

The ProblemThe Problem

Page 3: How to De-engineer a Semantic Web:

Summary dataSummary data

Page 4: How to De-engineer a Semantic Web:

Fragments of MeaningFragments of Meaning

Page 5: How to De-engineer a Semantic Web:

Instance dataInstance data

Page 6: How to De-engineer a Semantic Web:

Mixing ModelsMixing Models

ContextContext FindFind Quantity Quantity (weight)(weight)

1717 Dressel 2-4 Dressel 2-4 CatalanCatalan 400400

1818 Dressel 2-4 Dressel 2-4 EgyptianEgyptian 150150

cont.cont. findsfinds no.no. dimdim..

reg.?reg.?

Floor Floor AA

Egyptian Egyptian amph.amph. 33 rimsrims yesyes

Floor Floor BB

Cat.Cat. 11 vol.vol. nono

TypeType

RelationshipRelationship

Page 7: How to De-engineer a Semantic Web:

Mixing ModelsMixing Models

-- -- --

abab blah-de-blahblah-de-blah xyzxyz

cdcd da-de-dada-de-da uvwuvw

-- -- -- -- --

dfgdfsdfgdfs Tum-Te-TumTum-Te-Tum ii bishbish 11

ukuikukuik Tiddly-PomTiddly-Pom jjbosboshh

00

TypeType

RelationshipRelationship

Page 8: How to De-engineer a Semantic Web:

The representation The representation is not the data!is not the data!

Page 9: How to De-engineer a Semantic Web:

ApproachesApproaches

Page 10: How to De-engineer a Semantic Web:

TRANSLATIONTRANSLATION(TRansparent Negotiation and Sharing of Local Application Terminologies, (TRansparent Negotiation and Sharing of Local Application Terminologies, Instances and ONtologies)Instances and ONtologies)

Peer-to-peerPeer-to-peerServer frameworkServer framework

Page 11: How to De-engineer a Semantic Web:

Problems with the Problems with the TRANSLATION approachTRANSLATION approach

ClosedClosed

An engineers-eye viewAn engineers-eye view

‘‘Internet thinking’ not ‘web thinking’Internet thinking’ not ‘web thinking’

The network effect is created by Web 2.0 not The network effect is created by Web 2.0 not Internet 2.0!Internet 2.0!

Page 12: How to De-engineer a Semantic Web:

Linked DataLinked Data

http://linkeddata.org

Page 13: How to De-engineer a Semantic Web:

GeoNamesGeoNames

Page 14: How to De-engineer a Semantic Web:

SubgraphsSubgraphs

Canonical TypesCanonical Types

Instance DataInstance Data

Page 15: How to De-engineer a Semantic Web:

Extension/IntensionExtension/Intension

What is ‘Dressel 20’?What is ‘Dressel 20’?

Defined by attributes Defined by attributes (Intension -> a priori (Intension -> a priori analysis)?analysis)?

Defined by examples Defined by examples (Extension -> a (Extension -> a posteriori analysis)?posteriori analysis)?

Page 16: How to De-engineer a Semantic Web:

Quantity vs. uncertaintyQuantity vs. uncertainty

Page 17: How to De-engineer a Semantic Web:

Quantity vs. uncertaintyQuantity vs. uncertainty

Page 18: How to De-engineer a Semantic Web:

Quantity vs. uncertaintyQuantity vs. uncertainty

Page 19: How to De-engineer a Semantic Web:

Interface - ease of useInterface - ease of use

Archaeological data is distributed in fragments Archaeological data is distributed in fragments amongst (generally) non-tech literate amongst (generally) non-tech literate professionals with no money and less time!professionals with no money and less time!

Conversion must beConversion must be

SimpleSimple

FastFast

BeneficialBeneficial

Page 20: How to De-engineer a Semantic Web:

ImplementationImplementation

Page 21: How to De-engineer a Semantic Web:

De-engineering the dataDe-engineering the data

4 Steps4 Steps

Define OntologyDefine Ontology

Define Canonical TypesDefine Canonical Types

Map local termsMap local terms

Generate RDFGenerate RDF

Page 22: How to De-engineer a Semantic Web:

Two OntologiesTwo Ontologies

Page 23: How to De-engineer a Semantic Web:

Linked DatasetsLinked Datasets

archvocab.netarchvocab.netarchvocab.netarchvocab.net

archaeology.rkbexplorer.archaeology.rkbexplorer.comcom

archaeology.rkbexplorer.archaeology.rkbexplorer.comcom

Port Networks Triplestore +Port Networks Triplestore +Port Networks partner sitesPort Networks partner sitesPort Networks Triplestore +Port Networks Triplestore +Port Networks partner sitesPort Networks partner sites

SKOS SKOS SchemesSchemes

SKOS SKOS SchemesSchemes

Additional Additional RDFRDF

InstanceInstancedatadata

Page 24: How to De-engineer a Semantic Web:

archvocab.net/amphoraarchvocab.net/amphora

Page 25: How to De-engineer a Semantic Web:

archaeology.rkbexplorer.archaeology.rkbexplorer.comcom

Project-specific data at class levelProject-specific data at class level

class equivalence using SKOS class equivalence using SKOS (skos:exactMatch)(skos:exactMatch)

class origin (e.g. Dressel 20 :hasOrigin class origin (e.g. Dressel 20 :hasOrigin Baetica)Baetica)

other infoother info

Helps separate vocabulary (archvocab.net) Helps separate vocabulary (archvocab.net) from politics!from politics!

Page 26: How to De-engineer a Semantic Web:

DemoDemo