Adversarial Interoperability

Interoperable Serendipity

If you had asked my thoughts on interoperability some years ago, I wouldn't have had much to say. Nowadays, it has become one of my most revered ideals. And today, I want to take you along for a journey towards its summum: Interoperable Serendipity.

Eventual Interoperability – Pieter Colpaert

A pragmatic approach to interoperability: model your data richly for your own needs, then allow the eventual creation of one‑to‑many alignments.

Blaine Cook

Hi! I'm Blaine, a software programmer living in the Slocan Valley who works on decentralized technologies (<a href="https://www.eff.org/deeplinks/2019/10/adversarial-interoperability">this</a> kind, not that kind) in order to give communities the autonomy to self-determine in online spaces.

But First, Interoperability · augment

A blog by Anuj Ahooja

The Direction of Interoperability

Talking in terms of horizontal or vertical interoperability is too constrictive a mental model to understand what interoperability does. Doing better matters, and it's right within reach.

Infrastructure as Code is Artisanal Automation

“Artisanal” refers to something made in a traditional way by hand by a skilled craftsman, requiring both time and expertise.

Web Components Interoperability | Unpacked

Web Components Interoperability — explained clearly with diagrams.

Two Types of Interoperability Without Sharing Lexicons - Wesley's notes

Sharing lexicons is not the only way to leverage atproto’s interoperability

Two Types of Interoperability Without Sharing Lexicons - Wesley's notes

Sharing lexicons is not the only way to leverage atproto’s interoperability

Experiences with recombinant computing: Exploring ad hoc interoperability in evolving digital networks

This article describes an infrastructure that supports the creation of interoperable systems while requiring only limited prior agreements about the specific forms of communication between these systems. Conceptually, our approach uses a set of “meta-interfaces”—agreements on how to exchange new behaviors necessary to achieve compatibility at runtime , rather than requiring that communication specifics be built in at development time —to allow devices on the network to interact with one another. While this approach to interoperability can remove many of the system-imposed constraints that prevent fluid, ad hoc use of devices now, it imposes its own limitations on the user experience of systems that use it. Most importantly, since devices may be expected to work with peers about which they have no detailed semantic knowledge, it is impossible to achieve the sort of tight semantic integration that can be obtained using other approaches today, despite the fact that these other approaches limit interoperability. Instead, under our model, users must be tasked with performing the sense-making and semantic arbitration necessary to determine how any set of devices will be used together. This article describes the motivation and details of our infrastructure, its implications on the user experience, and our experience in creating, deploying, and using applications built with it over a period of several years.

Data Mesh Architecture: Interoperability, Co-Operation, and Co-Regulation 

This paper examines the emergence of data mesh architectures and data intermediaries as key components in emerging data economies. It explores how data mesh arc