1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
//! DID, key management and verifiable credential primitives.
//!
//! The crate is organised in two layers. The lower layer holds the DID data model ([`did`]), JOSE
//! keys and signatures ([`jose`]), key stores ([`keys`]), the signing party ([`identity`]), DID
//! resolution and dereferencing ([`resolver`]) and the `did:key`, `did:jwk` and `did:web`
//! methods ([`methods`]). The upper layer builds JWT-based verifiable credentials and
//! presentations on top of it ([`vc`]), SD-JWT verifiable credentials ([`sd_jwt_vc`]), the DIF
//! Well Known DID Configuration ([`domain_linkage`]) and DIF Linked Verifiable Presentations
//! ([`linked_vp`]), and never leaks back into the lower layer. [`prelude`] gathers the common
//! types of the lower layer, [`prelude::credentials`] those of the upper layer.
//!
//! # Cargo features
//!
//! All features are additive. The default set enables both layers over software keys and the
//! three DID methods; `--no-default-features` leaves the lower layer with the in-crate
//! parsers and verifiers only. The complete list, with what each feature pulls in, is in the
//! crate's `docs/DESIGN.md`; the ones that add surface rather than enable a module:
//!
//! - `utoipa`: OpenAPI schemas ([`utoipa::ToSchema`]) for [`DidDocument`](did::DidDocument),
//! [`VerificationMethod`](did::VerificationMethod), [`Service`](did::Service),
//! [`Jwk`](jose::Jwk), `DomainLinkageConfiguration` and `TypeMetadata`.
//! - `test-vectors`: [`keys::testsuite`], the behavioural suite every key store must pass, and
//! [`vectors`], the specification vectors the tests of this crate run against.