...
The TRQP Specification consists of three major parts:
The core protocol defines the data model for TRQP queries and responses. The data transmitted by a consumer making a TRQP query and by a TRQP endpoint responding to that query should be consistent regardless of any specific transport protocol binding.
The core query vocabulary is a set of standard verbs used for description, authorization, and recognition queries to maximize interoperability of TRQP across ecosystems.The RESTful binding specifies how TRQP queries and responses work over HTTPS, including the security and privacy considerations associated with that binding.
The Swagger API is a machine-readable definition of the RESTful binding.
The TRQL (Trust Registry Query Language) Specification
In May 2025, the TRTF concluded that the semantics of TRQP queries—specifically the semantics of the assertion component of TRQP authority statements—should be defined in a separate companion specification called the Trust Registry Query Language (TRQL, pronounced “turkle”). This separation enables the TRQP specification to stabilize while the TRQL specification can evolve quickly based on market feedback. See the TRQL wiki page for an introduction.
Implementation considerations
...
The set of verifiable identifier types that need to be supported by the TRQP consumers and endpoints on the network in order to support discovery and verification of TRQP authorities and entities.
The set of trust registries (or metaregistries) that can serve as starting points for TRQP recognition queries within the network.
The set of network-specific query language vocabulary (if any) that enables full interoperability of TRQP queries within that network.
...