Information sharing pipeline

Information Sharing Pipeline
Violeta Ilik & Lukas Koster
Columbia University Libraries | Library of the
University of Amsterdam
NASIG 2018, June 9, 2018
Atlanta, GA
@azraiekv @lukask

What do we mean by information
sharing pipeline?
[GDS/Real time information
channel]

Real time information channel fed by and consumed
by institutions and applications that manage and use
identity information.
We described the idea in a couple of blog posts:
● Why not share? 08/26/2017 [1]
● Real time information channel 10/19/2017 [2]
[1] https://ilikvioleta.blogspot.com/2017/08/why-not-share.html
[2] https://ilikvioleta.blogspot.com/2017/10/real-time-information-channel.html

https://ilikvioleta.blogspot.com/2017/10/real-time-information-channel.html

Overview
Ilik, Violeta. (2015). Distributed person data: using Semantic Web compliant data in subject name headings. International
UDC Seminar, Classification and Authority Control: Expanding Resource Discovery, Lisbon, Portugal, October 29, 2015.

Overview
The solution may not be to try and fix the closed
and constrained systems.
The solution may be to completely change the
way we currently think and work.
Use the W3C standards and protocols to
decouple data from service providers or
applications.

Outline:
● Inspiration: Decentralized Web
● Problem
● Existing standards/protocols
● Recommendations

Inspiration: Tim Berners-Lee
“There is an architecture in which a few existing or Web
protocols are gathered together with some glue to make a
world wide system in which applications (desktop or Web
Application) can work on top of a layer of commodity
read-write storage. Crucial design issues are that principals
(users) and groups are identified by URIs, and so are global
in scope, and that elements of storage are access controlled
using those global identifiers. The result is that storage
becomes a commodity, independent of the application
running on it.” [8/17/2009]
https://www.w3.org/DesignIssues/CloudStorage.html

Separate the Applications from Storage
● It allows the user to control access to their data, whatever applications they use
● It allows the data from various applications to be cross-linked, at great derived
extra value, breaking down the silos described above.
● It allows innovation in the market for applications, because the bar far launching
an app is far lower, as the app can run in the open data cloud.
● The persistence of applications and data may be very different. In some cases a
well-established application which people have grown very familiar with may be
used to make an online discussion which is ephemeral, in another case an
application may be developed to solve a short term problem in an enterprise where
the life of the data exceeds that of any of the applications the enterprise uses. By
decoupling the application and data, these persistences can be managed
independently.

Notifications
Push or pull?

https://github.com/solid/solid-tutorial-intro
One data pod per person
Highly granular access control
Inspiration: SOLID

https://www.w3.org/2018/Talks/0529-timbl-tur
ing/timbl-turing-slides-utopia-to-dystopia.html#/
97Inspiration: SOLID
Solid is an
application
platform for
decentralization
through Linked
Data

https://ruben.verborgh.org/blog/2017/12/20/paradigm-shifts-for-the-decentralized-web/
Inspiration: Ruben Verborgh

Paradigm
shift 1:
End users
become
data owners

Paradigm shift 2: Apps become views
you enter data only once—in your own data pod

Paradigm shift 3: Interfaces become queries

Decentralizing the Web is about reorganizing power

Problem
Who holds the data?
Stakeholder:
Libraries
Stakeholder:
Publishers
Stakeholder:
Vendors
Stakeholder:
Identity
Providers
Stakeholder:
OCLC

Stakeholder:
Libraries
Stakeholder:
Publishers
Stakeholder:
Vendors
Stakeholder:
Identity
Providers
Stakeholder:
OCLC
Problem
How do we work together to exchange/verify information
about entities in real time?

Stakeholder:
Libraries
Stakeholder:
Publishers
Stakeholder:
Vendors
Stakeholder:
Identity
Providers
Stakeholder:
OCLC
Break Down the Walls
Problem

Opening up the communication channel
Problem

http://csarven.ca/presentations/call-for-linked-research-dans/
Sarven Capadisli
Problem

Existing standards/protocols
WebSub protocol
ActivityPub protocol
Linked Data Notifications protocol

Existing standards:WebSub protocol
● Topic
● Hub ("the hub")
● Publisher
● Subscriber
● Subscription
● Subscriber Callback URL
● Event
● Content Distribution Notification / (Content
Distribution Request)
It’s not Linked Data centric!
https://www.w3.org/TR/websub/#definitions

https://www.w3.org/TR/websub/#high-level-protocol-flow

https://www.w3.org/TR/websub/#candidate-recommendation-exit-criteria
Roles:
1. Publisher
2. Subscriber
3. Hub

Subscribing and Unsubscribing
● Subscriber requests a subscription at the hub
● The hub validates the subscription with the publisher
(OPTIONAL)
● The hub confirms the subscription was actually
requested by the subscriber
● The hub periodically reconfirms the subscription is still
active (OPTIONAL)
https://www.w3.org/TR/websub/#subscribing-and-unsubscribing

In this environment there is no
central/correct/unique version of the data --
instead there are many versions that are informed
by work being done in different
institutions/applications that manage and use
identity information.
https://ilikvioleta.blogspot.com/2017/10/real-time-information-channel.html

Existing standards:ResourceSync
ResourceSync Change Notifications - push-based
Editors:
Martin Klein, Herbert Van de Sompel - Los Alamos National Laboratory
Simeon Warner - Cornell University
Graham Klyne - University of Oxford
Bernhard Haslhofer - University of Vienna
Michael Nelson - Old Dominion University
Carl Lagoze - University of Michigan
Robert Sanderson - The Getty
http://www.openarchives.org/rs/notification/1.0.1/notification

Existing standards: ResourceSync
ResourceSync Change Notifications
WebSub as Transport Protocol
Table 2: Mapping of terminologies between ResourceSync and WebSub
ResourceSync WebSub
Source Publisher
Destination Subscriber
Channel Topic
Notification Notification
Hub

Existing standards
ResourceSync Change Notifications
WebSub as Transport Protocol

Existing standards: ActivityPub
The ActivityPub protocol is a decentralized social
networking protocol based upon the [ActivityStreams] 2.0
data format. It provides a client to server API for creating,
updating and deleting content, as well as a federated server
to server API for delivering notifications and content.
https://www.w3.org/TR/activitypub/

ActivityPub provides two layers:
1. A server to server federation protocol
2. A client to server protocol

In ActivityPub, a user is represented by "actors" via the
user's accounts on servers. User's accounts on different
servers correspond to different actors. Every Actor has:
An inbox: How they get messages from the world
An outbox: How they send messages to others

All objects have the following properties:
● id
The object's unique global identifier
● type
The type of the object.

Actor types are Object types that are capable of performing
activities.
The core Actor Types include:
Application
Group
Organization
Person
Service

Existing standards: Linked Data Notifications
Simpler design:
Linked Data Notifications is a protocol that
describes how servers (receivers) can have
messages pushed to them by applications (senders),
as well as how other applications (consumers) may
retrieve those messages.
ActivityPub incorporates LDN.

Modular systems
Decouple data storage from the applications
The protocol is intended to allow senders, receivers
and consumers of notifications to seamlessly work
together, contributing to decentralisation of our
interactions on the Web.

https://www.w3.org/TR/ldn/#overview

LDN “in use”
By Herbert
Van de
Sompel
https://www.slideshare.net/hvdso
mp/paul-evan-peters-lecture/

Recommendations:
WebSub protocol
LDN protocol
Which one will work?

Recommendations:
WebSub + ResourceSync protocol
LDN protocol
Which one will work in the near future?

What’s the hold up?
Sarven Capadisli

What’s the hold up?
Politics
Intellectual property issues

Lukas Koster
Sarven Capadisli
Herbert Van de Sompel
PCC Task Group on Identity Management
in NACO
Acknowledgment
https://pixabay.com/photo-2031395/

Violeta Ilik
Thank you
https://pixabay.com/photo-2031395/

Information sharing pipeline

Recommended

Recommended

More Related Content

Similar to Information sharing pipeline

Similar to Information sharing pipeline (20)

More from Violeta Ilik

More from Violeta Ilik (13)

Recently uploaded

Recently uploaded (20)

Information sharing pipeline