1 Linked(OpenData) vs Open(Linked Data): a voice from the industry LOD 2014 – Rome 2014/02/20 Vittorio Di Tomaso – Matteo Casu 2 LD for Semantic Search 3 Objective 2 contexts: Linked/Open - Public/Private. What does prevent LOD publication? 4 Linked Open Data 5 Linked and/or Open Data 6 The Public Sector: clear process 7 Public sector: simple process… 8 The Private Sector: diverse uses of LD 9 Crafting RDF artifacts 10 Why companies’ RDF is not published 11 Receipts Public Sector: use “true” LOD technologies (RDF dumps or SPARQL endpoints) Private companies: use standard data models, internally and for their artifacts OpenData Community: please stress the linked in LOD!

1. Linked(OpenData) vs Open(Linked Data): a voice from the industry
LOD 2014 – Rome 2014/02/20
Vittorio Di Tomaso – Matteo Casu

2. projects
SaaS
consulti
ng
LD for Semantic Search
2
@copyright 2014 CELI / Me-Source / Cross Library
Lorem ipsum dolor sit amet, soldatino
consectetur, sed do eiusmod tempor
incididunt ut labore et sed eiusmod tempor
Luigi Einaudi aliqua. Roma, quis nostrud
exercitation ullamco laboris nisi ut aliquip ex
ea commodo consequat
http://it.dbpedia.org/resource/Luigi_Einaudihttp://purl.org/bncf/tid/17802
http://sws.geonames.org/3169071/
livedIn

3. Objective
Linked/Open
Public/Private
What does
prevent LOD
publication?
2 dimensions
2 contexts
3

4. Linked Open Data
4
1. use URIs
2. use HTTP URIs
3. use de-referentiable URIs,
using the standards
(RDF*, SPARQL)
4. include links to other URIs
But:
what does it count
as standard?
As open?
As linked?

5. Linked and/or Open Data
Linked Data
Open Data
?
5
LOD

6. The Public Sector: clear process
acquire
data
set open
license
open
formats
publish
6

7. Public sector: simple process…
LACK
OF MONEY
LACK
OF WILLINGNESS
USE OF “STANDARDS”
… hard
problems OPAQUE DATASETS
POOR RDF/SPARQL
SUPPORT
7

8. The Private Sector: diverse uses of LD
as user:
named entity recognition, content
enrichment, machine linking, discovery
search…
as provider for the Public Sector:
publishing, data integration
internal use:
e.g. assets management
crafting of RDF artifacts for a particular
application
8

9. RDF KB
Crafting RDF artifacts
Exploration APISearch
The artifacts/datasets
produced are linked (they
o f t e n r e u s e s t a n d a r d
models) but not always
inter-operable.
Why?
Linguistic Analysis
Processing
Index Ling
Resource
Data
Storage
Documents acquisition
9

10. Why companies’ RDF is not published
HENCE à OVERFITTING:
Provocation
It would not be interesting nor usable
WAY OUTS:
having more standard models for particular micro-domains could permit their direct
(re)use by the private company
10
• It often reflects customers’ needs • It often reflects internal data models

11. Receipts
Public Sector: use “true” LOD technologies (RDF dumps or SPARQL endpoints)
Private companies: use standard data models, internally and for their artifacts
OpenData Community: please stress the linked in LOD!
11
The success of LOD is bound to the use of Linked Data
as a technology
The use of LD in the private sector will positively
feedback on the diffusion of the necessary expertise
and sensibility in the Public Sector too