From 060ad3e02c5cf587b09448ef453a1d6b3038f0eb Mon Sep 17 00:00:00 2001 From: Darrell O'Donnell Date: Tue, 20 Feb 2024 09:02:20 -0800 Subject: [PATCH] edits per SM Signed-off-by: Darrell O'Donnell --- spec/scope.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/spec/scope.md b/spec/scope.md index 806d5f8..3c9bfac 100644 --- a/spec/scope.md +++ b/spec/scope.md @@ -7,7 +7,7 @@ ## Scope -The Trust Registry Protocol serves to provide a simple interface to the plethora of systems that contain answers that are required to make trust decisions. +The Trust Registry Protocol serves to provide a simple interface to enable access to systems of record that provide the information that drives a trust registry. There are a plethora of systems that contain answers that are required to make trust decisions. The protocol is intended to make the communication with any particular system-of-record consistent and simple. The TRP does not: * create a trust registry - it allows (read-only) access to a system-of-record that has the data needed to generate answers that a trust registry provides. @@ -20,7 +20,6 @@ The TRP does not: The purpose of this **ToIP specification** is to define a standard interoperable protocol for interacting with a global web of **peer trust registries**, each of which can answer queries about whether a particular **party** is trusted and authorized, to perform a particular **action** in a particular **digital trust ecosystem** (defined under an **EGF**), as well as which **peer trust registries** trust each other. - ### Motivations A core role within **Layer 4** of the **ToIP stack** is a **trust registry** (previously known as a **member directory**). This is a network service that enables the **governing authority** for an **ecosystem governance framework (EGF)** to specify what **governed parties** are authorized to perform what **actions** under the EGF. For example: