search

igneus / ordodo

generator of *ordo* (combined liturgical calendar for print)
MIT License
3 stars 1 forks source link

Lectionary #1

Open igneus opened 6 years ago

igneus commented 6 years ago

In some countries it is customary that the ordo also contains lectionary data for each celebration.

martindonat commented 6 years ago

Maybe we should continue the discussion here. I think I could help you with this, but maybe you could specify in which way you want to resolve this issue.

igneus commented 6 years ago

Any help is, of course, most welcome. Where do you live / where do you intend to assemble a directory for? I'm 90% sure national lectionaries occasionally differ even in choice of pericopes for common occasions (Sundays, ferials, feasts from the General Roman Calendar).

For Germany there is the API by P. von Hatzfeld, which handles both calendar and lectionary. It wouldn't be that hard to write an adapter for it and integrate it in ordodo. There are probably more useful resources out there, but I haven't done much research yet.

martindonat commented 6 years ago

Interesting. I'm from Germany. I could think of a calendar for dioceses of Trier, Limburg or Erfurt. I didn't know about the API from P. von Hatzfeld - thanks a lot. Trier and Limburg are not included there at the moment.

So, would you prefer to use the API (dynamical, but depended) and include it in ordodo or to have fixed data files, such as:

`

Jer 33, 14-16 ....

`

(I know, liturgical year is missing, I didn't have a look into ordodo's xml structures.)

I could have a look on national differences - actually, I would be surprised if there is so much difference. Differences occur in the abbreviations of biblical books. So I would prefer writing an XML with all lectionary data (latin style) and some localization files with mappings between the abbrevations and the possibility to overwrite the standard lectionary data. What do you think of it?

igneus commented 6 years ago

Integrating the API is something I have planned since I learned about it.

This means that, when using the API as a data source, ordodo would completely rely on the API for calendar computation and would only be responsible for resolution of differences between the various calendars being aggregated (if ordo for multiple dioceses was being generated) and output rendering.

A lectionary-computing library with packaged data is something desirable, too, but it's significantly more work. I would go for the API first. Btw. if data for your dioceses of interest are missing there, you can contribute them.