Skip to content

Epic: Restore ORUK schedule recurrence interoperability #12

Description

@oughnic

Summary

Track the schedule-model defects affecting HSDS compliance, iCalendar RRULE compatibility, and Schema.org interoperability.

Scope

This epic covers issues #2 through #11:

  • Loss of RRULE completeness in the schedule model
  • Non-conformance with iCalendar RRULE semantics
  • Partial and inconsistent Schema.org Schedule mapping
  • Missing DTSTART anchoring requirements for schedules
  • No support for recurrence termination in schedules
  • No support for complex recurrence patterns
  • Timezone inconsistency and duplication in schedule model
  • Lack of exception handling equivalent to EXDATE
  • Schema regression without backward compatibility strategy
  • Over-reliance on a simplified recurrence model

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions