Editor’s Draft — Work in Progress
This version: 4.0
Latest published version: 4.0
Previous version: 3.1
Editor: Cagan Mert ISLEK hello@islekcaganmert.me
Contributors: Cagan Mert ISLEK hello@islekcaganmert.me
Status: Draft
Publication Date: –/–/—-
Version: 4.0
Test Suite: Not yet available
Implementation Report: Not yet available
TheProtocols defines a federated communication and computation framework designed to decentralize super applications by enabling users to select both the network and the client of their preference. TheProtocols provides an extensible base for identity, session, data, and app management across independently administered networks, supporting both consumer-grade and enterprise-level applications.
The protocol defines interoperable object formats and transport mechanisms, intended to support the core functionality that a typical user requires in daily digital activity.
This section describes the status of this document at the time of its publication. Other documents, as published officially by the TheProtocols Foundation, may supersede this document.
This document is an Editor’s Draft of TheProtocols 4.0. It is under active development and subject to substantial change. Implementers MUST NOT rely on this version for production systems without providing a compatible fallback mechanism.
All interested parties are invited to submit implementation reports, issues, and suggestions via the public issue tracker, the Fediverse, or email at hello@islekcaganmert.me.
Future updates will reflect implementer feedback and formal testing.
TheProtocols defines a federated, extensible standard for building and interconnecting modular super applications. Its goal is to offer the interoperability and openness while enabling rich and secure app-level communication without a centralized authority.
TheProtocols consists of a Remote Procedure Call standard and multiple submodules under the org.theprotocols namespace, each addressing a distinct area.
This specification relies on the following technologies and formats:
All timestamps and durations defined in this specification MUST be expressed in UTC.
The key words MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in [RFC2119].
A conformant implementation of TheProtocols:
org.theprotocols.*).Conformance requirements apply equally to both servers and clients unless otherwise specified.
org.theprotocols.network)/.well-known/app_info.json)org.theprotocols.session.*)TheProtocols allows different namespaces to be introduced by third party implementers. Any external namespace MAY have their documentation added IF the namespace is intended for network-side federation. However, implementers MUST NOT expect these namespaces to exist in all networks even though all networks SHOULD implement as much namespaces as possible.