@tracepass/dpp-schemas 1.15.0 → 1.16.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +13 -2
- package/guidance/battery-datapoints-v2.0.json +861 -0
- package/guidance/battery-field-datapoints.json +407 -0
- package/package.json +2 -1
- package/templates/battery.json +14 -19
package/README.md
CHANGED
|
@@ -70,8 +70,10 @@ with required fields; construction's passport points are recorded as obligations
|
|
|
70
70
|
conditional on the delegated act under Reg (EU) 2024/3110 Art. 75(1).
|
|
71
71
|
|
|
72
72
|
It is not the case that every battery field is required: the template also carries fields that are
|
|
73
|
-
`anticipated
|
|
74
|
-
|
|
73
|
+
`anticipated`: data the Commission's data-points guidance v2.0 says is not to be filled or
|
|
74
|
+
displayed at the February 2027 start (carbon footprint, pending its acts; the due-diligence
|
|
75
|
+
report, required from 18 August 2027; recycled-content shares, pending the Article 8 act).
|
|
76
|
+
The dates live in `phasedObligations` (see below). The template also carries
|
|
75
77
|
fields that apply only to some battery sub-categories via `validation.requiredBy`.
|
|
76
78
|
|
|
77
79
|
**`required` means an instrument in force compels the data.** ESPR (EU) 2024/1781 is a
|
|
@@ -121,6 +123,15 @@ data group binds. Where parts of an instrument phase in later, the instrument ca
|
|
|
121
123
|
| `otherDates` | Other dates legitimately tied to the obligation (a postponed original date, later minimum-share steps) |
|
|
122
124
|
| `source` | The primary text or Commission guidance the date comes from, with its edition |
|
|
123
125
|
|
|
126
|
+
For batteries, `guidance/` holds the Commission's own data-point list: DG GROW, *Digital
|
|
127
|
+
Batteries Passport – data point by category*, 2nd edition (15 Aug 2026), as
|
|
128
|
+
`battery-datapoints-v2.0.json` (71 data points × EV / LMT / industrial: `mandatory`,
|
|
129
|
+
`certain-cases`, `optional`, `not-to-be-filled`). `battery-field-datapoints.json` records
|
|
130
|
+
which data point each publish-blocking field carries. Audit check [21] fails any field that
|
|
131
|
+
is required for a category without a mandatory data point behind it, or conditional
|
|
132
|
+
without a mandatory or certain-cases one. Fields the guidance omits but the primary text
|
|
133
|
+
is read to require are listed under `primaryTextOnly`, with the reason.
|
|
134
|
+
|
|
124
135
|
This is the one place those dates are kept. Copy that states them (the TracePass
|
|
125
136
|
marketing site checks every sentence against this registry) and the templates' own
|
|
126
137
|
`anticipated` flags follow it.
|