A blog post at openbindings.com argues that modeling network protocol descriptions on programming language interfaces such as Swift Protocols and Go Interfaces could invert dependencies and reduce vendor lock-in. The post references Dax Raad's tweet that gained over 50,000 views detailing inconsistent CLIs, config files, and declining Terraform support across providers. It cites IETF RFC 9727 on well-known URIs for discovery and notes the absence of an index.html equivalent for APIs that would allow semantic equivalence queries such as equating file uploads across S3 and R2.

Related coverage in the ACM Computing Surveys paper "IoT Interoperability: A Survey" (2022) documents parallel fragmentation across MQTT, CoAP, and Zigbee ecosystems where manufacturers ship opinionated layers that break abstractions, a point the original post did not connect to infrastructure tooling complaints. HashiCorp's 2023 state-of-infrastructure report similarly records provider plugins lagging vendor API changes, confirming the post's claim that abstraction layers merely relocate rather than eliminate the dependency problem.

The OpenBindings piece, Raad's tweet, and RFC 9727 together indicate that a self-describing standard at the network boundary would allow new implementations to satisfy a shared shape without upstream client modifications, a pattern established in programming languages since the 1990s but not yet standardized for web and IoT boundaries.