Skip to content

Commit

Permalink
Merge pull request #30 from andorsk/ask/problem_statement
Browse files Browse the repository at this point in the history
added problem statement
  • Loading branch information
andorsk authored Mar 11, 2024
2 parents 7d6cc8f + 6869f2b commit 4ea281b
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,6 +77,17 @@ 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
Expand Down

0 comments on commit 4ea281b

Please sign in to comment.