<?xml version='1.0' encoding='UTF-8'?>
<rfc category="exp" docName="draft-watts-scientific-quantity-verification-00" ipr="trust200902" submissionType="IETF" tocInclude="true" tocDepth="3" sortRefs="true" symRefs="true" xml:lang="en" version="3">
  <front>
    <title abbrev="Quantity Verification">Scientific Quantity Records with Digest-Bound Numeric Verification</title>
    <seriesInfo name="Internet-Draft" value="draft-watts-scientific-quantity-verification-00"/>
    <author fullname="Deonté O'dell Watts" initials="D. O." surname="Watts" asciiFullname="Deonte O'dell Watts">
      <organization>GoodShyt Group Inc.</organization>
      <address>
        <postal>
          <city>San Francisco</city>
          <region>CA</region>
          <country>United States of America</country>
        </postal>
        <email>deonte@goodshyt.fun</email>
        <uri>https://orcid.org/0009-0005-8586-3650</uri>
      </address>
    </author>
    <date year="2026" month="11" day="16"/>
    <keyword>scientific data</keyword>
    <keyword>measurement uncertainty</keyword>
    <keyword>units</keyword>
    <keyword>verification</keyword>
    <keyword>JSON</keyword>
    <abstract>
      <t>This document defines a JSON representation for scientific quantities (a decimal value, a unit, and an optional measurement uncertainty) and a binding by which a computed quantity names, by cryptographic digest, the exact input quantities, operation and arithmetic rules it was derived with. It also defines a fail-closed procedure by which a verifier recomputes the value, checks the unit relationship and, for one named method, recomputes the uncertainty, and reports a separate verdict for each aspect. A passing result means only that the stated numbers follow from the stated inputs under the stated rules. It does not establish that a measurement was valid, that the inputs are true, or that any scientific conclusion follows.</t>
    </abstract>
  </front>
  <middle>

    <section anchor="sec-intro">
      <name>Introduction</name>

      <section anchor="sec-problem">
        <name>Problem</name>
        <t>Scientific results are routinely produced by chains of small calculations: lengths are summed, a mass is divided by a volume, uncertainties are combined. When such results are exchanged as JSON, the numbers usually travel as JSON numbers (which many parsers read as IEEE 754 binary64), units travel as free text, uncertainty is absent or informal, and the derivation lives in prose or in code that is not tied to the data it ran on.</t>
        <t>Three problems follow. A derived number cannot be rechecked mechanically against its inputs, because the inputs are named but not pinned. An input that changes after the derivation cannot be detected. And where a result carries a "verified" flag, the flag rarely says what was verified: a record that is well formed, a record whose arithmetic reproduces, and a record that is scientifically sound are three different claims, and a single flag that merges them overstates what was checked.</t>
      </section>

      <section anchor="sec-defines">
        <name>What This Document Defines</name>
        <ul>
          <li>A <em>Quantity Record</em> (<xref target="sec-record"/>): a JSON object holding a decimal value (as a string), a unit, an optional uncertainty, and a statement of how the value was obtained.</li>
          <li>A <em>Trace Binding</em> (<xref target="sec-trace"/>): for a computed quantity, the operation, the exact input records (pinned by the SHA-256 digest of their canonical form), the arithmetic rules and an optional tolerance.</li>
          <li>A <em>numeric verification</em> procedure (<xref target="sec-verify"/>) that recomputes the value, checks the unit relationship and, for one named method, recomputes the uncertainty, reporting a separate verdict for each aspect and failing closed when it cannot decide.</li>
          <li>A <em>Verification Result Record</em> (<xref target="sec-result"/>) that carries those verdicts.</li>
        </ul>
      </section>

      <section anchor="sec-nongoals">
        <name>Non-Goals</name>
        <ul>
          <li>It does not assess whether a measurement was made correctly, whether an instrument was calibrated, or whether an input value is true. A verifier recomputes; it does not observe.</li>
          <li>It does not define a system of units. Units are carried as codes of an external scheme; this version defines UCUM only.</li>
          <li>It does not define authentication or signatures. Quantity Records and Verification Result Records are plain JSON, meant to be carried in or referenced from an authenticated container.</li>
          <li>It does not model correlated inputs, non-linear propagation, Monte Carlo propagation or interval arithmetic. One propagation method is defined.</li>
          <li>It does not define how records are stored, discovered or transported, or how a reference to an input is resolved.</li>
          <li>It does not define arrays, tables or datasets. A Quantity Record holds one scalar quantity.</li>
        </ul>
      </section>
    </section>

    <section anchor="sec-relationship">
      <name>Relationship to Existing Work</name>
      <dl newline="true">
        <dt>SenML</dt>
        <dd>SenML <xref target="RFC8428"/> represents sensor measurements as records with a name, a unit from a registry, and a JSON number as value. It defines no uncertainty member, carries numbers as JSON numbers, and has no notion of a value derived from other records. Quantity Records could be produced from SenML records; that mapping is not defined here (<xref target="sec-open"/>).</dd>
        <dt>D-SI</dt>
        <dd>The Digital System of Units <xref target="D-SI"/> is a machine-readable representation of SI quantities, units and measurement uncertainty developed in the metrology community. It covers the same ground as the value, unit and uncertainty members of a Quantity Record, and a deployment that already uses it should keep using it for that part. This document does not compete with it: the trace binding and the verification procedure are defined over quantities and could equally be defined over D-SI quantities. A unit scheme for D-SI could be added to <xref target="sec-units"/>.</dd>
        <dt>UCUM</dt>
        <dd>UCUM <xref target="UCUM"/> is a case-sensitive code system for units designed to be machine-parsable. It is used here as the one defined unit scheme.</dd>
        <dt>GUM</dt>
        <dd>The Guide to the Expression of Uncertainty in Measurement <xref target="GUM"/> defines the law of propagation of uncertainty from which the one propagation method of this document is taken (<xref target="sec-unc-aspect"/>). This document adds nothing to metrology; it only makes one calculation checkable.</dd>
        <dt>PROV</dt>
        <dd>W3C PROV <xref target="PROV-O"/> can express that one entity was derived from another and which activity produced it. It defines neither numeric recomputation nor pinning of inputs by digest. A trace binding carries that extra information and could be mapped to PROV.</dd>
        <dt>Packaging</dt>
        <dd>BagIt <xref target="RFC8493"/> gives fixity for files, and RO-Crate <xref target="ROCRATE"/> packages files with metadata. Neither gives a typed representation of individual quantities or a recomputation of derived ones.</dd>
        <dt>Attestation</dt>
        <dd>Supply-chain attestation frameworks such as in-toto <xref target="IN-TOTO"/> bind an output to its inputs by digest. The trace binding here applies the same pattern to individual numeric quantities and adds a defined recomputation. The pattern itself is not claimed as new.</dd>
        <dt>Signatures</dt>
        <dd>Authenticity of a record is out of scope. Records can be payloads of signed containers such as JWS <xref target="RFC7515"/> or COSE <xref target="RFC9052"/>, or be the subject of attestation in the sense of <xref target="RFC9334"/>.</dd>
        <dt>Evidence records</dt>
        <dd>The author's documents <xref target="SAER"/>, <xref target="SEA"/>, <xref target="REB"/> and <xref target="VEE"/> are concerned with evidence records, provenance and replication metadata, and source-grounded claims. A record in any of them can reference a Quantity Record by its digest. This document has no dependency on them.</dd>
      </dl>
      <t>In short, the value, unit and uncertainty members are not new, and a deployment with an existing representation should keep it. The contribution of this document is narrower: (1) a digest-bound trace for a single numeric derivation; (2) a verification procedure with per-aspect, fail-closed verdicts, including an explicit NOT_VERIFIABLE; and (3) the rule in <xref target="sec-meaning"/> that a numeric verdict is not a claim about the science.</t>
    </section>

    <section anchor="sec-terms">
      <name>Conventions and Terminology</name>

      <section anchor="sec-bcp14">
        <name>Requirements Language</name>
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
      </section>

      <section anchor="sec-defs">
        <name>Terms</name>
        <dl newline="true">
          <dt>Quantity Record</dt>
          <dd>A JSON object defined in <xref target="sec-record"/>.</dd>
          <dt>Subject</dt>
          <dd>The Quantity Record being verified.</dd>
          <dt>Input</dt>
          <dd>A Quantity Record named by the subject's trace.</dd>
          <dt>Declared value</dt>
          <dd>The number written in a record. <em>Recomputed value</em> is the number a verifier derives from the inputs.</dd>
          <dt>Verifier</dt>
          <dd>A program or service that performs the procedure in <xref target="sec-verify"/>.</dd>
          <dt>Resolver</dt>
          <dd>The mechanism by which a verifier obtains the octets of an input from its <tt>ref</tt>. It is outside this document.</dd>
          <dt>Aspect</dt>
          <dd>One independently reported part of a verification: schema, basis, inputs, unit, value or uncertainty.</dd>
          <dt>Decimal numeral</dt>
          <dd>A string matching <xref target="sec-numerals"/>.</dd>
        </dl>
      </section>

      <section anchor="sec-idents">
        <name>Identifiers</name>
        <t>Several members hold identifiers: operation identifiers, method identifiers and unit schemes. An identifier is a non-empty string. An identifier without a colon is defined by this document or a successor and MUST be one of the values it defines. An identifier containing a colon MUST be an absolute URI <xref target="RFC3986"/> and is an extension point. Identifiers are compared octet for octet.</t>
      </section>
    </section>

    <section anchor="sec-record">
      <name>Quantity Record</name>

      <section anchor="sec-members">
        <name>Members</name>
        <t>A Quantity Record is a JSON object <xref target="RFC8259"/> that conforms to I-JSON <xref target="RFC7493"/>; in particular it MUST NOT contain duplicate member names. The members are:</t>
        <table anchor="tbl-record">
          <name>Members of a Quantity Record</name>
          <thead>
            <tr><th>Member</th><th>Presence</th><th>Value</th></tr>
          </thead>
          <tbody>
            <tr><td>version</td><td>REQUIRED</td><td>The string "0.1".</td></tr>
            <tr><td>quantity_id</td><td>REQUIRED</td><td>Non-empty string identifying the quantity. Uniqueness is not checked by this document.</td></tr>
            <tr><td>quantity_kind</td><td>OPTIONAL</td><td>String naming the kind of quantity, such as "length". Informational.</td></tr>
            <tr><td>basis</td><td>REQUIRED</td><td>One of "measured", "computed", "assumed", "reference" (<xref target="sec-basis"/>).</td></tr>
            <tr><td>value</td><td>REQUIRED</td><td>Decimal numeral held in a string (<xref target="sec-numerals"/>).</td></tr>
            <tr><td>unit</td><td>REQUIRED</td><td>Object (<xref target="sec-units"/>).</td></tr>
            <tr><td>uncertainty</td><td>OPTIONAL</td><td>Object (<xref target="sec-uncertainty"/>).</td></tr>
            <tr><td>trace</td><td>REQUIRED if basis is "computed", otherwise MUST NOT be present</td><td>Trace Binding (<xref target="sec-trace"/>).</td></tr>
            <tr><td>annotations</td><td>OPTIONAL</td><td>Any JSON object. Informational.</td></tr>
          </tbody>
        </table>
        <t>A Quantity Record MUST NOT contain a member that is not listed above. The same closed-member rule applies to every nested object defined in this document except <tt>annotations</tt>. Extension data belongs in <tt>annotations</tt>, whose content is covered by the digest (<xref target="sec-canon"/>) but MUST NOT influence any verdict. Changes to the set of members, or to the meaning of any member, are made by changing <tt>version</tt>.</t>
        <t>The members <tt>quantity_kind</tt> and <tt>role</tt> (<xref target="sec-inputs"/>), and the content of <tt>annotations</tt>, MUST NOT be used to decide any verdict.</t>
      </section>

      <section anchor="sec-numerals">
        <name>Decimal Numerals</name>
        <t>A decimal numeral is a string matching the following ABNF <xref target="RFC5234"/>, which is the JSON number grammar of <xref target="RFC8259"/> held in a string:</t>
        <sourcecode type="abnf">
