@tracepass/dpp-schemas 1.4.0 → 1.5.0

package/README.md

@@ -66,7 +66,8 @@ an ESPR delegated act, or citing an instrument that creates no passport duty at
 (`paints-coatings`, `packaging`, `construction`).
 
 It is not the case that every battery field is required: the template also carries fields that are
-`anticipated` (pending the carbon-footprint and due-diligence implementing acts) and
+`anticipated` (pending the carbon-footprint and due-diligence acts, and — per the
+Commission's data-points guidance v2.0 — the Article 8 recycled-content act) and
 fields that apply only to some battery sub-categories via `validation.requiredBy`.
 
 **`required` means an instrument in force compels the data.** ESPR (EU) 2024/1781 is a
@@ -85,6 +86,37 @@ containing Annex X materials. `conditional` means the instrument compels the fie
 its stated gate is met — so a passport legitimately leaves it empty otherwise. Fields with no
 `requiredBy` apply to the whole category.
 
+## Standards
+
+[`standards.json`](./standards.json) is a registry of the technical standards a field — or
+a DPP system — relates to. A field names them in `regulationRef.standards`, as keys into the
+registry:
+
+```jsonc
+"regulationRef": {
+  "article": "EN 10204, EN 10025, EN 10088 (stainless)",   // human-facing, unchanged
+  "kind": "standard",
+  "standards": ["EN 10204", "EN 10025", "EN 10088"]          // machine-facing
+}
+```
+
+- **A standard never makes a field required.** Only `kind: "legislation"` can. A standard
+  supports a presumption of conformity; it binds nothing on its own.
+- **Only an Official Journal citation confers that presumption.** Entries with
+  `kind: "harmonised-standard"` carry `ojCitation` — the implementing decision and the
+  provisions it covers. Today that is the six CEN/CLC/JTC 24 system standards
+  (EN 18216, 18219, 18220, 18221, 18222, 18223) cited by Implementing Decision (EU)
+  2026/1736 for ESPR Articles 10 and 11. EN 18239 and EN 18246 are still drafts.
+- **National adoptions are aliases, not separate standards.** Every CEN/CENELEC member
+  publishes an EN unchanged (DIN EN 18219, BDS EN …); confirmed ones are listed under
+  `nationalAdoptions`.
+- **`verified: true`** means the title and status were checked against the OJ or the
+  standard's own text. Otherwise `subject` is a descriptive label, not the official title.
+- **Naming a standard is not a conformity claim** — for this dataset or for any system
+  built on it.
+
+`npm run check:standards` fails if any field references a key the registry does not hold.
+
 ## What a field looks like
 
 ```jsonc

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tracepass/dpp-schemas",
-  "version": "1.4.0",
+  "version": "1.5.0",
   "description": "Machine-readable field specifications for EU Digital Product Passports (ESPR) — 13 product categories, 1005 fields, each traced to the article of EU law that mandates it. Pure JSON, no dependencies.",
   "keywords": [
     "digital-product-passport",
@@ -32,6 +32,7 @@
     "schema.json",
     "index.json",
     "instruments.json",
+    "standards.json",
     "units.json",
     "README.md",
     "LICENSE"
@@ -45,6 +46,7 @@
     "validate": "python3 -c \"import json,glob,sys;from jsonschema import Draft202012Validator as V;v=V(json.load(open('schema.json')));bad=0\nfor p in sorted(glob.glob('templates/*.json')):\n    e=list(v.iter_errors(json.load(open(p))));bad+=bool(e);print(('FAIL' if e else 'ok  '),p)\n    [print('     ',str(x.absolute_path),x.message[:120]) for x in e[:3]]\nsys.exit(1 if bad else 0)\"",
     "build:index": "node scripts/build-index.mjs",
     "check:index": "node scripts/build-index.mjs --check",
-    "check": "npm run validate && npm run check:index"
+    "check": "npm run validate && npm run check:index && npm run check:standards",
+    "check:standards": "node scripts/check-standards.mjs"
   }
 }

package/schema.json

@@ -525,6 +525,14 @@
                 "null"
               ],
               "description": "Free-text name when the reference is not EU legislation."
+            },
+            "standards": {
+              "type": "array",
+              "items": {
+                "type": "string"
+              },
+              "uniqueItems": true,
+              "description": "Keys into `standards.json` for the technical standards this field relates to (test method, declaration format, identifier scheme). Relating to a standard never makes a field required — only `kind: legislation` can — and naming one is not a claim of conformity."
             }
           }
         },