The document summarizes a presentation on mapping language analysis of comparative characteristics. It discusses how the presenters initially tried to compare existing mapping languages by analyzing their requirements, but realized they did not do everything right. They then worked to improve their analysis by filling out a shared document, communicating over email, and resolving issues. The goal was to properly analyze and compare mapping languages to understand their tradeoffs.
Mapping Language Analysis and Comparison of Characteristics
1. Mapping language analysis
of comparative
characteristics
Ben De Meester, Pieter Heyvaert,
Ruben Verborgh, and Anastasia Dimou
Ghent University – imec – IDLab, Belgium
ben.demeester@ugent.be – @B_ _DM
2. AKA the “don’t quote me
on this” presentation
Ben De Meester, Pieter Heyvaert,
Ruben Verborgh, and Anastasia Dimou
Ghent University – imec – IDLab, Belgium
3. http://bit.ly/kgbmap
Ben De Meester, Pieter Heyvaert,
Ruben Verborgh, and Anastasia Dimou
Ghent University – imec – IDLab, Belgium
AKA the “please (digitally)
interrupt me” presentation
27. Step 3
Align and categorize
Non-functional requirements
EASY Easy to use
W3C Based on standards
FULL Fully covering the generation process
DS: Data source support (Tabular, Hierarchical, ...)
Functional requirements
F() General functions (M:N relations, data types, graphs, ...)
EXT Extensible
NEST Nesting
[...] Collections and Lists
30. What we did
Problem
We can’t compare mapping languages
Solution
First attempt: compare existing requirements
Fallout
We didn’t do everything right
Life after the paper
35. What we did
Problem
We can’t compare mapping languages
Solution
First attempt: compare existing requirements
Fallout
We didn’t do everything right
Life after the paper
Let’s try and get it right
36. Let’s disagree
Filling in the document: http://bit.ly/kgbmap
Sending e-mails
Raising and resolving issues
37. Mapping language analysis
of comparative characteristics
Ben De Meester, Pieter Heyvaert,
Ruben Verborgh, and Anastasia Dimou
Ghent University – imec – IDLab, Belgium
ben.demeester@ugent.be – @B__DM
https://openreview.net/forum?id=HklWL4erv4
38. You were actually hoping
to see citations?
[1] Debruyne C, McKenna L and O'Sullivan D (2017), "Extending R2RML with Support for RDF Collections and Containers
to Generate MADS-RDF Datasets", In Research and Advanced Technology for Digital Libraries: 21st International
Conference on Theory and Practice of Digital Libraries, TPDL 2017, Thessaloniki, Greece, September 18-21, 2017,
Proceedings. Cham , pp. 531-536. Springer International Publishing.
[2] Debruyne C and O'Sullivan D (2016), "R2RML-F: Towards Sharing and Executing Domain Logic in R2RML Mappings", In
Workshop on Linked Data on the Web. CEUR.
[3] Junior AC, Debruyne C, Brennan R and O'Sullivan D (2017), "An evaluation of uplift mapping languages", International
Journal of Web Information Systems. Vol. 13(4), pp. 405-424.
[4] Lefrançois M, Zimmermann A and Bakerally N (2017), "A SPARQL Extension for Generating RDF from Heterogeneous
Formats", In The Semantic Web 14th International Conference, ESWC 2017, Portorož, Slovenia, May 28 – June 1, 2017,
Proceedings. Portoroz, Slovenia, May, 2017. , pp. 35-50. Springer International Publishing.
[5] Michel F, Djimenou L, Faron-Zucker C and Montagnat J (2015), "Translation of Heterogeneous Databases into RDF, and
Application to the Construction of a SKOS Taxonomical Reference", In International Conference on Web Information
Systems and Technologies. , pp. 275-296.
[6] Michel F, Djimenou L, Faron-Zucker C and Montagnat J (2017), "xR2RML: Relational and Non-Relational Databases
toRDF Mapping Language". Thesis at: CNRS., October, 2017.
[7] Slepicka J, Yin C, Szekely PA and Knoblock CA (2015), "KR2RML: An Alternative Interpretation of R2RML for
Heterogenous Sources.", In Proceedings of the 6th International Workshop on Consuming Linked Data (COLD 2015).
[8] Tennison J, Kellogg G and Herman I (2015), "Generating RDF from Tabular Data on the Web". Thesis at: World Wide
Web Consortium (W3C)., December, 2015.
Editor's Notes
My name is Ben De Meester, and I have 2 confessions to make.
First confession...
When buying a car, you can choose
And that choice, that being able to choose, that's related to my next confession
So it’s not.
bc. it’s a trade-off. But that’s where the problem lies:
Which trade-off? Which mapping language should I use for my use case?
But. How exactly do mapping languages compare? for which factors is one better or worse than the others?
There's not really smth to compare. (which makes sense, this is all very new)
First attempt, 4 steps
This is biased. Incomplete. It’s a best effort, but not even trying to be exhaustive
The blue ones are claims we made
So, we’re done! A nice little comparative framework, people can pick the right language and right tools.
Except for the fact that this isn’t nearly complete.
Bc of course we didn’t do everything right. This is crude.
Comparisons in an continuously evolving, and tracking-gaining field are always incomplete, obsolete etc.
However, without, what happens is that everyone is re-inventing the same things over and over and over...
And certain gaps remain.
Pano Maria comes after me, he will disagree even more, which is great!