From f0a508ce1eeb93deb6d951a98fcc02fe5bf03993 Mon Sep 17 00:00:00 2001 From: Andor Kesselman Date: Mon, 11 Mar 2024 11:02:04 -0700 Subject: [PATCH] added problem statement --- spec.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/spec.md b/spec.md index 8972aec..7424aa3 100644 --- a/spec.md +++ b/spec.md @@ -35,6 +35,17 @@ spec offers a straightforward yet effective discovery layer for both legacy and new trust registry services. The intended audience includes individuals or entities seeking to improve service interoperability with their existing services or on new services. +### Problem Statement + +Current endpoint systems lack a clear method to identify the protocols a service +supports. The DID Core Spec’s Service Endpoint type field is not sufficiently +expressive for endpoints to fully understand what protocols a service endpoint +supports. This specification addresses this gap in the DID Core specification by +introducing a straightforward way for endpoints to indicate support of a +protocol or service using a structured Profile Document Model. These documents +are reusable, decentralized, and expressive documents that allow service +providers to connect and interoperate with endpoint systems with less friction. + ### Example In this example, we illustrate a practical example of profiles. We have a Service that