Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| dido:01-fdis-ra:02-background-and-motivation:02-2-the-fdta-context:02-2-1-fdta-implementation-timeline:start [2026/07/11 00:42] – created nick_dido | dido:01-fdis-ra:02-background-and-motivation:02-2-the-fdta-context:02-2-1-fdta-implementation-timeline:start [2026/07/18 12:33] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 3: | Line 3: | ||
| [[dido: | [[dido: | ||
| - | The [[fxdemo:99_part_annexes: | + | The [[dido:99_annexes: |
| - | The FDTA became law on 23 December 2022 as Title LVIII of the James M. Inhofe National | + | The FDTA became law on 23 December 2022 as Title LVIII of the James M. Inhofe National |
| - | The statute relies on open standards and coordinated standard-setting rather than prescribing specific technologies, | + | The statute relies on open standards and coordinated standard-setting rather than prescribing specific technologies, |
| The FDTA implementation process consists of multiple stages. | The FDTA implementation process consists of multiple stages. | ||
| Line 17: | Line 17: | ||
| * Subsequent agency-specific rulemaking or other agency action to apply applicable standards to particular collections of information | * Subsequent agency-specific rulemaking or other agency action to apply applicable standards to particular collections of information | ||
| - | The final joint rule establishes common data standards for participating agencies. It does not, by itself, change existing reporting requirements or directly apply the standards to every regulated collection of information. Most implementing agencies must subsequently determine, through agency-specific rulemaking or other authorised | + | The final joint rule establishes common data standards for participating agencies |
| - | The final rule also recognises that agencies may tailor the joint standards where permitted or adopt other standards when appropriate under the statutory framework. The implementation timeline, therefore, does not result in a single simultaneous migration to a uniform reporting system. Instead, it establishes a coordinated standards baseline followed by agency-specific implementation decisions, schedules, and transitions. | + | The final rule also recognises that agencies may tailor the joint standards where permitted or adopt other standards when appropriate under the statutory framework |
| The result is a multi-stage rollout extending across several years. During this period: | The result is a multi-stage rollout extending across several years. During this period: | ||
| Line 30: | Line 30: | ||
| * Multiple versions of definitions, | * Multiple versions of definitions, | ||
| - | This staged implementation creates an architectural need to preserve continuity of meaning across versions and reporting periods. Systems need to retain the ability to interpret historical submissions according to the [[fxdemo:99_part_annexes: | + | This staged implementation creates an architectural need to preserve continuity of meaning across versions and reporting periods. Systems need to retain the ability to interpret historical submissions according to the [[dido:99_annexes: |
| - | The final joint rule establishes technical data standards, but it does not define a complete interpretation architecture or prescribe how systems preserve historical semantic context. Agency-specific implementation may also introduce differing scopes, schedules, tailoring decisions, and transition arrangements. | + | The final joint rule establishes technical data standards, but it does not define a complete interpretation architecture or prescribe how systems preserve historical semantic context |
| FDIS-RA addresses the resulting architectural concern by supporting: | FDIS-RA addresses the resulting architectural concern by supporting: | ||
| Line 43: | Line 43: | ||
| * Comparison across reporting periods and implementation versions | * Comparison across reporting periods and implementation versions | ||
| - | These capabilities cannot be achieved through one-time conformance with a schema, taxonomy, identifier standard, or submission format. They require explicit architectural support for semantic versioning, provenance, traceability, | + | These capabilities cannot be achieved through one-time conformance with a schema, taxonomy, identifier standard, or submission format. They require explicit architectural support for semantic versioning, provenance, traceability, |
| ---- | ---- | ||