Interoperability: Difference between revisions

From XPUB & Lens-Based wiki
(To write about Interoperability on the Grapevine)
 
m (Better syntax)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[:Category: Tommi’s to-do list]]
One of the most crucial problems of technology is when machines or software don’t know how to talk to each other, because of many overlapping potential reasons: proprietary and closed implementations, inability of humans to agree on standards, deprecated or obsolete protocols that limit the scope of what it is now possible to do…
[[Category: Grapevine]]
 
[[Image:Xkcd -927- Standards.png|thumb|alt=[Caption above the panels:] How Standards Proliferate (See: A/C chargers, character encodings, instant messaging, etc.) [A text-only panel.] Situation: There are 14 competing standards.      [Cueball and Ponytail stand facing each other.] Cueball: 14?! Ridiculous! We need to develop one universal standard that covers everyone’s use cases. Ponytail: Yeah! [Another text-only panel. The word “Soon:” appears in its own box at the upper left of the panel.] Soon: Situation: There are 15 competing standards.|[https://xkcd.com/927/ xkcd #927: Standards]]]
 
The challenge remains: interoperability among tools can be associated with confabulation among human beings. It may not be the fastest, most efficient, and most <q>productive</q> way of achieving a goal, still, it is the most accepting, inclusive, communal.
 
Even if interoperability was not conceived as a fundamental principle in the making of a tool, as hackers it is our imperative to crack things open, and bridge them!
 
We should also compel big tech to be at least a bit more fair by enforcing <q>Adversarial Interoperability</q><ref><cite>Cory Doctorow, [https://www.eff.org/deeplinks/2019/11/altinteroperabilityadversarial alt.interoperability.adversarial]</cite> (2019)</ref>: ensuring that widespread closed technologies adopt open standards. A perfect example in the legislative domain is the European Union’s [https://digital-markets-act.ec.europa.eu/index_en Digital Markets Act]<ref>REGULATION (EU) 2022/1925 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 14 September 2022 on contestable and fair markets in the digital sector and amending Directives (EU) 2019/1937 and (EU) 2020/1828 (Digital Markets Act): https://eur-lex.europa.eu/eli/reg/2022/1925/oj/eng</ref>
 
<noinclude>[[Category: Grapevine]]</noinclude>

Latest revision as of 11:25, 11 March 2026

One of the most crucial problems of technology is when machines or software don’t know how to talk to each other, because of many overlapping potential reasons: proprietary and closed implementations, inability of humans to agree on standards, deprecated or obsolete protocols that limit the scope of what it is now possible to do…

The challenge remains: interoperability among tools can be associated with confabulation among human beings. It may not be the fastest, most efficient, and most productive way of achieving a goal, still, it is the most accepting, inclusive, communal.

Even if interoperability was not conceived as a fundamental principle in the making of a tool, as hackers it is our imperative to crack things open, and bridge them!

We should also compel big tech to be at least a bit more fair by enforcing Adversarial Interoperability[1]: ensuring that widespread closed technologies adopt open standards. A perfect example in the legislative domain is the European Union’s Digital Markets Act[2]

  1. Cory Doctorow, alt.interoperability.adversarial (2019)
  2. REGULATION (EU) 2022/1925 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 14 September 2022 on contestable and fair markets in the digital sector and amending Directives (EU) 2019/1937 and (EU) 2020/1828 (Digital Markets Act): https://eur-lex.europa.eu/eli/reg/2022/1925/oj/eng