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
55
56
57
58
59
//! `dpp-vc` — the trust layer: who may read a passport, and how that is proven.
//!
//! W3C Verifiable Credentials, `did:web` documents, Bitstring Status List
//! revocation, and the JSON-LD context those are expressed in.
//!
//! Pure (no I/O, no network). Not a `wasm32-unknown-unknown` target: it depends
//! on [`dpp_crypto`], whose RNG requires a platform entropy source.
//!
//! # Trust, not primitives, and not policy
//!
//! Three neighbouring concerns are deliberately **not** here:
//!
//! - **Cryptographic primitives** — JWS, keys, the keystore — are
//! [`dpp_crypto`], which this crate depends on. Signing bytes is a different
//! job from deciding whose signature means what.
//! - **The disclosure contract** — `Audience`, `Disclosure`, the per-field
//! disclosure map and the filter that applies it — describes what a passport
//! *is*, not who is asking. It currently lives in `dpp-crypto::access`; its
//! settled home is `dpp-domain`.
//! - **Projections** — GS1, AAS — render a passport for an ecosystem. They say
//! nothing about trust.
//!
//! The seam this crate sits on: **a credential establishes which `Audience` a
//! caller holds; the disclosure policy maps that `Audience` to fields.** Those
//! are two questions and they are answered in two places.
pub use ;
pub use build_did_document;
pub use ;
pub use LocalIdentityService;
pub use ;
pub use StatusList;
/// Compile-checks this crate's README examples.
///
/// A README example is a public claim about the API, and nothing else in the
/// build compiles one. Without this, a README can advertise a function that
/// does not exist — which is exactly what happened before this harness landed.
;