02 — Standards

seed

Interoperable specifications that bind the primitives from 01-fundamentals/ into concrete formats consumable by heterogeneous software. They change on a scale of years.

Chapters

File	Topic	Status
`01-x509-and-asn1.kmd`	X.509 certificate structure, ASN.1 DER, extensions (SAN, EKU, BasicConstraints), trust path	seed
`02-pades.kmd`	PDF Advanced Electronic Signatures — ETSI EN 319 142. Signature embedded in PDF, LTV, BTLT/LTA	planned
`03-xades.kmd`	XML Advanced Electronic Signatures — ETSI EN 319 132. Used in NF-e, eSocial, ICP-Brasil	planned
`04-cades.kmd`	CMS Advanced Electronic Signatures — ETSI EN 319 122. Basis of PAdES, used in archiving	planned
`05-jades.kmd`	JSON Advanced Electronic Signatures — ETSI EN 319 182. JOSE-friendly equivalent	planned
`06-ocsp-e-crl.kmd`	Certificate revocation: RFC 6960 (OCSP), RFC 5280 §5 (CRL), OCSP stapling, CRLite	planned
`07-jose-cose.kmd`	JWSJWEJWT (RFC 7515-19), COSE (RFC 9052) — signatures and encryption in JSON/CBOR	planned
`08-rfc-3161-timestamping.kmd`	TSAs, token format, long-term validation	planned

How these standards compose

                  ┌─ PAdES (embedded PDF) ───┐
   X.509 cert ───>┤                          ├──> CMS / CAdES ──> ASN.1 DER
                  └─ XAdES (XML envelope) ───┘
                  └─ JAdES (JSON envelope) ──────> JWS ──────────> base64url

   Timestamping (RFC 3161) ───> CMS token ───> embedded in any of the above
   Revocation ──> OCSP response or CRL ──> embedded for LTV

Cross-references

01-fundamentals/ — primitives consumed
03-legislation/ — which standards each jurisdiction recognizes
05-icp-brasil/ — Brazilian profiles (DOC-ICP-15 and related)