Skip to content

Feature request: first-class block types for Confession/Reconciliation and Eucharistic Adoration #1

Description

@t1c1

Thanks for TabulaScript — the movable-feast and seasonal handling is exactly what GTFS/RRULE/opening_hours get wrong for parish schedules, and the line-oriented syntax is a pleasure to read.

I'm using it to model Catholic parish schedules at scale (a few hundred parishes across the Archdiocese of Los Angeles, growing). Mass timetables map cleanly. The two things every parish publishes alongside Mass — and that I'd love to express in the same document — are:

  1. Confession / Reconciliation — often "Saturday 3:30–4:30 PM, or by appointment," sometimes "30 minutes before each Mass," and frequently tied to a Holy Hour.
  2. Eucharistic Adoration — recurring windows ("Fri 9 AM–5 PM"), First-Friday patterns, and perpetual (24/7) adoration.

A few questions / requests:

  • Is the intended way to model these today simply additional timetable blocks (e.g. confession: / adoration:) with the host environment defining the block types? If so, a short README example would make that discoverable — right now the docs center on mass: and it's not obvious the same machinery covers other service types.
  • Two recurring patterns that don't fit a fixed time slot cleanly: "by appointment" (no time) and "perpetual / 24h" adoration. Is there a recommended idiom for "available but no fixed slot," or would a sentinel make sense?
  • "Relative to Mass" confession (e.g. "before the 8 AM and 5 PM Masses") is very common — is there a way to reference another block's slots, or is duplicating the times the expected approach?

Happy to contribute examples or a PR for a docs/services.md with confession/adoration recipes if that'd be welcome. Either way, thank you for releasing this.

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