decimal = [ "-" ] nonneg
nonneg  = int [ frac ] [ exp ]
int     = "0" / ( %x31-39 *DIGIT )
frac    = "." 1*DIGIT
exp     = ( %x65 / %x45 ) [ "-" / "+" ] 1*DIGIT
</sourcecode>
        <t>A leading "+", leading zeros, a leading or trailing ".", hexadecimal, "NaN" and "Infinity" are not decimal numerals. The value of a decimal numeral is the exact rational number it denotes; "-0" denotes zero. Members documented as "non-negative" take the <tt>nonneg</tt> form; members documented as "positive" take the <tt>nonneg</tt> form with a value greater than zero.</t>
        <t>Numbers are held in strings for three reasons:</t>
        <ul>
          <li>JSON numbers are commonly parsed to binary64, which cannot represent most decimal fractions exactly (for example 20.10), so the value a reader recovers can differ from the value written.</li>
          <li>Canonicalization <xref target="RFC8785"/> rewrites JSON numbers in ECMAScript form, which drops trailing zeros (20.10 becomes 20.1). A string is preserved exactly, so the digest of a record changes when and only when the record's text changes.</li>
          <li>The writer's choice of digits stays visible. This document attaches no meaning to trailing zeros: comparisons are numeric (<xref target="sec-value-aspect"/>). Whether trailing zeros denote significant digits is for the uncertainty to say.</li>
        </ul>
        <t>The only JSON number in a Quantity Record is the integer <tt>precision</tt> (<xref target="sec-arith"/>).</t>
      </section>

      <section anchor="sec-units">
        <name>Units</name>
        <t><tt>unit</tt> is an object with two members, both non-empty strings: <tt>scheme</tt> and <tt>code</tt>. This document defines one scheme, "ucum", for which <tt>code</tt> is a case-sensitive expression of <xref target="UCUM"/> (for example "mm", "g/cm3" or "1"). Any other scheme MUST be an absolute URI (<xref target="sec-idents"/>).</t>
        <t>Two units are <em>identical</em> if and only if their scheme and code are equal octet for octet. No normalization is applied: "mm" and "mm " are different units. The unit describes the value; it is not checked against <tt>quantity_kind</tt>.</t>
      </section>

      <section anchor="sec-uncertainty">
        <name>Uncertainty</name>
        <t><tt>uncertainty</tt> is an object with these members:</t>
        <dl newline="true">
          <dt>form (REQUIRED)</dt>
          <dd>"standard": <tt>value</tt> is a standard uncertainty (GUM 2.3.1). "expanded": <tt>value</tt> is an expanded uncertainty U = k u (GUM 2.3.5), with k given by <tt>coverage_factor</tt>. No coverage probability is asserted.</dd>
          <dt>value (REQUIRED)</dt>
          <dd>A non-negative decimal numeral, in the unit of the quantity.</dd>
          <dt>coverage_factor</dt>
          <dd>A positive decimal numeral. REQUIRED if <tt>form</tt> is "expanded"; MUST NOT be present otherwise.</dd>
          <dt>method (OPTIONAL)</dt>
          <dd>An identifier (<xref target="sec-idents"/>) stating how <tt>value</tt> was derived from the inputs' uncertainties. Permitted only when <tt>basis</tt> is "computed". This document defines "gum-first-order-independent" (<xref target="sec-unc-aspect"/>). If <tt>method</tt> is absent the record makes no claim about how the uncertainty was obtained, and the uncertainty aspect is NOT_CLAIMED.</dd>
          <dt>tolerance (OPTIONAL)</dt>
          <dd>A tolerance object (<xref target="sec-tolerance"/>) for comparing <tt>value</tt> with the recomputed uncertainty. If absent the comparison is exact.</dd>
        </dl>
        <t>An uncertainty obtained by measurement or by judgement (Type A or Type B evaluation in GUM terms) has no <tt>method</tt> in this version, because nothing here can recompute it.</t>
      </section>

      <section anchor="sec-tolerance">
        <name>Tolerance</name>
        <t>A tolerance object has a <tt>mode</tt> and, for two modes, a <tt>value</tt> that is a non-negative decimal numeral tau:</t>
        <dl newline="true">
          <dt>"exact"</dt>
          <dd><tt>value</tt> MUST be absent. The declared and recomputed numbers must be equal.</dd>
          <dt>"absolute"</dt>
          <dd>|declared - recomputed| &lt;= tau, in the unit of the quantity.</dd>
          <dt>"relative"</dt>
          <dd>|declared - recomputed| &lt;= tau * |recomputed|.</dd>
        </dl>
        <t>A tolerance is chosen by the producer of the record. A consumer that relies on a bounded tolerance needs its own policy (<xref target="sec-security"/>).</t>
      </section>

      <section anchor="sec-basis">
        <name>Basis</name>
        <dl newline="true">
          <dt>measured</dt>
          <dd>The value was obtained by observation, by a procedure outside this document.</dd>
          <dt>computed</dt>
          <dd>The value was derived by one operation from other Quantity Records, as stated in <tt>trace</tt>.</dd>
          <dt>assumed</dt>
          <dd>The value was adopted by assumption, such as a modelling choice.</dd>
          <dt>reference</dt>
          <dd>The value was taken from an external reference, such as a published constant.</dd>
        </dl>
        <t><tt>basis</tt> is a statement by the producer. This document does not verify it, except that "computed" selects the recomputation of <xref target="sec-verify"/>.</t>
      </section>
    </section>

    <section anchor="sec-trace">
      <name>Trace Binding</name>

      <section anchor="sec-trace-members">
        <name>Members</name>
        <t>The <tt>trace</tt> of a computed quantity is an object with these members: <tt>operation</tt> (REQUIRED, <xref target="sec-ops"/>), <tt>inputs</tt> (REQUIRED, <xref target="sec-inputs"/>), <tt>arithmetic</tt> (REQUIRED, <xref target="sec-arith"/>) and <tt>tolerance</tt> (OPTIONAL, <xref target="sec-tolerance"/>, applied to the value; if absent the comparison is exact).</t>
      </section>

      <section anchor="sec-ops">
        <name>Operations</name>
        <t><tt>operation</tt> is an object with <tt>id</tt> and, for extension operations, <tt>digest</tt>. The core operations are binary and take their operands in the order of <tt>inputs</tt>:</t>
        <table anchor="tbl-ops">
          <name>Core operations</name>
          <thead>
            <tr><th>id</th><th>Result</th></tr>
          </thead>
          <tbody>
            <tr><td>add</td><td>inputs[0] + inputs[1]</td></tr>
            <tr><td>sub</td><td>inputs[0] - inputs[1]</td></tr>
            <tr><td>mul</td><td>inputs[0] * inputs[1]</td></tr>
            <tr><td>div</td><td>inputs[0] / inputs[1]</td></tr>
          </tbody>
        </table>
        <t>An extension operation is identified by an absolute URI and MUST carry a <tt>digest</tt> (<xref target="sec-canon"/>) of the artifact that defines it, such as a specification or an executable. Core operations MUST NOT carry a <tt>digest</tt>. The digest pins which definition the producer meant; it does not give a verifier the ability to run it. A verifier executes only operations it already implements, selected by the pair (id, digest), reports NOT_VERIFIABLE for any other, and MUST NOT fetch and run code named by a record.</t>
      </section>

      <section anchor="sec-inputs">
        <name>Inputs</name>
        <t><tt>inputs</tt> is a non-empty array of objects; for core operations it has exactly two elements. Each element has:</t>
        <dl newline="true">
          <dt>ref (REQUIRED)</dt>
          <dd>A non-empty string passed to the resolver. This document does not interpret it. The digest, not the ref, binds the input.</dd>
          <dt>digest (REQUIRED)</dt>
          <dd>An object <tt>{"alg", "value"}</tt> (<xref target="sec-canon"/>) holding the digest of the input Quantity Record.</dd>
          <dt>role (OPTIONAL)</dt>
          <dd>A string label such as "addend" or "divisor". Informational; operand order is the array order.</dd>
        </dl>
      </section>

      <section anchor="sec-arith">
        <name>Arithmetic</name>
        <t><tt>arithmetic</tt> states how the recomputed value is formed from the exact values of the inputs. It has a <tt>domain</tt>:</t>
        <dl newline="true">
          <dt>"exact"</dt>
          <dd>The result is the exact result of the operation. It is allowed only if that result has a finite decimal expansion. For div this holds if and only if the quotient, in lowest terms, has a denominator whose only prime factors are 2 and 5. <tt>precision</tt> and <tt>rounding</tt> MUST be absent.</dd>
          <dt>"decimal"</dt>
          <dd>The exact result is rounded once, to <tt>precision</tt> significant decimal digits, using <tt>rounding</tt>. <tt>precision</tt> is an integer from 1 to 2^53 - 1. <tt>rounding</tt> is one of "half-even" (nearest, ties to the even digit), "half-up" (nearest, ties away from zero), "down" (toward zero) or "up" (away from zero).</dd>
        </dl>
        <t>Each core operation is a single step, so there is no intermediate rounding. The exponent range is unbounded in the definition; implementations impose limits (<xref target="sec-limits"/>). Binary floating-point arithmetic is not defined in this version (<xref target="sec-open"/>).</t>
      </section>
    </section>

    <section anchor="sec-canon">
      <name>Canonical Form and Digests</name>
      <t>The canonical form of a Quantity Record is its serialization under the JSON Canonicalization Scheme <xref target="RFC8785"/>. Because the only JSON number in a Quantity Record is the integer <tt>precision</tt>, differences in number serialization cannot arise. Member names and string values are serialized as UTF-8 text; no Unicode normalization is applied.</t>
      <t>The digest of a Quantity Record is SHA-256 <xref target="RFC6234"/> over the UTF-8 octets of its canonical form. A <tt>digest</tt> object has two members: <tt>alg</tt>, identifying the hash algorithm, and <tt>value</tt>. This document defines the <tt>alg</tt> value "sha-256", for which <tt>value</tt> is the 32 octets of the digest as 64 lowercase hexadecimal characters:</t>
      <sourcecode type="abnf">
