Semantic extensions to ecoRelevé
Olivier Rovellotti
• The projet• The Sem Web• The extentions
Reduce Software complexity
For who?
People we know:
People we don’t know?
Define Protocols Collect data
Analyzedata
AskQuestions
Data Admin
What for?
Citizen Science
Professional Research
PHD
DBA/GIS
3 Modules
RDF
2007
2009
Life Science
2012
Now what ?
What is it good for?
• Better annotations• Easier data integration• More extensible• More expressive
Controlled Vocabularies:
Build protocols forms
Enhance existing dataset
Aggregate data
Annotations
ecoRelevé
Core
1.0
Observation Layers
Data integration
ecoRelevé
explorer
Data enhancement
4 dimensions
Time
Biology
Space
People
Time
Biology
Space
PeopleFriends
Work
FOAF
Localities Protected Areas
Last weekAt the same time as
Conservation Status
Family
GeoSparql
Data connector
Milan royalMilvus milvusRed Kite
SPARQL:Catch the frog
select ?scientificName, ?status, ?lat, ?long FROM <urn:rdf.TdwgFroggyChallenge>where { ?s rdf:type uniprot:Molecule . ?s terms:relation ?id. ?s terms:subject ?taxonInGB . ?id geo:lat ?lat. ?id geo:long ?long. ?taxonInDbPedia dbOwl:conservationStatus ?status. ?taxonInGB rdfs:seeAlso ?taxonInDbPedia. ?taxonInGB uniprot:scientificName ?scientificName.}
ecoReleve
SparQL
TAISTY!
Take home message :
• There is a learning curve• But RDF is not that difficult• One API is better than 10 • We need data in RDF to experiment
• Reasoning is for later …
Thanks ..
@orovellotti