Re:Protocols, Not Platforms: A Technological Approach to Fre...
by zer0gravity on Thursday January 28, 2021 @12:58PM
(#25945843)
What I think we need is Interoperability, not just protocols. What I understand by interoperability is what a mature (spoken) language provides. Although its body of words remains pretty much fixed, it offers a wide range of expression. I think that what we need is a language of the internet to achieve this type of interoperability. So, in a way, a language can be seen as a communication protocol and, with such a language, two systems can talk and discover and consume each other's services. This language shouldn't change too much, but it should be complex enough, to start with, in order to allow a high degree of expression and, ultimately, interoperability.
[ Parent
| on HN ]
Re:Protocols, Not Platforms: A Technological Approach to Fre...
by hirundo on Thursday January 28, 2021 @01:37PM
(#25946672)
Discoverability is a fundamental part of protocol design. Here's a list of service discovery protocols:
https://en.wikipedia.org/wiki/Service_discovery
We could use a C-3PO (protocol droid, fluent in over six million forms of communication) for interop.
Re:Protocols, Not Platforms: A Technological Approach to Fre...
by zer0gravity on Thursday January 28, 2021 @01:58PM
(#25947073)
I'm not talking about a zillion protocols with discoverable services, but of a single language of the internet that allows service discoverability and concept sharing dynamically between peers.