hexdigest = 64( %x30-39 / %x61-66 )
</sourcecode>
      <t>A verifier that does not support the algorithm named MUST NOT substitute another algorithm. It reports NOT_VERIFIABLE (DIGEST_ALG_UNSUPPORTED). Later versions may define further algorithms.</t>
      <t>A digest binds the content of a record. It does not authenticate who produced it (<xref target="sec-security"/>).</t>
    </section>

    <section anchor="sec-verify">
      <name>Numeric Verification</name>

      <section anchor="sec-verdicts">
        <name>Verdicts</name>
        <t>A verifier reports a verdict for each of six aspects: schema, basis, inputs, unit, value and uncertainty.</t>
        <table anchor="tbl-verdicts">
          <name>Aspect verdicts</name>
          <thead>
            <tr><th>Verdict</th><th>Meaning</th></tr>
          </thead>
          <tbody>
            <tr><td>PASS</td><td>The aspect was checked and holds.</td></tr>
            <tr><td>FAIL</td><td>The aspect was checked and does not hold, or the record is malformed.</td></tr>
            <tr><td>NOT_VERIFIABLE</td><td>The verifier could not decide: an input is unavailable, a feature is unsupported, or a resource limit was reached.</td></tr>
            <tr><td>NOT_CLAIMED</td><td>The record makes no assertion that this aspect could check. Used only for the uncertainty aspect.</td></tr>
          </tbody>
        </table>
        <t>The overall verdict is FAILED if any aspect is FAIL; otherwise NOT_VERIFIABLE if any aspect is NOT_VERIFIABLE; otherwise VERIFIED. An aspect that is NOT_CLAIMED does not prevent VERIFIED, so a consumer MUST read the per-aspect verdicts and MUST NOT read VERIFIED as covering an aspect reported as NOT_CLAIMED.</t>
        <t>The procedure fails closed: VERIFIED is produced only when every aspect that applies was positively decided PASS. Any inability to decide yields NOT_VERIFIABLE, never PASS.</t>
      </section>

      <section anchor="sec-procedure">
        <name>Procedure</name>
        <t>The inputs to a verifier are the octets of the subject and a resolver. The verifier performs the following steps in order. An aspect that cannot be decided because an earlier aspect was not PASS is reported NOT_VERIFIABLE with reason PREREQUISITE_NOT_MET. Once the inputs have been resolved, the unit, value and uncertainty aspects are evaluated independently: a FAIL in one MUST NOT prevent the others from being evaluated.</t>
        <ol type="1">
          <li><t>Parse. Parse the octets as JSON. If any object contains a duplicate member name, the schema aspect is FAIL (DUPLICATE_MEMBER). If parsing fails for any other reason, if the text contains a JSON number that is not an integer, or if it contains NaN or Infinity, the schema aspect is FAIL (SCHEMA_INVALID). In both cases the verifier computes the subject digest over the received octets and marks the subject as not canonical (<xref target="sec-result"/>), and the remaining aspects are PREREQUISITE_NOT_MET.</t></li>
          <li><t>Version. If <tt>version</tt> is a string other than one the verifier supports, the schema aspect is NOT_VERIFIABLE (VERSION_UNSUPPORTED).</t></li>
          <li><t>Schema. Check the record against <xref target="sec-record"/> and <xref target="sec-trace"/>, including the closed-member rule. Failure is FAIL (SCHEMA_INVALID); otherwise PASS.</t></li>
          <li><t>Basis. If <tt>basis</tt> is not "computed", the basis aspect is NOT_VERIFIABLE (BASIS_NOT_COMPUTED): nothing is recomputed, so the verifier MUST NOT report VERIFIED. Otherwise PASS.</t></li>
          <li><t>Inputs. For each input in order: obtain its octets from the resolver (if unavailable, NOT_VERIFIABLE with INPUT_UNAVAILABLE); if the digest <tt>alg</tt> is unsupported, NOT_VERIFIABLE with DIGEST_ALG_UNSUPPORTED; parse the octets and compute the digest of the result's canonical form (if the octets do not parse as an I-JSON object, or the digest differs from the pinned value, FAIL with INPUT_DIGEST_MISMATCH); if the input's <tt>version</tt> is unsupported, NOT_VERIFIABLE with VERSION_UNSUPPORTED; if the input is not a valid Quantity Record, FAIL with INPUT_SCHEMA_INVALID. The aspect is FAIL if any input is FAIL, otherwise NOT_VERIFIABLE if any is NOT_VERIFIABLE, otherwise PASS; the reason reported is the first of the deciding kind in input order. The verifier MUST compute the digest over exactly the content it then uses.</t></li>
          <li><t>Operation. If the operation is an extension operation that the verifier does not implement for the given (id, digest), the unit and value aspects are NOT_VERIFIABLE (OPERATION_UNSUPPORTED). The uncertainty aspect is NOT_VERIFIABLE (OPERATION_UNSUPPORTED) if the subject declares an uncertainty <tt>method</tt>, otherwise NOT_CLAIMED. The procedure ends.</t></li>
          <li><t>Unit, value and uncertainty. Evaluate <xref target="sec-unit-aspect"/>, <xref target="sec-value-aspect"/> and <xref target="sec-unc-aspect"/>.</t></li>
        </ol>
        <t>Verification is one hop. The verifier does not verify the inputs' own traces, and the verdict for a subject does not depend on whether its inputs are themselves computed correctly (<xref target="sec-meaning"/>).</t>
      </section>

      <section anchor="sec-unit-aspect">
        <name>Unit Aspect</name>
        <t>For add and sub, the subject and both inputs MUST carry identical units (<xref target="sec-units"/>). Otherwise the aspect is FAIL (UNIT_MISMATCH). This version defines no unit conversion: a conversion is its own computed quantity under an extension operation.</t>
        <t>For mul and div, the verifier needs unit algebra. If the three units all use the scheme "ucum" and the verifier supports the expressions involved, it reduces each unit to a pair (dimension vector, scale factor) relative to the UCUM base units. For mul the subject's pair MUST equal the product of the inputs' pairs (dimension vectors added, scale factors multiplied); for div, the quotient (dimension vectors subtracted, scale factors divided). Scale factors are compared exactly. Equality gives PASS and inequality gives FAIL (UNIT_MISMATCH). Comparing scale factors, and not only dimensions, is essential: the value recomputation applies no conversion, so a result whose unit differs from the combined input units by a power of ten is wrong even when its dimension is right (see vector QV-24 in <xref target="app-table"/>).</t>
        <t>If any unit uses another scheme, or an expression the verifier cannot reduce exactly (for example a non-multiplicative unit such as a temperature on the Celsius scale, an arbitrary unit, or a unit whose definition involves an irrational constant), the aspect is NOT_VERIFIABLE (UNIT_ALGEBRA_UNSUPPORTED). A verifier MUST NOT approximate.</t>
      </section>

      <section anchor="sec-value-aspect">
        <name>Value Aspect</name>
        <t>Let a and b be the exact values of <tt>inputs[0]</tt> and <tt>inputs[1]</tt>, and let r be the recomputed value defined by <xref target="sec-arith"/>:</t>
        <ul>
          <li>For div with b = 0, the aspect is FAIL (DIVISION_BY_ZERO).</li>
          <li>In the "exact" domain, if r has no finite decimal expansion, the aspect is FAIL (EXACT_DOMAIN_VIOLATION).</li>
          <li>If a resource limit prevents the computation, the aspect is NOT_VERIFIABLE (RESOURCE_LIMIT).</li>
          <li>Otherwise the verifier compares the declared value v with r numerically, not as text, under the trace's tolerance (<xref target="sec-tolerance"/>). If v = r the aspect is PASS with match "exact". If v differs from r but is within tolerance, it is PASS with match "within_tolerance". Otherwise it is FAIL (VALUE_MISMATCH). Comparisons use exact rational arithmetic.</li>
        </ul>
      </section>

      <section anchor="sec-unc-aspect">
        <name>Uncertainty Aspect</name>
        <t>If the subject has no <tt>uncertainty</tt> member, or its <tt>uncertainty</tt> has no <tt>method</tt>, the aspect is NOT_CLAIMED. If the method is not one the verifier implements, the aspect is NOT_VERIFIABLE (METHOD_UNSUPPORTED). If an input has no <tt>uncertainty</tt> member, the aspect is NOT_VERIFIABLE (INPUT_UNCERTAINTY_MISSING). If an input's value makes the method undefined (div with a zero divisor), the aspect is NOT_VERIFIABLE (PREREQUISITE_NOT_MET).</t>
        <t>This document defines one method, "gum-first-order-independent". It is the first-order law of propagation of uncertainty (GUM 5.1.2) for uncorrelated inputs. Let x1 and x2 be the values of the inputs, and u1 and u2 their standard uncertainties (an expanded uncertainty is divided by its coverage factor). Define S exactly, in rational arithmetic, as the sum of the squared products of each sensitivity coefficient and its standard uncertainty:</t>
        <sourcecode>
