5
W OL: S D V S A Krzysztof Janowicz STKO Lab University of California, Santa Barbara, USA Pascal Hitzler DaSe Lab Wright State University, Datyon, USA EarthCube All-Hands Meeting EarthCube Architecture Forum June 2014 S D V S A J H

AHM 2014: OceanLink, Smart Data versus Smart Applications

Embed Size (px)

DESCRIPTION

Presentation given by Krysztof Janowicz and Pascal Hitzler in the afternoon Architecture Forum Session on Day 1, June 24, at the EarthCube All-Hands Meeting.

Citation preview

Page 1: AHM 2014: OceanLink, Smart Data versus Smart Applications

Why

OceanLink: Smart Data Versus Smart

Applications

Krzysztof JanowiczSTKO Lab University of California, Santa Barbara, USA

Pascal HitzlerDaSe Lab Wright State University, Datyon, USA

EarthCube All-Hands MeetingEarthCube Architecture Forum

June 2014

Smart Data Versus Smart Applications Janowicz and Hitzler

Page 2: AHM 2014: OceanLink, Smart Data versus Smart Applications

Why

What kind of architecture specification do you have?

OceanLink relies on the Semantic Web and Linkd Data; strictlyspeaking this is not an architecture.Data component: Data is translated into RDF (Resource DescriptionFramework), semantically lifted, and published as 5-star Linked Data.Schema component: OceanLink wants to foster discoverability andinteroperability without restricting heterogeneity and thus does notuse classical static data models. Instead, it relies on Ontology DesignPatterns (ODP) and data-driven, application-centric ontologies thatuse these patterns.Service component: OceanLink data is made discoverable andqueryable via a SPARQL Endpoint. Inferencing is supported via theused ODPs and standard Semantic Web reasoning services. A userinterface for data seeking and exploration is provided via a facetedbrowsing interface.

Smart Data Versus Smart Applications Janowicz and Hitzler

Page 3: AHM 2014: OceanLink, Smart Data versus Smart Applications

Why

How is it being used?

In OceanLink Semantic Web technologies & ontologies are used toEase the publication of data (so far BCO-DMO and R2R)Improve the retrieval of data beyond keyword searchDeploy ODP to be used by other EarthCube repositoriesEstablish links between repositories (planned)Compress data based on background ontologies (planned)Support simple inferencing based on the ODP

Smart Data Versus Smart Applications Janowicz and Hitzler

Page 4: AHM 2014: OceanLink, Smart Data versus Smart Applications

Why

Why is it valuable?

Two key insights and paradigm shifts1 Enable the creation of smart data in contrast to smart applications.

Instead of developing increasingly complex software, the businesslogic should be moved to the (meta)data. Smart data will make allfuture applications more usable, flexible, and robust, while smarterapplications fail to improve data along the same dimensions.

2 Cultural, conceptual, and infrastructural heterogeneities must berespected in order to maintain different perspectives and differingpriorities and thus foster inclusivity in the EarthCube endeavor.Heterogeneity is a resource and should not be resolved.

The Semantic Web and Linked Data were developed with those ideas andWeb-scalability in mind. Longevity is ensured via an early, open, and rigidstandardization process by the W3C.

Smart Data Versus Smart Applications Janowicz and Hitzler

Page 5: AHM 2014: OceanLink, Smart Data versus Smart Applications

Why

What worked, and what did not?

WorkedCreation of ontology design patternsCreation of Linked DataFaceted browsing interface

Did not workToo early to tellSome data types/formats will be difficult to transfer to Linked Data

Smart Data Versus Smart Applications Janowicz and Hitzler