Call for Linked Research

Three architectural bases of the Web:

• Identification (URI)
• Interaction (HTTP)
• Data Formats (resource representations)

Axiom 0a: Universality 2

Any resource of significance should be given a URI.

Axiom 2b: identity

the significance of identity for a given URI is determined by the person who owns the URI, who first determined what it points to.

Forces

Actor

Content

Accessibility

Availability

Functions

Registration

Awareness

Certification

Archiving

Decentralized system

A distributed system in which multiple authorities control different components and no single authority is fully trusted by all others.

6 o'clock news at 11:

Decentralised != Interoperable (based on open consensus?)

Open != Free, Inclusive.. (what are the constraints?)

Trends != “the right way”^(tm) (beware of marketing)

Registration does not entail third-party control

Systems... want to control your identity and data.

Couldn’t care less whether infrastructure is operated using open source, commercial, whatever software. It’s about whether the infrastructure components provide open, interoperable, web-centric interfaces.

Data on the Web should not be locked in to particular systems or be only readable by the applications which created it. Users should be free to switch between applications and share data between them.

Applications generate notifications about activities, interactions, and new information, which may be presented to the user or processed further.

• Autonomy; any resource can have an Inbox anywhere
• Identifiable unit; notifications have URIs
• Reusable; a notification can contain any data; use any vocabulary
• Separation of concerns; sender, consumer, receiver

Decentralized social networking protocol based upon the Activity Streams 2.0 data format.

• client to server interactions (eg CRUD, Follow, Like, Block activities)
• federated server to server API for delivering notifications and content

• Choose personal data storage and identities on the Web;
• Use interoperable applications;
• Resource-centric access controls

A simple graph:

• Guinan has a personal storage, and an inbox.
• Guinan knows Ophelia, Eve, Amy.

a client-side editor for decentralised article publishing, annotations and social interactions.

• Linked Data driven tool to read-write resources;
• Single-page application or browser extension;
• Read-Write: Linked Data Platform (or any HTTP server)
• Authentication: WebID-TLS (soon WebID-OIDC)

Human and machine-readable information units.

• Content: progressively-enhanced HTML/RDF, schema.org, PROV-O, SPAR Ontologies, RDF Data Cube, .. (any)
• Annotations: Web Annotation Model (replies, peer-reviews, liking, sharing, bookmarking, describing)
• Notifications: Linked Data Notifications for social sharing
• Activities: ActivityPub protocol, Activity Streams 2.0 vocabulary
• License: Creative Commons for each contribution (user decides)
• Robust Links, ... Archive-friendly!

• Various SW/LD conferences/workshops eg ISWC, ESWC, LDOW, SemStats welcome it - more importantly "Linked Research"
• CEUR-WS.org (largest OA publisher in CompSci) - see ceur-make
• Growing number of examples in the wild
• ... W3C Note Embedding Web Annotations in HTML examples
• ... these slides!

Notifications about scholarly activities (articles, annotations, citations..)

• A notification MUST conform to one of the specified data shapes;
• MUST refer to Linked Data resources;
• MUST refer to free and publicly accessible resources.