Document ILM-native timestamping and split SignServer docs into their own section - #320
Document ILM-native timestamping and split SignServer docs into their own section#320ivosh wants to merge 39 commits into
Conversation
Add a consolidated Standards and Compliance reference page and point-of-use citations across the timestamping docs, mapping eIDAS / ETSI / IETF requirements to the ILM mechanisms that implement them. Includes the design spec and review fixes (EN 319 422 title, esi4-qtstStatement-1 ASN.1 name, SigningCertificateV2 attribute). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
|
|
|
Rename provider-interface page to signature-formatting-provider, strip it to interface-level content, and point the connectors table at the concrete Timestamp Formatting Connector implementation.
Add a consolidated Standards and Compliance reference page and point-of-use citations across the timestamping docs, mapping eIDAS / ETSI / IETF requirements to the ILM mechanisms that implement them. Includes the design spec and review fixes (EN 319 422 title, esi4-qtstStatement-1 ASN.1 name, SigningCertificateV2 attribute). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Rename provider-interface page to signature-formatting-provider, strip it to interface-level content, and point the connectors table at the concrete Timestamp Formatting Connector implementation.
…ing APIs These specs are already published at the pinned 2.18.0 apiVersion.
…rotocol APIs Bumps apiVersion to 2.19.0; these specs are not yet published there, so yarn build will fail until interface-documentation 2.19.0 ships.
lubomirw
left a comment
lubomirw
left a comment
There was a problem hiding this comment.
Automated multi-reviewer pass (/pr-multi-review): Copilot CLI, guided-pr-review, superpowers code-review, and hygiene.
The signing → signserver rename, the docusaurus.config.js redirect block, and MDX/frontmatter are all sound — the full Docusaurus build passes with no broken links or anchors. Posting 8 findings inline (1 High, 5 Medium, 2 Low), all documentation/correctness issues in the new timestamping content. Findings were validated against the core, helm-charts, and timestamp-formatting-connector repos; likely-noise and needs-judgment items were filtered out.
lubomirw
changed the title
Reviewer (lubomirw): - time-quality-monitor-configuration: document MESSAGING_TIME_QUALITY_ENABLED enable flag - timestamping-flow: correct profile-resolution caching claim and link to caching page; remove incorrect serial-exhaustion error row (verified against Core) - signing-profile: rename planned "Human Signing" to "Content Signing"; add Certificate -> Token to relationships diagram - limitations: make bound-resource list non-exhaustive, defer to diagram - timestamp-formatting-connector: clarify PORT default 8080 (image) / 8070 (jar) - configuration: mark Qualified Timestamp and Validate Signature as not required - standards-and-compliance: add RFC 6211 normative reference Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
@ivosh the documentation is exhaustive and describes all parts of the implementation, which is great, thank you very much for that, however, it needs updates according to my perspective and provided comments. There is a mix of technical information for deployment and user guides that should be split, and names that should not be used to avoid issues in future maintenance of the docs. I would appreciate if you can take a look into it. |
… feat/ilm-timestamping-docs
… TQM README.md in its repository
…nd TSP protocol APIs" This reverts commit 2a6bc0e.
5 participants
No description provided.