<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Document Trust Grade — rubric changelog</title>
    <link>https://documenttrustgrade.org/</link>
    <description>Changes to the rubric behind the Document Trust Grade. Each entry states what changed, why, and which grades would move as a result.</description>
    <language>en</language>
    <lastBuildDate>Thu, 22 Oct 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://documenttrustgrade.org/changelog.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>v0.4.0 — minor</title>
      <link>https://documenttrustgrade.org/v0.4.0</link>
      <guid isPermaLink="true">https://documenttrustgrade.org/v0.4.0</guid>
      <pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate>
      <description>The commercial programme regime is defined by criteria instead of by naming a single list. It now covers any established commercial trust list: one that publishes its admission requirements, requires independent audit of the certificate authorities it admits, and publishes its membership in a form a validator can load. The ceiling stays at B. A validator states which lists it carries; one that carries no commercial list grades such documents as not recognised, and says so.

Grades affected: Up only: a document whose certificate chains to an established commercial trust list other than the one 0.3.x named can rise from D to B, with a validator that carries that list. No grade goes down, so the change is minor under the published policy.</description>
    </item>
    <item>
      <title>v0.3.1 — patch</title>
      <link>https://documenttrustgrade.org/v0.3.1</link>
      <guid isPermaLink="true">https://documenttrustgrade.org/v0.3.1</guid>
      <pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate>
      <description>Wording only. The text now reads as a standard rather than as one validator’s documentation: criteria refer to the trust regimes the scale recognises instead of “we”; the validation status is defined by ETSI EN 319 102-1 (TOTAL-PASSED) rather than by the constant of one validation library; and the note on qualified validation applies to any validator instead of naming Tindom. The eIDAS Article 25 note is shown once, next to how the scale works, instead of twice.

Grades affected: None. A patch under the published policy: no document’s grade can change.</description>
    </item>
    <item>
      <title>v0.3.0 — major</title>
      <link>https://documenttrustgrade.org/v0.3.0</link>
      <guid isPermaLink="true">https://documenttrustgrade.org/v0.3.0</guid>
      <pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate>
      <description>A+ is redefined. It no longer depends on a closed list of markers — only one of the four could be assessed, and only in one signing platform’s evidence format, which a neutral scale should not privilege. A+ now means everything required for A, at the highest ETSI baseline level (B-LTA), with an archive timestamp that is a qualified time stamp and validates, and no material change after signing. Rung titles corrected: B-LTA is part of the ETSI standard, not beyond it, and A is not the standard &quot;met in full&quot;. Embedded evidence packages are still shown with the result but no longer affect the grade.

Grades affected: Up: B-LTA documents with a qualified, valid archive timestamp that were held at A for want of a marker (A → A+). Down: a B-LTA document that reached A+ only through an embedded evidence package while its archive timestamp is not qualified (A+ → A). Major under the published policy for that reason, although no document validated so far is known to be affected.</description>
    </item>
    <item>
      <title>v0.2.0 — major</title>
      <link>https://documenttrustgrade.org/v0.2.0</link>
      <guid isPermaLink="true">https://documenttrustgrade.org/v0.2.0</guid>
      <pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate>
      <description>The published text and the grading code now say the same thing. (1) Signature scope: validation data, timestamps and further signatures added after signing no longer count as content outside the signature — this is how PAdES B-LT and B-LTA are built, and under 0.1.0 it held every such PDF at B. (2) The A+ condition &quot;no post-signing modification&quot; now means no material change, for the same reason. (3) A multi-signature document now reaches A+ only if every signature meets A in full; before, the result could depend on signature order. (4) The B and C criteria list every reason a document lands there, and B requires a timestamp rather than a qualified one — the qualification of the timestamp was never checked. (5) A D now states the grade the file’s own construction would reach with a recognised certificate. (6) Corrected the legal weight of the EU/EEA qualified regime. Released as 0.2.0 because the scale is still pre-release; under the published policy the change is major, since one grade can go down.

Grades affected: Up: PAdES B-LT/B-LTA documents held at B only by signature scope (B → A); B-LTA documents held at A only by permitted additions can reach A+. Down: a multi-signature document graded A+ where one signature was held at A by something other than the missing marker (A+ → A). No change to the letter of a D. Separately, Norwegian BankID SDO files are no longer graded (previously a false F) and are refused as not yet supported.</description>
    </item>
    <item>
      <title>v0.1.0 — initial release</title>
      <link>https://documenttrustgrade.org/v0.1.0</link>
      <guid isPermaLink="true">https://documenttrustgrade.org/v0.1.0</guid>
      <pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate>
      <description>First published version of the scale. Pre-release under semantic versioning: the thresholds have not yet been calibrated against a real distribution of documents, so they may still move.

Grades affected: Not applicable — no earlier version exists.</description>
    </item>
  </channel>
</rss>