add, sub:  S = u1^2 + u2^2
mul:       S = (x2*u1)^2 + (x1*u2)^2
div:       S = (u1/x2)^2 + (x1*u2/x2^2)^2
</sourcecode>
        <t>The reference uncertainty on the scale of the declared uncertainty is R = k * sqrt(S), with k = 1 for form "standard" and k equal to the coverage factor for form "expanded". Let D be the declared uncertainty value. The verifier decides whether D matches R under the uncertainty's tolerance <em>exactly</em>, without evaluating the square root in finite precision. Because D and R are non-negative, each comparison is equivalent to one on squares, with K = k^2 * S:</t>
        <ul>
          <li>exact: D^2 = K.</li>
          <li>absolute with tau: max(0, D - tau)^2 &lt;= K &lt;= (D + tau)^2.</li>
          <li>relative with tau &lt; 1: (D / (1 + tau))^2 &lt;= K &lt;= (D / (1 - tau))^2.</li>
          <li>relative with tau &gt;= 1: K &gt;= (D / (1 + tau))^2.</li>
        </ul>
        <t>A match gives PASS, with match "exact" if D^2 = K and "within_tolerance" otherwise; no match gives FAIL (UNCERTAINTY_MISMATCH). A square root is generally irrational, so an exact comparison succeeds only when R is a rational number; a producer whose uncertainty is not exactly representable SHOULD declare an explicit tolerance. A verifier MAY report in <tt>recomputed</tt> a decimal approximation of R; the verdict MUST NOT depend on it.</t>
      </section>

      <section anchor="sec-limits">
        <name>Resource Limits</name>
        <t>Exact arithmetic on adversarial input can consume unbounded time and memory. A verifier MUST enforce limits on at least the length of any numeral, the magnitude of any exponent, the working precision, and the number of inputs. When a limit is reached the affected aspect is NOT_VERIFIABLE (RESOURCE_LIMIT). A verifier MUST NOT truncate, round or approximate in order to stay within a limit. This document does not fix the limits; a verifier SHOULD document them, and a Verification Result Record is meaningful only relative to them.</t>
      </section>

      <section anchor="sec-meaning">
        <name>What a Verdict Does Not Mean</name>
        <t>Schema conformance, numeric reproducibility, empirical support and scientific interpretation are different claims and MUST NOT be collapsed into one. A verdict of this document concerns the second only, and then only for one hop. In particular:</t>
        <ul>
          <li>VERIFIED does not mean the measurement was valid, the instrument calibrated, or an input value true. It means the stated numbers follow from the stated inputs under the stated rules.</li>
          <li>PASS for the uncertainty aspect does not mean the inputs are independent, that the first-order method is appropriate for the function, or that the input uncertainties are right. It means D matches what the declared method gives from the declared input uncertainties.</li>
          <li>VERIFIED is not transitive. It says nothing about whether an input that is itself a computed quantity was computed correctly. A consumer that needs that verifies each computed input in turn.</li>
          <li>VERIFIED with the uncertainty aspect NOT_CLAIMED says nothing about the uncertainty.</li>
          <li>A verdict applies to the exact record whose digest the Verification Result Record carries, and to the input records whose digests the trace pins.</li>
          <li>An unauthenticated verdict is not evidence that verification took place (<xref target="sec-security"/>).</li>
        </ul>
      </section>
    </section>

    <section anchor="sec-result">
      <name>Verification Result Record</name>

      <section anchor="sec-result-members">
        <name>Members</name>
        <t>A Verification Result Record is a JSON object that conforms to I-JSON with these members:</t>
        <table anchor="tbl-result">
          <name>Members of a Verification Result Record</name>
          <thead>
            <tr><th>Member</th><th>Value</th></tr>
          </thead>
          <tbody>
            <tr><td>version</td><td>The string "0.1".</td></tr>
            <tr><td>subject</td><td>Object with <tt>digest</tt> (the digest of the subject's canonical form), <tt>quantity_id</tt> (OPTIONAL; present when the subject parsed to an object with a string <tt>quantity_id</tt>), and <tt>canonical</tt> (OPTIONAL; the boolean false, present only when the digest was computed over the received octets because the subject could not be parsed).</td></tr>
            <tr><td>verifier</td><td>Object with string members <tt>id</tt> and <tt>version</tt>.</td></tr>
            <tr><td>checked_at</td><td>RFC 3339 <xref target="RFC3339"/> date-time at which the verification ran.</td></tr>
            <tr><td>aspects</td><td>Object with exactly the six members schema, basis, inputs, unit, value and uncertainty, each an aspect object.</td></tr>
            <tr><td>verdict</td><td>"VERIFIED", "FAILED" or "NOT_VERIFIABLE" (<xref target="sec-verdicts"/>).</td></tr>
          </tbody>
        </table>
        <t>An aspect object has <tt>verdict</tt> (REQUIRED; one of the four aspect verdicts), <tt>reason</tt> (present if and only if the verdict is FAIL or NOT_VERIFIABLE; one of the codes in <xref target="sec-reasons"/>), <tt>match</tt> ("exact" or "within_tolerance"; value and uncertainty aspects when PASS) and <tt>recomputed</tt> (a decimal numeral; value and uncertainty aspects, when the verifier got far enough to compute it). For the value aspect <tt>recomputed</tt> is exact; for the uncertainty aspect it is informative (<xref target="sec-unc-aspect"/>).</t>
        <t>All six aspects are always present. A Verification Result Record is not a Quantity Record and carries no signature; it can be digested and signed by whatever container carries it.</t>
      </section>

      <section anchor="sec-reasons">
        <name>Reason Codes</name>
        <table anchor="tbl-reasons">
          <name>Reason codes</name>
          <thead>
            <tr><th>Code</th><th>Verdict</th><th>Condition</th></tr>
          </thead>
          <tbody>
            <tr><td>DUPLICATE_MEMBER</td><td>FAIL</td><td>An object in the received text has a duplicate member name.</td></tr>
            <tr><td>SCHEMA_INVALID</td><td>FAIL</td><td>The text does not parse as required, or the record violates <xref target="sec-record"/> or <xref target="sec-trace"/>.</td></tr>
            <tr><td>VERSION_UNSUPPORTED</td><td>NOT_VERIFIABLE</td><td>The record's version is not supported.</td></tr>
            <tr><td>BASIS_NOT_COMPUTED</td><td>NOT_VERIFIABLE</td><td>The basis is not "computed"; nothing is recomputed.</td></tr>
            <tr><td>INPUT_UNAVAILABLE</td><td>NOT_VERIFIABLE</td><td>The resolver could not supply an input.</td></tr>
            <tr><td>DIGEST_ALG_UNSUPPORTED</td><td>NOT_VERIFIABLE</td><td>The digest algorithm is not supported.</td></tr>
            <tr><td>INPUT_DIGEST_MISMATCH</td><td>FAIL</td><td>The resolved input does not match its pinned digest.</td></tr>
            <tr><td>INPUT_SCHEMA_INVALID</td><td>FAIL</td><td>The resolved input is not a valid Quantity Record.</td></tr>
            <tr><td>OPERATION_UNSUPPORTED</td><td>NOT_VERIFIABLE</td><td>An extension operation is not implemented.</td></tr>
            <tr><td>UNIT_MISMATCH</td><td>FAIL</td><td>The unit relationship does not hold.</td></tr>
            <tr><td>UNIT_ALGEBRA_UNSUPPORTED</td><td>NOT_VERIFIABLE</td><td>The verifier cannot reduce the units exactly.</td></tr>
            <tr><td>VALUE_MISMATCH</td><td>FAIL</td><td>The declared value is not within tolerance of the recomputed value.</td></tr>
            <tr><td>DIVISION_BY_ZERO</td><td>FAIL</td><td>The divisor is zero.</td></tr>
            <tr><td>EXACT_DOMAIN_VIOLATION</td><td>FAIL</td><td>The exact result has no finite decimal expansion.</td></tr>
            <tr><td>METHOD_UNSUPPORTED</td><td>NOT_VERIFIABLE</td><td>The uncertainty method is not implemented.</td></tr>
            <tr><td>INPUT_UNCERTAINTY_MISSING</td><td>NOT_VERIFIABLE</td><td>An input lacks an uncertainty.</td></tr>
            <tr><td>UNCERTAINTY_MISMATCH</td><td>FAIL</td><td>The declared uncertainty does not match the method's result within tolerance.</td></tr>
            <tr><td>RESOURCE_LIMIT</td><td>NOT_VERIFIABLE</td><td>A verifier limit was reached (<xref target="sec-limits"/>).</td></tr>
            <tr><td>PREREQUISITE_NOT_MET</td><td>NOT_VERIFIABLE</td><td>An earlier aspect prevents this one from being decided.</td></tr>
          </tbody>
        </table>
      </section>
    </section>

    <section anchor="sec-example">
      <name>Worked Example</name>
      <t>Two lengths are measured with a caliper and summed. The numbers are chosen so that the root-sum-square of the two standard uncertainties is exact (0.03^2 + 0.04^2 = 0.05^2), which lets the example use exact tolerance throughout.</t>
      <t>The records are shown formatted for reading. A digest is always computed over the canonical form (<xref target="sec-canon"/>), never over this text. The canonical forms and digests are in <xref target="app-vectors"/>. Long lines are folded as described in <xref target="RFC8792"/>.</t>
      <t>First input:</t>
      <sourcecode type="json">{
  "version": "0.1",
  "quantity_id": "urn:example:qr:length-1",
  "quantity_kind": "length",
  "basis": "measured",
  "value": "12.30",
  "unit": {"scheme": "ucum", "code": "mm"},
  "uncertainty": {"form": "standard", "value": "0.03"}
}</sourcecode>
      <t>Second input:</t>
      <sourcecode type="json">{
  "version": "0.1",
  "quantity_id": "urn:example:qr:length-2",
  "quantity_kind": "length",
  "basis": "measured",
  "value": "7.80",
  "unit": {"scheme": "ucum", "code": "mm"},
  "uncertainty": {"form": "standard", "value": "0.04"}
}</sourcecode>
      <t>The computed quantity. The digests in <tt>inputs</tt> are those of the two records above:</t>
      <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{
  "version": "0.1",
  "quantity_id": "urn:example:qr:length-total",
  "quantity_kind": "length",
  "basis": "computed",
  "value": "20.10",
  "unit": {"scheme": "ucum", "code": "mm"},
  "uncertainty": {
    "form": "standard",
    "value": "0.05",
    "method": "gum-first-order-independent"
  },
  "trace": {
    "operation": {"id": "add"},
    "inputs": [
      {
        "role": "addend",
        "ref": "urn:example:qr:length-1",
        "digest": {
          "alg": "sha-256",
          "value": "8c383922ef0eb4f7934cd847b36fdb82260cbec62eee36c8\
c93b6ee1aca6d348"
        }
      },
      {
        "role": "addend",
        "ref": "urn:example:qr:length-2",
        "digest": {
          "alg": "sha-256",
          "value": "d6922de0395dbd44198dd8b0075b12b9641840d08c94afdb\
c8a45f6a8d733f0a"
        }
      }
    ],
    "arithmetic": {
      "domain": "decimal",
      "precision": 28,
      "rounding": "half-even"
    },
    "tolerance": {"mode": "exact"}
  }
}</sourcecode>
      <t>A verifier given the computed quantity and a resolver that returns the two inputs produces:</t>
      <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{
  "version": "0.1",
  "subject": {
    "quantity_id": "urn:example:qr:length-total",
    "digest": {
      "alg": "sha-256",
      "value": "9c8d5351e878fceaa8a31725f3391da64631b4e1257ed7817f17\
aa1ed741215e"
    }
  },
  "verifier": {"id": "example-verifier", "version": "0.1"},
  "checked_at": "2026-11-16T00:00:00Z",
  "aspects": {
    "schema": {"verdict": "PASS"},
    "basis": {"verdict": "PASS"},
    "inputs": {"verdict": "PASS"},
    "unit": {"verdict": "PASS"},
    "value": {
      "verdict": "PASS",
      "match": "exact",
      "recomputed": "20.1"
    },
    "uncertainty": {
      "verdict": "PASS",
      "match": "exact",
      "recomputed": "0.05"
    }
  },
  "verdict": "VERIFIED"
}</sourcecode>
      <t>The recomputed value is the numeral 20.1, which denotes the same number as the declared 20.10, so the value aspect passes; comparison is numeric, not textual. The recomputed uncertainty is the square root of 0.0009 + 0.0016 = 0.0025, which is 0.05. Both comparisons are exact.</t>
    </section>

    <section anchor="sec-security">
      <name>Security Considerations</name>
      <dl newline="true">
        <dt>Scope of assurance</dt>
        <dd>A verdict is about arithmetic consistency. Anyone can construct input records and a computed record that are consistent with each other and wrong about the world. Consumers MUST NOT treat VERIFIED as evidence that a measurement is valid (<xref target="sec-meaning"/>), and MUST read per-aspect verdicts.</dd>
        <dt>Authenticity</dt>
        <dd>Digests bind records to each other, not to a trusted origin. Without an authenticated container, an attacker can replace a whole chain of records. Records SHOULD be carried in a signed or attested container (<xref target="sec-relationship"/>).</dd>
        <dt>Input substitution and time of check</dt>
        <dd>A resolver can return different content at different times, or different content to the verifier than to a human reader. A verifier MUST compute the digest over exactly the octets it then parses and uses, and MUST NOT fetch an input twice.</dd>
        <dt>Parser differences</dt>
        <dd>JSON parsers differ in how they treat duplicate member names, so one reader can see a different value than another. Duplicate names make a record invalid, and canonicalization requires I-JSON input.</dd>
        <dt>Resource exhaustion</dt>
        <dd>Large exponents, long numerals, large precision and deep nesting can exhaust time or memory in exact arithmetic or parsing. Verifiers MUST enforce limits (<xref target="sec-limits"/>) and SHOULD bound parser depth and input size.</dd>
        <dt>Tolerance</dt>
        <dd>The tolerance is chosen by the producer. A large tolerance makes a wrong value pass. The result reports whether a match was exact or within tolerance; a consumer SHOULD apply its own ceiling on tolerance and treat records that exceed it as not acceptable, whatever the verdict.</dd>
        <dt>Extension operations</dt>
        <dd>A digest on an extension operation pins a definition but does not make it safe to run. A verifier executes only implementations it already trusts, selected by (id, digest), and never code supplied by the record. An unrecognized operation yields NOT_VERIFIABLE, not PASS.</dd>
        <dt>Digest algorithms</dt>
        <dd>The guarantees depend on the collision and second-preimage resistance of SHA-256. A verifier MUST NOT silently substitute a different algorithm for the one named (<xref target="sec-canon"/>), because that would let an attacker choose the weakest.</dd>
        <dt>Unit confusion</dt>
        <dd>Unit errors by a power of ten are common and the value recomputation applies no conversion. The unit aspect therefore compares scale as well as dimension (<xref target="sec-unit-aspect"/>), and returns NOT_VERIFIABLE rather than guessing when it cannot reduce the units exactly.</dd>
        <dt>Uncertainty assumptions</dt>
        <dd>The method assumes uncorrelated inputs and a function that is well approximated to first order. A verifier cannot test either assumption. Two lengths measured with the same instrument share systematic error, and a PASS on the uncertainty aspect does not detect that.</dd>
        <dt>Verifier trust</dt>
        <dd>A Verification Result Record is unsigned and produced by a verifier whose implementation the consumer may not be able to inspect. A consumer that cannot trust the verifier re-runs the procedure itself; all steps are deterministic given the records.</dd>
        <dt>Conversion to binary floating point</dt>
        <dd>A consumer that converts decimal strings to binary64 before using them forfeits the exactness this document provides. Where the digits matter, consumers keep decimal strings.</dd>
      </dl>
    </section>

    <section anchor="sec-privacy">
      <name>Privacy Considerations</name>
      <dl newline="true">
        <dt>Disclosure</dt>
        <dd>Quantity Records can disclose measurement data, and <tt>annotations</tt> and <tt>ref</tt> can disclose instruments, locations, people or infrastructure. Verification requires the verifier to see every input, so a verifier operated by another party receives all of them.</dd>
        <dt>Digests are not hiding</dt>
        <dd>A digest of a record whose content is guessable (a small set of plausible values in a known structure) can be confirmed by trying candidates. A digest MUST NOT be treated as protecting a low-entropy record.</dd>
        <dt>Minimization</dt>
        <dd>Producers SHOULD omit <tt>annotations</tt> and use opaque <tt>ref</tt> values unless there is a reason to disclose more.</dd>
      </dl>
    </section>

    <section anchor="sec-iana">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions. Registries for operation identifiers, method identifiers and unit schemes, and a media type, are listed as open issues (<xref target="sec-open"/>).</t>
    </section>

    <section anchor="sec-impl">
      <name>Implementation Status</name>
      <t>[Note to the RFC Editor: please remove this section, and the reference to RFC 7942, before publication.]</t>
      <t>This section records the state of implementation at the time of writing, in the spirit of <xref target="RFC7942"/>.</t>
      <t>A reference verifier exists, written in Python 3 using only its standard library. It implements <xref target="sec-record"/> to <xref target="sec-result"/>, using exact rational arithmetic for every numeric decision and a small UCUM subset (metre, centimetre, millimetre, gram, kilogram, second and the dimensionless unit, with products, quotients and integer exponents) for unit algebra. It generated every digest, verdict and vector in <xref target="sec-example"/> and <xref target="app-vectors"/>. A randomized self-check compares its decimal rounding with Python's decimal module and its uncertainty comparison with a 60-digit square root, and feeds it a few thousand damaged and hostile inputs, each of which must yield a verdict and never an exception; no mismatches or crashes were found in the runs performed.</t>
      <t>The limits of this evidence are as follows. The verifier has not been publicly released. It has not been run against any independent implementation, so the vectors show internal consistency, not interoperability. The self-check compares two arithmetic back-ends inside one program, which are not independent implementations of this specification. Unit algebra covers only the subset above.</t>
    </section>

    <section anchor="sec-open">
      <name>Open Issues</name>
      <t>[Note to the RFC Editor: please remove this section before publication.]</t>
      <ol type="1">
        <li>Registries for operation identifiers, method identifiers and unit schemes, and a media type for Quantity Records and Verification Result Records. The rule that bare identifiers are reserved (<xref target="sec-idents"/>) anticipates them.</li>
        <li>Binary floating point. Much computation runs in IEEE 754 binary64. Verifying such a result requires the operation order, rounding mode and library behaviour to be part of the trace. A binary64 domain for the four core operations, which IEEE 754 specifies exactly, is a candidate. Functions such as exp and log, whose results IEEE 754 does not fully specify, are not.</li>
        <li>Further propagation methods: correlated inputs with covariance, higher-order terms, interval arithmetic and Monte Carlo propagation <xref target="GUM-S1"/>.</li>
        <li>Further operations: n-ary sums, powers, roots and functions; a unit conversion operation; and full UCUM algebra including non-multiplicative units.</li>
        <li>Verification of the transitive closure of a derivation graph, and how to report it.</li>
        <li>Binding to signature and attestation formats (<xref target="RFC7515"/>, <xref target="RFC9052"/>, <xref target="RFC9334"/>), so that a Verification Result Record can be authenticated.</li>
        <li>A CBOR encoding with deterministic serialization.</li>
        <li>Arrays and tables of quantities that share a unit or uncertainty.</li>
        <li>Mappings from SenML <xref target="RFC8428"/> and D-SI <xref target="D-SI"/> records, and to PROV <xref target="PROV-O"/>.</li>
        <li>Whether trailing zeros should carry a defined meaning as significant digits.</li>
        <li>Minimum limits that every verifier should support, and whether a Verification Result Record should state the limits in force.</li>
      </ol>
    </section>

  </middle>
  <back>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>

        <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119">
          <front>
            <title>Key words for use in RFCs to Indicate Requirement Levels</title>
            <author initials="S." surname="Bradner" fullname="S. Bradner"/>
            <date year="1997" month="March"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="2119"/>
          <seriesInfo name="DOI" value="10.17487/RFC2119"/>
        </reference>

        <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174">
          <front>
            <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
            <author initials="B." surname="Leiba" fullname="B. Leiba"/>
            <date year="2017" month="May"/>
          </front>
          <seriesInfo name="BCP" value="14"/>
          <seriesInfo name="RFC" value="8174"/>
          <seriesInfo name="DOI" value="10.17487/RFC8174"/>
        </reference>

        <reference anchor="RFC3339" target="https://www.rfc-editor.org/info/rfc3339">
          <front>
            <title>Date and Time on the Internet: Timestamps</title>
            <author initials="G." surname="Klyne" fullname="G. Klyne"/>
            <author initials="C." surname="Newman" fullname="C. Newman"/>
            <date year="2002" month="July"/>
          </front>
          <seriesInfo name="RFC" value="3339"/>
          <seriesInfo name="DOI" value="10.17487/RFC3339"/>
        </reference>

        <reference anchor="RFC3986" target="https://www.rfc-editor.org/info/rfc3986">
          <front>
            <title>Uniform Resource Identifier (URI): Generic Syntax</title>
            <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee"/>
            <author initials="R." surname="Fielding" fullname="R. Fielding"/>
            <author initials="L." surname="Masinter" fullname="L. Masinter"/>
            <date year="2005" month="January"/>
          </front>
          <seriesInfo name="STD" value="66"/>
          <seriesInfo name="RFC" value="3986"/>
          <seriesInfo name="DOI" value="10.17487/RFC3986"/>
        </reference>

        <reference anchor="RFC5234" target="https://www.rfc-editor.org/info/rfc5234">
          <front>
            <title>Augmented BNF for Syntax Specifications: ABNF</title>
            <author initials="D." surname="Crocker" fullname="D. Crocker" role="editor"/>
            <author initials="P." surname="Overell" fullname="P. Overell"/>
            <date year="2008" month="January"/>
          </front>
          <seriesInfo name="STD" value="68"/>
          <seriesInfo name="RFC" value="5234"/>
          <seriesInfo name="DOI" value="10.17487/RFC5234"/>
        </reference>

        <reference anchor="RFC6234" target="https://www.rfc-editor.org/info/rfc6234">
          <front>
            <title>US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)</title>
            <author initials="D." surname="Eastlake 3rd" fullname="D. Eastlake 3rd"/>
            <author initials="T." surname="Hansen" fullname="T. Hansen"/>
            <date year="2011" month="May"/>
          </front>
          <seriesInfo name="RFC" value="6234"/>
          <seriesInfo name="DOI" value="10.17487/RFC6234"/>
        </reference>

        <reference anchor="RFC7493" target="https://www.rfc-editor.org/info/rfc7493">
          <front>
            <title>The I-JSON Message Format</title>
            <author initials="T." surname="Bray" fullname="T. Bray" role="editor"/>
            <date year="2015" month="March"/>
          </front>
          <seriesInfo name="RFC" value="7493"/>
          <seriesInfo name="DOI" value="10.17487/RFC7493"/>
        </reference>

        <reference anchor="RFC8259" target="https://www.rfc-editor.org/info/rfc8259">
          <front>
            <title>The JavaScript Object Notation (JSON) Data Interchange Format</title>
            <author initials="T." surname="Bray" fullname="T. Bray" role="editor"/>
            <date year="2017" month="December"/>
          </front>
          <seriesInfo name="STD" value="90"/>
          <seriesInfo name="RFC" value="8259"/>
          <seriesInfo name="DOI" value="10.17487/RFC8259"/>
        </reference>

        <reference anchor="RFC8785" target="https://www.rfc-editor.org/info/rfc8785">
          <front>
            <title>JSON Canonicalization Scheme (JCS)</title>
            <author initials="A." surname="Rundgren" fullname="A. Rundgren"/>
            <author initials="B." surname="Jordan" fullname="B. Jordan"/>
            <author initials="S." surname="Erdtman" fullname="S. Erdtman"/>
            <date year="2020" month="June"/>
          </front>
          <seriesInfo name="RFC" value="8785"/>
          <seriesInfo name="DOI" value="10.17487/RFC8785"/>
        </reference>

        <reference anchor="UCUM" target="https://ucum.org/ucum">
          <front>
            <title>The Unified Code for Units of Measure (UCUM)</title>
            <author initials="G." surname="Schadow" fullname="G. Schadow"/>
            <author initials="C. J." surname="McDonald" fullname="C. J. McDonald"/>
            <date/>
          </front>
        </reference>
      </references>

      <references>
        <name>Informative References</name>

        <reference anchor="RFC7515" target="https://www.rfc-editor.org/info/rfc7515">
          <front>
            <title>JSON Web Signature (JWS)</title>
            <author initials="M." surname="Jones" fullname="M. Jones"/>
            <author initials="J." surname="Bradley" fullname="J. Bradley"/>
            <author initials="N." surname="Sakimura" fullname="N. Sakimura"/>
            <date year="2015" month="May"/>
          </front>
          <seriesInfo name="RFC" value="7515"/>
          <seriesInfo name="DOI" value="10.17487/RFC7515"/>
        </reference>

        <reference anchor="RFC7942" target="https://www.rfc-editor.org/info/rfc7942">
          <front>
            <title>Improving Awareness of Running Code: The Implementation Status Section</title>
            <author initials="Y." surname="Sheffer" fullname="Y. Sheffer"/>
            <author initials="A." surname="Farrel" fullname="A. Farrel"/>
            <date year="2016" month="July"/>
          </front>
          <seriesInfo name="BCP" value="205"/>
          <seriesInfo name="RFC" value="7942"/>
          <seriesInfo name="DOI" value="10.17487/RFC7942"/>
        </reference>

        <reference anchor="RFC8428" target="https://www.rfc-editor.org/info/rfc8428">
          <front>
            <title>Sensor Measurement Lists (SenML)</title>
            <author initials="C." surname="Jennings" fullname="C. Jennings"/>
            <author initials="Z." surname="Shelby" fullname="Z. Shelby"/>
            <author initials="J." surname="Arkko" fullname="J. Arkko"/>
            <author initials="A." surname="Keranen" fullname="A. Keranen"/>
            <author initials="C." surname="Bormann" fullname="C. Bormann"/>
            <date year="2018" month="August"/>
          </front>
          <seriesInfo name="RFC" value="8428"/>
          <seriesInfo name="DOI" value="10.17487/RFC8428"/>
        </reference>

        <reference anchor="RFC8493" target="https://www.rfc-editor.org/info/rfc8493">
          <front>
            <title>The BagIt File Packaging Format (V1.0)</title>
            <author initials="J." surname="Kunze" fullname="J. Kunze"/>
            <author initials="J." surname="Littman" fullname="J. Littman"/>
            <author initials="E." surname="Madden" fullname="E. Madden"/>
            <author initials="J." surname="Scancella" fullname="J. Scancella"/>
            <author initials="C." surname="Adams" fullname="C. Adams"/>
            <date year="2018" month="October"/>
          </front>
          <seriesInfo name="RFC" value="8493"/>
          <seriesInfo name="DOI" value="10.17487/RFC8493"/>
        </reference>

        <reference anchor="RFC8792" target="https://www.rfc-editor.org/info/rfc8792">
          <front>
            <title>Handling Long Lines in Content of Internet-Drafts and RFCs</title>
            <author initials="K." surname="Watsen" fullname="K. Watsen"/>
            <author initials="E." surname="Auerswald" fullname="E. Auerswald"/>
            <author initials="A." surname="Farrel" fullname="A. Farrel"/>
            <author initials="Q." surname="Wu" fullname="Q. Wu"/>
            <date year="2020" month="June"/>
          </front>
          <seriesInfo name="RFC" value="8792"/>
          <seriesInfo name="DOI" value="10.17487/RFC8792"/>
        </reference>

        <reference anchor="RFC9052" target="https://www.rfc-editor.org/info/rfc9052">
          <front>
            <title>CBOR Object Signing and Encryption (COSE): Structures and Process</title>
            <author initials="J." surname="Schaad" fullname="J. Schaad"/>
            <date year="2022" month="August"/>
          </front>
          <seriesInfo name="STD" value="96"/>
          <seriesInfo name="RFC" value="9052"/>
          <seriesInfo name="DOI" value="10.17487/RFC9052"/>
        </reference>

        <reference anchor="RFC9334" target="https://www.rfc-editor.org/info/rfc9334">
          <front>
            <title>Remote ATtestation procedureS (RATS) Architecture</title>
            <author initials="H." surname="Birkholz" fullname="H. Birkholz"/>
            <author initials="D." surname="Thaler" fullname="D. Thaler"/>
            <author initials="M." surname="Richardson" fullname="M. Richardson"/>
            <author initials="N." surname="Smith" fullname="N. Smith"/>
            <author initials="W." surname="Pan" fullname="W. Pan"/>
            <date year="2023" month="January"/>
          </front>
          <seriesInfo name="RFC" value="9334"/>
          <seriesInfo name="DOI" value="10.17487/RFC9334"/>
        </reference>

        <reference anchor="GUM" target="https://www.bipm.org/en/committees/jc/jcgm/publications">
          <front>
            <title>Evaluation of measurement data - Guide to the expression of uncertainty in measurement</title>
            <author><organization>Joint Committee for Guides in Metrology</organization></author>
            <date year="2008"/>
          </front>
          <seriesInfo name="JCGM" value="100:2008"/>
        </reference>

        <reference anchor="GUM-S1" target="https://www.bipm.org/en/committees/jc/jcgm/publications">
          <front>
            <title>Evaluation of measurement data - Supplement 1 to the "Guide to the expression of uncertainty in measurement" - Propagation of distributions using a Monte Carlo method</title>
            <author><organization>Joint Committee for Guides in Metrology</organization></author>
            <date year="2008"/>
          </front>
          <seriesInfo name="JCGM" value="101:2008"/>
        </reference>

        <reference anchor="PROV-O" target="https://www.w3.org/TR/prov-o/">
          <front>
            <title>PROV-O: The PROV Ontology</title>
            <author initials="T." surname="Lebo" fullname="T. Lebo" role="editor"/>
            <author initials="S." surname="Sahoo" fullname="S. Sahoo" role="editor"/>
            <author initials="D." surname="McGuinness" fullname="D. McGuinness" role="editor"/>
            <date year="2013" month="April"/>
          </front>
          <refcontent>W3C Recommendation</refcontent>
        </reference>

        <reference anchor="D-SI" target="https://doi.org/10.5281/zenodo.3522631">
          <front>
            <title>Digital System of Units (D-SI)</title>
            <author><organization>SmartCom project (EMPIR)</organization></author>
            <date year="2019" month="November"/>
          </front>
          <seriesInfo name="DOI" value="10.5281/zenodo.3522631"/>
        </reference>

        <reference anchor="ROCRATE" target="https://www.researchobject.org/ro-crate/">
          <front>
            <title>RO-Crate Metadata Specification</title>
            <author><organization>RO-Crate community</organization></author>
            <date/>
          </front>
        </reference>

        <reference anchor="IN-TOTO" target="https://github.com/in-toto/attestation">
          <front>
            <title>in-toto Attestation Framework</title>
            <author><organization>in-toto project</organization></author>
            <date/>
          </front>
        </reference>

        <reference anchor="SAER" target="https://datatracker.ietf.org/doc/draft-watts-scientific-admissibility-evidence/">
          <front>
            <title>Scientific Admissibility Evidence Record</title>
            <author initials="D. O." surname="Watts" fullname="Deonte O'dell Watts"/>
            <date year="2026" month="September"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-watts-scientific-quantity-verification-00"/>
          <refcontent>Work in Progress</refcontent>
        </reference>

        <reference anchor="SEA" target="https://datatracker.ietf.org/doc/draft-watts-scientific-evidence-admissibility/">
          <front>
            <title>Scientific Evidence Admissibility</title>
            <author initials="D. O." surname="Watts" fullname="Deonte O'dell Watts"/>
            <date year="2026" month="October"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-watts-scientific-quantity-verification-00"/>
          <refcontent>Work in Progress</refcontent>
        </reference>

        <reference anchor="REB" target="https://datatracker.ietf.org/doc/draft-watts-research-evidence-bundle/">
          <front>
            <title>A Research Evidence Bundle JSON Envelope for Provenance and Replication Metadata</title>
            <author initials="D. O." surname="Watts" fullname="Deonte O'dell Watts"/>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-watts-scientific-quantity-verification-00"/>
          <refcontent>Work in Progress</refcontent>
        </reference>

        <reference anchor="VEE" target="https://datatracker.ietf.org/doc/draft-watts-veriflow-evidence-envelope/">
          <front>
            <title>Veriflow Evidence Envelope for Source-Grounded Computational Claims</title>
            <author initials="D. O." surname="Watts" fullname="Deonte O'dell Watts"/>
            <date year="2026"/>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-watts-scientific-quantity-verification-00"/>
          <refcontent>Work in Progress</refcontent>
        </reference>
      </references>
    </references>

    <section anchor="app-vectors">
      <name>Test Vectors</name>
      <t>All values in this appendix were produced by the reference verifier described in <xref target="sec-impl"/>. They demonstrate that the procedure is deterministic and self-consistent; they have not been confirmed by a second implementation. Long lines are folded as described in <xref target="RFC8792"/>.</t>

      <section anchor="app-digests">
        <name>Digests of the Fixture Records</name>
        <t>Each digest below is the SHA-256 of the canonical form of the record with that <tt>quantity_id</tt> (<xref target="sec-canon"/>), as lowercase hexadecimal. The first three records are those of <xref target="sec-example"/>.</t>
        <sourcecode>urn:example:qr:length-1
  8c383922ef0eb4f7934cd847b36fdb82260cbec62eee36c8c93b6ee1aca6d348
