[3] A DID identifies any subject (e.g., a person, organization, thing, data model, abstract entity, etc.)

DIDs are designed to enable the controller of a DID to prove control over it and to be implemented independently of any centralized registry, identity provider, or certificate authority.

[4] Each DID document can express cryptographic material, verification methods, and service endpoints to enable trusted interactions associated with the DID subject.

A DID document might contain additional semantics about the subject that it identifies.

[7] The AT Protocol and applications powered by the protocol such as Bluesky use DIDs for their identity system in order to give users full control over their identity, including where their data is stored.