Summary
The schedule regression removes supported fields without any migration, deprecation, or mapping guidance.
Evidence
The profile patch removes RRULE-related properties directly, while the repository describes the profile process as patching HSDS rather than redefining schedule semantics.
Impact
Technical: existing integrations can break on schema change or lose data during regeneration.
Business: suppliers and councils face migration risk and uncertainty, slowing adoption.
Expected behaviour
Breaking changes should be accompanied by a documented migration path and compatibility guidance.
Suggested resolution
Publish a migration note or compatibility matrix, and define how legacy RRULE fields map into the new schema.
Severity
High
Versioning note
These defects affect the core data model and likely require a breaking change (ORUK v4) to resolve fully. Backward compatibility may be maintained via transformation layers, but not within the current schema design.
Summary
The schedule regression removes supported fields without any migration, deprecation, or mapping guidance.
Evidence
The profile patch removes RRULE-related properties directly, while the repository describes the profile process as patching HSDS rather than redefining schedule semantics.
Impact
Technical: existing integrations can break on schema change or lose data during regeneration.
Business: suppliers and councils face migration risk and uncertainty, slowing adoption.
Expected behaviour
Breaking changes should be accompanied by a documented migration path and compatibility guidance.
Suggested resolution
Publish a migration note or compatibility matrix, and define how legacy RRULE fields map into the new schema.
Severity
High
Versioning note
These defects affect the core data model and likely require a breaking change (ORUK v4) to resolve fully. Backward compatibility may be maintained via transformation layers, but not within the current schema design.