urn:example:qr:length-2
  d6922de0395dbd44198dd8b0075b12b9641840d08c94afdbc8a45f6a8d733f0a
urn:example:qr:length-total
  9c8d5351e878fceaa8a31725f3391da64631b4e1257ed7817f17aa1ed741215e
urn:example:qr:mass
  5ff8de217c76bd8c749979bfd109b9e693a6058a89f3dc85cfb362d0f2e7924e
urn:example:qr:volume
  751564fc6f75f0c68d8c49e6766764fdac46ddf2df9cccbbed258199083396f7
urn:example:qr:density
  5f4ba284dbfd77c17c27823af7cfe71a163f08020c9731f1eca5609a83fe6e4e
urn:example:qr:a
  913d56e48a757af9f9d443ef87a37295c96e861a542c866907ac4b158bc02807
urn:example:qr:b
  2a8faacaeb444c30f1595adca780992e25cb152e1db3fcbd6ce1b570703ac27e
urn:example:qr:ratio
  1b3151d819bfc7af106d21c3fc18a90d92687e7f61d910c0c31d417135b92499
urn:example:qr:l
  a5cb080607ee26f0cf7d3994fa8a7cf3e8f95b281c1e7acf8f624d0314e520d3
urn:example:qr:w
  9fdec5f26ae9aeb03732a568ef277d521e0561603740ae0a31e1f511e856ea30
urn:example:qr:area
  bfb111f1d9cc22fb3c4ad3c91b6d0d295f9a69e99e5baafe95f89fb71288b0eb</sourcecode>
      </section>

      <section anchor="app-canonical">
        <name>Canonical Forms of the Fixture Records</name>
        <t>The canonical form is shown for each record, so that an implementation can check its own canonicalization and digests. The pinned digests inside the computed records are those listed in <xref target="app-digests"/>.</t>
                <t><tt>urn:example:qr:length-1</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"measured","quantity_id":"urn:example:qr:length-1","quantit\
y_kind":"length","uncertainty":{"form":"standard","value":"0.03"},"u\
nit":{"code":"mm","scheme":"ucum"},"value":"12.30","version":"0.1"}</sourcecode>
        <t><tt>urn:example:qr:length-2</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"measured","quantity_id":"urn:example:qr:length-2","quantit\
y_kind":"length","uncertainty":{"form":"standard","value":"0.04"},"u\
nit":{"code":"mm","scheme":"ucum"},"value":"7.80","version":"0.1"}</sourcecode>
        <t><tt>urn:example:qr:length-total</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"computed","quantity_id":"urn:example:qr:length-total","qua\
ntity_kind":"length","trace":{"arithmetic":{"domain":"decimal","prec\
ision":28,"rounding":"half-even"},"inputs":[{"digest":{"alg":"sha-25\
6","value":"8c383922ef0eb4f7934cd847b36fdb82260cbec62eee36c8c93b6ee1\
aca6d348"},"ref":"urn:example:qr:length-1","role":"addend"},{"digest\
":{"alg":"sha-256","value":"d6922de0395dbd44198dd8b0075b12b9641840d0\
8c94afdbc8a45f6a8d733f0a"},"ref":"urn:example:qr:length-2","role":"a\
ddend"}],"operation":{"id":"add"},"tolerance":{"mode":"exact"}},"unc\
ertainty":{"form":"standard","method":"gum-first-order-independent",\
"value":"0.05"},"unit":{"code":"mm","scheme":"ucum"},"value":"20.10"\
,"version":"0.1"}</sourcecode>
        <t><tt>urn:example:qr:mass</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"measured","quantity_id":"urn:example:qr:mass","quantity_ki\
nd":"mass","uncertainty":{"form":"standard","value":"0.05"},"unit":{\
"code":"g","scheme":"ucum"},"value":"12.50","version":"0.1"}</sourcecode>
        <t><tt>urn:example:qr:volume</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"measured","quantity_id":"urn:example:qr:volume","quantity_\
kind":"volume","uncertainty":{"form":"standard","value":"0.02"},"uni\
t":{"code":"cm3","scheme":"ucum"},"value":"5.00","version":"0.1"}</sourcecode>
        <t><tt>urn:example:qr:density</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"computed","quantity_id":"urn:example:qr:density","quantity\
_kind":"density","trace":{"arithmetic":{"domain":"decimal","precisio\
n":28,"rounding":"half-even"},"inputs":[{"digest":{"alg":"sha-256","\
value":"5ff8de217c76bd8c749979bfd109b9e693a6058a89f3dc85cfb362d0f2e7\
924e"},"ref":"urn:example:qr:mass","role":"dividend"},{"digest":{"al\
g":"sha-256","value":"751564fc6f75f0c68d8c49e6766764fdac46ddf2df9ccc\
bbed258199083396f7"},"ref":"urn:example:qr:volume","role":"divisor"}\
],"operation":{"id":"div"}},"uncertainty":{"form":"standard","method\
":"gum-first-order-independent","tolerance":{"mode":"relative","valu\
e":"0.001"},"value":"0.01414"},"unit":{"code":"g/cm3","scheme":"ucum\
"},"value":"2.5","version":"0.1"}</sourcecode>
        <t><tt>urn:example:qr:a</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"measured","quantity_id":"urn:example:qr:a","quantity_kind"\
:"length","unit":{"code":"mm","scheme":"ucum"},"value":"10","version\
":"0.1"}</sourcecode>
        <t><tt>urn:example:qr:b</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"measured","quantity_id":"urn:example:qr:b","quantity_kind"\
:"length","unit":{"code":"mm","scheme":"ucum"},"value":"3","version"\
:"0.1"}</sourcecode>
        <t><tt>urn:example:qr:ratio</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"computed","quantity_id":"urn:example:qr:ratio","quantity_k\
ind":"ratio","trace":{"arithmetic":{"domain":"exact"},"inputs":[{"di\
gest":{"alg":"sha-256","value":"913d56e48a757af9f9d443ef87a37295c96e\
861a542c866907ac4b158bc02807"},"ref":"urn:example:qr:a"},{"digest":{\
"alg":"sha-256","value":"2a8faacaeb444c30f1595adca780992e25cb152e1db\
3fcbd6ce1b570703ac27e"},"ref":"urn:example:qr:b"}],"operation":{"id"\
:"div"}},"unit":{"code":"1","scheme":"ucum"},"value":"3.333333333","\
version":"0.1"}</sourcecode>
        <t><tt>urn:example:qr:l</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"measured","quantity_id":"urn:example:qr:l","quantity_kind"\
:"length","unit":{"code":"m","scheme":"ucum"},"value":"2","version":\
"0.1"}</sourcecode>
        <t><tt>urn:example:qr:w</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"measured","quantity_id":"urn:example:qr:w","quantity_kind"\
