Data that changes rarely, used for stable product or battery-passport attributes.
Static data matters for DPP and battery-passport architecture because not all passport data has the same update rhythm. Stable product attributes can often be maintained differently from lifecycle, usage, or condition data.
Commission Delegated Regulation (EU) 2022/670 supplementing Directive 2010/40/EU
data that do not change often or on a regular basis
Direct EU definition from intelligent transport systems context; useful for static/dynamic data distinction but not battery-specific.
Reference: Article 2, point 5
These entries are non-verbatim context summaries. They are not presented as public legal definitions.
DIN DKE SPEC 99100:2025-02 — Requirements for data attributes of the battery passport
DIN DKE SPEC 99100 uses static data as implementation context for battery-passport data attributes that have a low update frequency.
Implementation-context summary only; not a verbatim DIN definition. This is a copyrighted standard, so Minespider should use it as standards context rather than republishing the standard text.
Reference: Section 3.19
For implementation, static data should be separated from dynamic data so systems can manage ownership, update cadence, audit trails, and access permissions correctly.
Static data can sound simple because it changes less often, but it still needs governance. The key implementation question is which stable facts can be reused safely across model, batch, or item records, and how those stable facts do not drift away from the batteries they describe when suppliers, documents, or specifications change.