From identifiers to trusted interactions.

Distinguish the identifier, its document and its subject.

Proving control of an identifier and establishing a real-world identity are different tasks.

Check authorship and integrity, then decide whether to accept the claim.

Checking a credential protection mechanism differs from deciding whether to trust its issuer.

DID Core supplies a shared model; each method supplies its own rules.

The wallet manages identities and credentials; applications still evaluate requests.

Understand the exchange between an application request and the user’s identity tool.

A visual identifier helps recognition; it is not proof of control.

Domain management and DID methods belong to different layers.

Proving eligibility and transferring an asset are different operations.

A rights object supplies evidence; a service decides which operation it permits.

Separate a verification method from its permitted verification relationship.

HTTP URIs and profile documents offer another identification model.

Separate a login protocol, an identifier and API authorization.

Separate who makes a claim, who it describes, who presents it and who verifies it.

Check validity periods, suspension and revocation separately.

Identify the layer each occupies before comparing combinations.

It describes verification and interaction information, not a biography.

Methods supply operational rules beneath the shared data model.

Resolution finds a document; dereferencing locates a more specific resource.

Recovery depends on the method and the control arrangements already in place.

It coordinates engineering work on specifications and implementations.

Eligibility an application recognizes, not a government travel document.

Separate a verifiable claim, ownership state and service authorization.