:"length","unit":{"code":"cm","scheme":"ucum"},"value":"3","version"\
:"0.1"}</sourcecode>
        <t><tt>urn:example:qr:area</tt>:</t>
        <sourcecode type="json">=============== NOTE: '\' line wrapping per RFC 8792 ================

{"basis":"computed","quantity_id":"urn:example:qr:area","quantity_ki\
nd":"area","trace":{"arithmetic":{"domain":"decimal","precision":28,\
"rounding":"half-even"},"inputs":[{"digest":{"alg":"sha-256","value"\
:"a5cb080607ee26f0cf7d3994fa8a7cf3e8f95b281c1e7acf8f624d0314e520d3"}\
,"ref":"urn:example:qr:l"},{"digest":{"alg":"sha-256","value":"9fdec\
5f26ae9aeb03732a568ef277d521e0561603740ae0a31e1f511e856ea30"},"ref":\
"urn:example:qr:w"}],"operation":{"id":"mul"}},"unit":{"code":"cm2",\
"scheme":"ucum"},"value":"6","version":"0.1"}</sourcecode>
      </section>

      <section anchor="app-table">
        <name>Vectors</name>
        <t>Each vector verifies one subject with a resolver holding the unmodified fixture inputs, except where the case says otherwise. QV-01 to QV-19 and QV-25 use the records of <xref target="sec-example"/>; QV-20 to QV-22 use the density records, QV-23 the exact-domain records, and QV-24 the area records.</t>
        <table anchor="tbl-vectors">
          <name>Test vectors</name>
          <thead>
            <tr><th>ID</th><th>Case</th><th>Overall</th><th>Aspects that decide</th></tr>
          </thead>
          <tbody>
            <tr><td>QV-01</td><td>Section 9 example, unmodified</td><td>VERIFIED</td><td>all aspects PASS</td></tr>
            <tr><td>QV-02</td><td>Value written "20.100" instead of "20.10"</td><td>VERIFIED</td><td>all aspects PASS</td></tr>
            <tr><td>QV-03</td><td>Value "20.11"</td><td>FAILED</td><td>value: VALUE_MISMATCH</td></tr>
            <tr><td>QV-04</td><td>Value "20.14", tolerance absolute 0.05</td><td>VERIFIED</td><td>value: within tolerance</td></tr>
            <tr><td>QV-05</td><td>Value "20.16", tolerance absolute 0.05</td><td>FAILED</td><td>value: VALUE_MISMATCH</td></tr>
            <tr><td>QV-06</td><td>Uncertainty "0.04" instead of "0.05"</td><td>FAILED</td><td>uncertainty: UNCERTAINTY_MISMATCH</td></tr>
            <tr><td>QV-07</td><td>Uncertainty without a method member</td><td>VERIFIED</td><td>uncertainty: NOT_CLAIMED</td></tr>
            <tr><td>QV-08</td><td>Result unit "cm" with input units "mm"</td><td>FAILED</td><td>unit: UNIT_MISMATCH</td></tr>
            <tr><td>QV-09</td><td>First input record changed after its digest was pinned</td><td>FAILED</td><td>inputs: INPUT_DIGEST_MISMATCH</td></tr>
            <tr><td>QV-10</td><td>Second input record cannot be resolved</td><td>NOT_VERIFIABLE</td><td>inputs: INPUT_UNAVAILABLE</td></tr>
            <tr><td>QV-11</td><td>Extension operation the verifier does not implement</td><td>NOT_VERIFIABLE</td><td>unit, value, uncertainty: OPERATION_UNSUPPORTED</td></tr>
            <tr><td>QV-12</td><td>Subject has basis measured (the first input)</td><td>NOT_VERIFIABLE</td><td>basis: BASIS_NOT_COMPUTED</td></tr>
            <tr><td>QV-13</td><td>Member name "value" appears twice</td><td>FAILED</td><td>schema: DUPLICATE_MEMBER</td></tr>
            <tr><td>QV-14</td><td>"value" is a JSON number</td><td>FAILED</td><td>schema: SCHEMA_INVALID</td></tr>
            <tr><td>QV-15</td><td>Working precision 100000</td><td>NOT_VERIFIABLE</td><td>value: RESOURCE_LIMIT</td></tr>
            <tr><td>QV-16</td><td>Input digest algorithm "sha-512"</td><td>NOT_VERIFIABLE</td><td>inputs: DIGEST_ALG_UNSUPPORTED</td></tr>
            <tr><td>QV-17</td><td>"version" is "0.2"</td><td>NOT_VERIFIABLE</td><td>schema: VERSION_UNSUPPORTED</td></tr>
            <tr><td>QV-18</td><td>Undefined top-level member "comment"</td><td>FAILED</td><td>schema: SCHEMA_INVALID</td></tr>
            <tr><td>QV-19</td><td>Added "annotations" member</td><td>VERIFIED</td><td>all aspects PASS</td></tr>
            <tr><td>QV-20</td><td>Density m/V, g and cm3, unit algebra available</td><td>VERIFIED</td><td>uncertainty: within tolerance</td></tr>
            <tr><td>QV-21</td><td>Density with result unit "kg/m3", value unchanged</td><td>FAILED</td><td>unit: UNIT_MISMATCH; uncertainty: within tolerance</td></tr>
            <tr><td>QV-22</td><td>Density with value "2.51"</td><td>FAILED</td><td>value: VALUE_MISMATCH; uncertainty: within tolerance</td></tr>
            <tr><td>QV-23</td><td>10 mm / 3 mm in the exact domain, value declared as a decimal</td><td>FAILED</td><td>value: EXACT_DOMAIN_VIOLATION; uncertainty: NOT_CLAIMED</td></tr>
            <tr><td>QV-24</td><td>2 m times 3 cm declared as "6" cm2</td><td>FAILED</td><td>unit: UNIT_MISMATCH; uncertainty: NOT_CLAIMED</td></tr>
            <tr><td>QV-25</td><td>Declared value "1E+5000"</td><td>NOT_VERIFIABLE</td><td>value: RESOURCE_LIMIT</td></tr>
          </tbody>
        </table>
        <t>Notes:</t>
        <ul>
          <li>QV-02, QV-04 and QV-20 show numeric comparison and tolerance matching; QV-07 shows VERIFIED with the uncertainty aspect NOT_CLAIMED; QV-19 shows that <tt>annotations</tt> changes the digest but not the verdict.</li>
          <li>QV-15 and QV-25 assume a verifier whose precision limit is below 100000 and whose exponent limit is below 5000.</li>
          <li>QV-20 to QV-24 need UCUM unit algebra. A verifier without it reports the unit aspect NOT_VERIFIABLE (UNIT_ALGEBRA_UNSUPPORTED) for each; the overall verdicts are then NOT_VERIFIABLE for QV-20, QV-21 and QV-24, and remain FAILED for QV-22 and QV-23.</li>
          <li>QV-24 is a scale error: 2 m times 3 cm is 6 m.cm, which is not 6 cm2, although both have the dimension of area.</li>
        </ul>
      </section>
    </section>

  </back>
</rfc>