Christian Nennemann
56f2ce669c
Both drafts now live in workspace/drafts/ as siblings:
drafts/
├── act/ (ACT -01, native to parent repo)
│ ├── draft-nennemann-act-01.md kramdown-rfc source
│ ├── draft-nennemann-act-01.{xml,txt,html,pdf}
│ ├── .refcache/ bibxml cache
│ └── build.sh
├── ietf-wimse-ect/ (ECT -02, submodule, PDF added)
│ └── ...
└── README-pdf.md PDF toolchain docs
ACT kramdown-rfc conversion:
- full YAML frontmatter (title, author, refs)
- section structure matches kramdown-rfc conventions
- {{REF}} citation syntax, auto-numbered sections
- references auto-built from normative/informative blocks
- removed manual TOC (kramdown-rfc generates)
- builds cleanly: 133K XML, 89K TXT, 208K HTML, 167K PDF
PDF toolchain:
- xml2rfc --pdf via weasyprint<60 + pydyf<0.10 injected into xml2rfc pipx venv
- both build.sh scripts now produce PDF as Step 4
- README-pdf.md documents the setup for new machines
Submodule: bump ietf-wimse-ect pointer for build.sh PDF step
15 lines
942 B
XML
15 lines
942 B
XML
<reference anchor="RFC7519" target="https://www.rfc-editor.org/info/rfc7519">
|
|
<front>
|
|
<title>JSON Web Token (JWT)</title>
|
|
<author fullname="M. Jones" initials="M." surname="Jones"/>
|
|
<author fullname="J. Bradley" initials="J." surname="Bradley"/>
|
|
<author fullname="N. Sakimura" initials="N." surname="Sakimura"/>
|
|
<date month="May" year="2015"/>
|
|
<abstract>
|
|
<t>JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.</t>
|
|
</abstract>
|
|
</front>
|
|
<seriesInfo name="RFC" value="7519"/>
|
|
<seriesInfo name="DOI" value="10.17487/RFC7519"/>
|
|
</reference>
|