LEAP – Lexical Engine and Platform – Why Linked Data?
LEAP – Lexical Engine and Platform – Why Linked Data?
1 0
OGL_Symposium
Reveal.js presentation for the Oxford Global Languages SymposiumOn Github mattkohl / OGL_Symposium
LEAP
Lexical Engine and Platform
Matt Kohl | Team Lead
Our
Challenge:
Integrate
Optimize,
&
Deliver
OUP lexical data
We have loads:
Dictionaries
Thesauri
Morphology
Usage examples
In many
languages
Most of this is
Some of which is
linked
But...
The data-sets are siloed,
& managing those links is
difficult
Also...
We can only deliver
via
manual
data dump
Our
Solution:
Linked Data!
APIs!!
Why Linked Data?
Scalable data integration
Graph model
Inferencing
English monolingual
lunch
noun
a meal eaten in the middle of the day, typically one that is lighter or less formal than an evening meal
English-Northern Sotho bilingual
lunch
noun
letena
English-isiZulu bilingual
lunch
noun
isidlo sasemini
lunch
noun
a meal eaten in the middle of the day, typically one that is lighter or less formal than an evening meal
letena (Northern Sotho)
isidlo sasemini (isiZulu)
megh ( Klingon)
lunch (en) - letena (nso) - isidlo sasemini (zu)
Why APIs ?
Automated data delivery ! ! !
More flexibility
Extended reach
New business models
Our
Status:
We have written an
Ontology
in OWL DL
We built an
XMLRDF
transformation framework
& we're pushing data-sets through
Next: UrduWe've launched our
API version 0.1
GET
POST
PUT
DELETE
Using these technologies
( and a few others... )
We've solicited some
Early-access testing
to kick the tires
Want in?
Let us know!
Next Steps:
New API endpoints
More data-sets into RDF
Improve linking within & without
Thanks !
Questions ?
matt.kohl @ oup.com