Catholic Open Source
Canonicalization of liturgical event ids #3
Replies: 5 comments 11 replies
-
|
Hi John, I've been working on a liturgical text system since 2010 called BMD (Bible MarkDown) and would like to share some insights from that experience. My Approach: Short Codes vs. Long KeysI faced similar challenges with identifier design. After experimenting with different approaches, I settled on a compact code system:
File naming pattern: Observations on ID DesignFrom my experience, here are some trade-offs to consider:
Recommendations
Example Structure Proposal{
"id": "anthony_of_egypt_abbot",
"short_code": "0117",
"latin": "S. Antonii, abbatis",
"date": {
"month": 1,
"day": 17
},
"rank": "memorial",
"moveable": false,
"martyrology_ref": "RM2004-0117-001"
}My DocumentationI've attached my BMD Fragment System documentation below which describes how I handle:
BMD (Bible MarkDown) Fragment SystemOverviewBMD (Bible MarkDown) is a lightweight markup language and file-based storage system designed specifically for liturgical texts. It extends standard Markdown with specialized symbols for biblical and liturgical notation, optimized for the Liturgy of the Hours (Divine Office). BMD Markup SyntaxPsalm Verse NotationBiblical psalms and canticles use a specialized verse structure with pause markers:
Example - Psalm Structure: The Rubrics and Instructions
Headings
Text Formatting
Biblical ReferencesReferences follow Italian convention: File Naming ConventionPattern 1: Date-based (Sanctoral)
Pattern 2: Liturgical Hour Fragments
Pattern 3: Combined Context
Abbreviation ReferenceLiturgical Hours
Content Elements
Liturgical Seasons
Position Indicators
Directory StructureContent ExamplesPsalm with Full NotationResponsoryPrayer/CollectShort ReadingSaint EntryEncoding
Hash SystemThe numeric suffix (e.g.,
Replacement System (RPL/)The Placeholder Syntax
The pipe character (
Memorial Files (MEM;MMDD.bmd)Memorial files define saint name replacements by calendar date: File Content Example (MEM;0117.bmd): Usage in Template: Alleluia Replacement Files (AL#;#.bmd)Seasonal alleluia variations for Easter/Lent adaptation:
Selector Logic:
Static Placeholders (Static/)The Processing Flow
Special Cases
Empty replacement files indicate dates with dedicated proper texts that don't use common templates. |
Beta Was this translation helpful? Give feedback.
-
|
Wow that's quite a system, you've done a lot of work on this Bible MarkDown Fragment system could live in a repository of its own. Let me create two initial repositories then for the Liturgical event ids, and for the Roman Martyrology. |
Beta Was this translation helpful? Give feedback.
-
|
It's great that you posted examples of OWL and LinkML representations. If we can incorporate both of these kinds of representations into the canonical id repositories, they can work both for the semantic layer and for the data layer. From what I've been reading, LinkML can be directly transformed to python dataclasses and the likes. |
Beta Was this translation helpful? Give feedback.
-
|
I opened the https://github.com/CatholicOS/cledr repo for the liturgical events. But then as I was writing the description, I also realized that the liturgical events also depend on the edition of the Roman Missal in which they were printed. And it would be good to have canonicalized ids for the editions of the Roman Missal that the liturgical events can refer to. So I wound up creating another repository to track this too: https://github.com/CatholicOS/crmetdr. @t1c1 we should talk with Mons. Patrick from the Dicastery for Divine Worship and see if he has any input, I just wrote him a note. |
Beta Was this translation helpful? Give feedback.
-
|
We will need to separate any data repositories from the "canonical id" repositories, and if the data repositories contain copyrighted text (as are the texts of the Roman Missals, Lectionaries, and Liturgy of the Hours), those repositories will need to be private repositories and we will need to gate who has access to them |
Beta Was this translation helpful? Give feedback.
-
|
Instead the canonical id repositories will be open, to allow for contributions from the wider community and from any bishops conference or diocesan Liturgical office that may want to participate (including the Dicastery for Divine Worship of course). |
Beta Was this translation helpful? Give feedback.
-
|
Of course, I'm only putting the IDs I've created so far in the repo. I wanted to point out that there are definitely some spurious IDs at the moment due to spurious fragments. Out of 33,000 IDs, after a cleanup, there could probably be 10,000. Let's just put the rule for creating them, which should be fairly consolidated, although there's certainly still something to consolidate. |
Beta Was this translation helpful? Give feedback.
-
|
I myself was wondering, while creating the frontend forms for allowing a national or diocesan liturgical office to create their own calendars, how the ids should be generated: they should follow a predefined scheme, which is difficult to do if you are trying to generate them based on the name of the celebration. Then I thought, perhaps most of the celebrations that can be defined locally by a Bishops Conference or diocesan liturgy office, are already entries in the Roman Martyrology. So that's where my interest in the Roman Martyrology comes into play. If we also define canonical ids for the Roman Martyrology, then we wouldn't have to worry about finding a way to generate an id that matches a rule or schema, we could preload the martyrology ids in the frontend interface and the liturgy office would choose either an id from the General Roman Calendar or from the martyrology. But then again, the list might not be exhaustive. For example, in Argentina the national patronal feast day is Our Lady of Luján. And this probably does not exist in the Roman Martyrology. So then we would need a way to allow for local celebrations that don't fit into either the General Roman Calendar or the Roman Martyrology, with a custom id that is valid only at the local level, but then again this is not simple: if you generate the id by snake_casing the name of the celebration (perhaps normalizing accented characters), this might not be valid for languages with non Latin characters, such as many Asian languages. Perhaps it would be useful to have a predefined list of all possible local celebrations that don't fit into either the General Roman Calendar or the Roman Martyrology, and define an id in this list before allowing the local liturgy office to create their local calendar? |
Beta Was this translation helpful? Give feedback.
-
|
We could cross-reference entries in the Roman Martyrology that are also in the General Roman Calendar, so as to avoid duplicates when generating a frontend form: the celebrations in the General Roman Calendar (based on the latest Editio Typica plus any celebrations defined via decrees of the Dicastery for Divine Worship issued after the publication of the latest Editio Typica) would have precedence, then any entries from the Roman Martyrology that are not in the first list can be included, and finally entries that are defined at a local level but do not fit into either of the first two lists can be included. |
Beta Was this translation helpful? Give feedback.
-
|
@marcodelpin dealing only with matching the IDs for now, so that we can attempt to match my IDs with other project IDs and work towards a canonicalization from there, I have created a repository https://github.com/JohnRDOrazio/liturgical-calendar-ids. In the |
Beta Was this translation helpful? Give feedback.
-
|
The script |
Beta Was this translation helpful? Give feedback.
-
|
Hello @emagnier , I have mapped the romcal identifiers to the litcal identifiers, currently these are the two open source projects that I know of that have the most complete list of identifiers: https://github.com/CatholicOS/cledr. The only identifier I could not account for is christmas_time_january_8, I'm not sure what celebration this identifier refers to because looking at the Italian lectionary, the weekdays of Christmas only go to January 7; then we start the "weekdays after Epiphany" which can be identified either as Jan 7 - 12 or Mon - Sat after Epiphany (when Epiphany is celebrated on a Sunday, and in fact romcal identifies these as |
Beta Was this translation helpful? Give feedback.
-
|
Hello @JohnRDOrazio, indeed this identifier may be extraneous. I’ll have more time next week to look into this more closely. I’ll keep you posted. |
Beta Was this translation helpful? Give feedback.
-
|
Dear Fr. John, Following up on your request to create similar JSON/MD files matching IDs to names, I've prepared the mapping for the temporale entries. 📋 About the "Missing" Temporale KeysThe 48 entries in 🔧 CLEDR ID FormatExamples:
Tempus Codes:
Dies Codes (Latin planetary notation):
📄 Mappings PreparedI've created complete mapping files for all 48 "missing" temporale entries:
Each entry includes:
❓ Question for DiscussionThis format allows for:
Does this align with your vision for CLEDR? Would you prefer a different format? 📝 Next Steps
Let me know how you'd like to proceed! Marco |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello @CatholicOS/liturgy-working-group team, this is to get the discussion started as regards canonicalization of the ids regarding the Liturgical Calendar events (temporale, sanctorale, etc.) and Saints of the Roman Martyrology. Some of us have already been working with some of this data, so it would be useful to define together a standardized form for the ids. I think we will need more than one repository to handle this, for example:
I'm thinking, we can display a table in the README with the canonical id in one column, and the Latin "name" in a second column.
Then within the repository or repositories, we can include some structured data such as JSON.
When we will have a server with IETF tools, we can work towards an RFC for the canonicalization of this data, but in the meantime working within the repositories will be a good start. Shall we start with two repositories, one for the General Roman Calendar and one for the Martyrology? Or do you think we could use a single repository?
Beta Was this translation helpful? Give feedback.
All reactions