linked data developments in seadatacloud · publication of the linked data terms. • port entries...
TRANSCRIPT
![Page 1: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/1.jpg)
Linked Data Developments in SeaDataCloud
Adam Leadbetter, Rob Thomas (Marine Institute)
Alexandra Kokkinaki, Chris Wood (BODC)
Dick Schaap (Maris)
![Page 2: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/2.jpg)
Why Linked Data for SeaDataNet?
![Page 3: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/3.jpg)
Why Linked Data for SeaDataNet?
• Types of questions we can ask…• “Which cruises have physical
oceanographic data?”
• “Give me all temperature data for the Celtic Seas for 2015”
![Page 4: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/4.jpg)
Why Linked Data for SeaDataNet?
![Page 5: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/5.jpg)
What we didn’t want to do
![Page 6: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/6.jpg)
What we did about it
• Reusing existing patterns• Better understanding outside of SDN
• Better interoperability with other organisations
• Better INSPIRE compliance
![Page 7: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/7.jpg)
What we did about it
• Reusing existing patterns• EDMO
• EDMED
• EDMERP
• CDI
• CSR
• EDIOS
![Page 8: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/8.jpg)
What we did about it
• Reusing existing patterns• EDMO – W3C Organisation
• EDMED – W3C DCAT
• EDMERP – W3C Prov / DBPedia Research Project
• CDI – W3C DCAT• ODV metadata to INSPIRE / ISO O&M
• CSR - …
• EDIOS – INSPIRE Environmental Monitoring Facilities
![Page 9: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/9.jpg)
What we did about it
• Reusing existing patterns• Also
• Sextant catalogue to W3C DCAT
![Page 10: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/10.jpg)
CSR Patterns
cruise:Cruise
cruise-summary:CruiseSummary
Report
cruise-summary:describesCruise
“…”cruise-summary:
description
cruise-summary:responsibleLaboratory
<<…>><<…>>
cruise-summary:generalOceanArea
cruise-summary:marsdenSquare
dcterms:Location
dcterms:spatial
<<…>>
cruise-summary:specificGeographicArea
“…”^^xsd:date
dc:created
<<…>>cruise-summary:
trackChart
cruise-summary:hasProgram
geolink:Dataset
cruise-summary:hasDataset
prov:Activity
prov:Organization
operation:Operation
cruise-summary:hasOperation
![Page 11: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/11.jpg)
CSR Patterns
cruise:Cruise
cruise:hasChiefScientist
cruise:hasStartPortCall
cruise:hasEndPortCall
cruise:isUndertakenBy
cruise:hasCoChiefScientist
cruise:hasIdentifier
^^gsp:wktLiteralcruise:
hasTrack
cruise:PortCall
cruise:PortCall
prov:Agent
prov:Agent
<< >>
cruise:hasDOI
rdfs:label
prov:Agent
![Page 12: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/12.jpg)
CSR Patterns
geolink:Dataset
<<…>>
[…]
geolink:hasInstrument
geolink:hasInstrumentType
<<…>>
geolink:hasMeasurementType cruise:
PortCall
<<…>>cruise:atPort
“…”^^xsd:date
cruise:hasTimestamp
operation:Operation
operation:AssociatedEvent
operation:AssociatedEvent
^^xsd:date ^^gsp:wktLiteral
operation:hasTimeStamp operation:
atLocation
operation:
hasDescriptionoperation:
hasInstrumentprov:Agent
![Page 13: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/13.jpg)
Issues• Creation of a SeaDataNet Linked Data
ontology.
• Clean URIs for each catalogue
• Content negotiation
• NERC Vocabulary Server v.1 is deprecated.
• EDMO links to external vocabularies
• All terms in C19 are equated to prov:Location.
• A register of individuals and publications.
• Project record to an associated research programme links to another EDMERP record not an XML snippet.
• Dbpedia to PROV-O alignment.
• CDIs with EDMED codes included should be used to populate the DCAT Distribution information.
• Consider alignments in the DCAT keywords
specification to the research classification vocabularies.
• A non-SDN/SDC namespace is used for the publication of the Linked Data terms.
• Port entries in C38 should be given an RDF linkage to their countries.
• Port entries in C38 should be made instances of geolink:Place and prov:Location.
• Research vessels entries in C17 should be made instances of prov:Entity.
• A CDI SKOS scheme should be set up on the NVS incorporating the P02, L05 and C19 vocabularies.
• Include links to ICES station dictionary URIs.
• Include links to terms from the BODC Series Feature Type vocabulary (C10).
![Page 14: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/14.jpg)
Issues – URLs
http://seadata.bsh.de/Cgi-csr/retrieve_sdn2/viewReport.pl?csrref=[csr_code]http://www.bodc.ac.uk/data/information_and_inventories/edmed/report/[edmed_code]/http://seadatanet.maris2.nl/v_edmo/print.asp?n_code=[n_code]http://seadatanet.maris2.nl/v_edmerp/print.asp?n_code=[n_code]http://seadatanet.maris2.nl/v_cdi_v3/print_ajax.asp?n_code=[n_code]http://seadatanet.maris2.nl/v_edios_v2/print_ajax.asp?screen=0&n_code=[n_code] programmehttp://seadatanet.maris2.nl/v_edios_v2/print_ajax.asp?screen=1&n_code=[n_code] series
![Page 15: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/15.jpg)
Issues – URLs
http://www.seadatanet.org/cruise-summary/[csr_code]
http://www.seadatanet.org/edmed/[edmed_code]
http://www.seadatanet.org/edmo/[n_code]
http://www.seadatanet.org/edmerp/[n_code]
http://www.seadatanet.org/cdi/[n_code]
http://www.seadatanet.org/edios/programme/[n_code]
http://www.seadatanet.org/edios/series/[n_code]
![Page 16: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/16.jpg)
Issues – URLs
http://www.seadatanet.org/cruise-summary/[csr_code]
http://seadata.bsh.de/Cgi-csr/retrieve_sdn2/viewReport.pl?csrref=[csr_code]
![Page 17: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/17.jpg)
Issues – EDMO interoperability
http://vocab.aodn.org.au/def/organisation/entity/1 a skos:Concept;
skos:inScheme http://vocab.aodn.org.au/def/organisation/1.
http://linked.seadatanet.org/edmo/1 a org:Organization.
???
![Page 18: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/18.jpg)
Issues – EDMO interoperability
![Page 19: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/19.jpg)
Issues – EDMO interoperability
skos:exactMatch
![Page 20: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/20.jpg)
Issues – EDMO interoperability
skos:exactMatch
owl:sameAs
![Page 21: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/21.jpg)
Issues – EDMO interoperability
skos:exactMatch
owl:sameAs
rdfs:seeAlso
![Page 22: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/22.jpg)
Issues – EDMO interoperability
skos:exactMatch
owl:sameAs
so:claimsIdentical
rdfs:seeAlso
![Page 23: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/23.jpg)
Issues – EDMO interoperability
skos:exactMatch
owl:sameAs
Recommended reading:
When owl:sameAs isn't the Same by Halpin et al
http://iswc2010.semanticweb.org/pdf/261.pdf
so:claimsIdentical
rdfs:seeAlso
![Page 24: Linked Data Developments in SeaDataCloud · publication of the Linked Data terms. • Port entries in C38 should be given an RDF linkage to their countries. • Port entries in C38](https://reader034.vdocuments.us/reader034/viewer/2022050203/5f565ee63a11501d3968500b/html5/thumbnails/24.jpg)
Next Steps
• Address pre-requisites in the issues
• Develop RDF implementation of catalogues• Alexandra will present EDMED developments
• Develop Schema.org mappings• Done for EDMED