If a person has developed their own lectionary (ie using the XML file format that is documented), does this work fine in Logos 4?
I have not gotten it work and have yet to get an answer on this during beta testing. The new Lectionaries are "real" Logos4 books, so probably they will have to be converted somehow, but I really do not know.
If I had to level a guess, I'd say that this is going to be post 2nd quarter of 2010. It may indeed come in with the updated PBB functionality. But it's only a guess.
Like you Kenneth, I asked questions about timeliness and other XML files during beta but strangly those were never answered.... Is it time for tinfoil hats?
Here Here ... this "lacting feature" is enough for me to keep on using Libronix 3.0
The Catholic lectionary furnished with 4.0 (yes I upgraded) has ONLY sunday lectionaries ... It sure is hard to keep up / promote / develop a habit of daily lectionary reading when it occurs only on one out of seven days ... I thought 4.0 was supposed to help you get into the bible[:)]
Steve Egge
I noted the same thing - also that the responsorial psalm has been omitted. The RCL has a daily version as well now so the oversight is even more significant. In that user generated timelines are a "wait for it" feature, I fear that lectionaries are in the same boat.
It also appears that the lectionary/ordo connection is too tight. I can find a way to access the votive readings.
I assume you mean timelines? [:)]
Bob wrote (http://community.logos.com/forums/p/1804/13898.aspx#13898):
In a post 4.0 release; they'll move to a "compile" model like PBB, because we'll index them with your other user-created content.
As for user-created lectionaries: I'm not sure what the plan for those is in future updates to 4.0, sorry. In 4.0, lectionaries are actually Logos resources, not just XML files, which makes supporting the existing files a little hard than it was in LDLS3.
While I'm not privy to the details, somewhere back in the last 2 days of the forum, I think Bob P. assured me that some type of user-supplied lectionaries will be supported. If not, I promise to clog LOGOS email with Excel spread sheets full of lectionary entries ... including everything I think should be included. I'm actually working on the Jewish cycle of readings now - current practice is find but the primary Pericope scholars' site has a notation I'm still trying to puzzle out.
Well that's unfortunate. That's a huge disadvantage for ver 4, I use the lectionary to drive my Bible reading, and the Logos version is inadequate. Consider me on the sidelines re: upgrade to version 4.
Do you use a custom lectionary, or simply one we don't have in the system?
If it's a standard lectionary and you send it to us, and it doesn't have rights issues, we can add it to the system. Support for your own editable lectionaries will come in the future.
Bob, the BCP Daily lectionary I created and distributed via the old newsgroups is from the Book of Common Prayer of the Episcopal Church USA, and by their canon law is freely reproducable. (II.3.6.b.2 - it was copyrighted, but copyright was relinquished upon adoption)
They understandably request that users acknowledge the source, but you can use it as you like. In fact, that is why I produced the xml version. I am Lutheran, but our derived version of that does not have the same blanket permission.
Now, of course, if you wish to produce a complete Book of Common Prayer, I am sure many of us wouldn't mind.
I use a custom one I produced. It's a Catholic daily and Sunday, I wrote software to scrape the USCCB web site for verse numbers to build it. It includes vestment colors, options and all seasons, and includes things like multiple gospel readings on Palm Sunday, and variations on readings for Charistmas and Easter Vigil vs. Sunday masses plus other options.There are no copyright issues with this version as I take no text from anyone.
The Logos Catholic lectionary has some other issues, for example it does not include Psalm readings which are part of the Mass.
Second, for example Ascension Sunday, there are two sets of readings forwhich the reader picks the appropriate one for their diocese, as someparts of the country celebrate the Seventh Sunday of Easter, and otherparts (most actually) celebrate Ascension this Sunday. The LogosCatholic lectionary does not have Sunday Ascension readings. This is because the bishops have the authority to change feast days in their own diocese.
Mine needs to be updated about 4 times a year, as the lectionary defies any algorithm, I can figure out with a normal liturgical calendar, saint feasts which override, and variations of days like Ash Wednesday, Easter, Triduum, etc. I could probably do a year-version of one without too much effort though, it's just easier to web-scrape and generate the file 4x a year.
I sent a copy of mine to Phil Gons a while ago (around May of this year), we were discussing my project before Logos came out with the Sunday Catholic version. I was interested in converting it to a binary non-XML version like the Logos lectionaries. In fact, I sent him a follow-up this morning asking whether anything existed to convert the lectionary to ver 4 format, I would be happy to play around and test/verify it.
as the lectionary defies any algorithm, I can figure out with a normal liturgical calendar, saint feasts which override, and variations of days like Ash Wednesday, Easter, Triduum, etc.
I strongly believe that the lectionary data should be accessible by liturgical day name AND that the software should not attempt to provide anything but the basic calendar. To explain the problem: Start with the Roman Lectionary --> adjust for America --> adjust for West Coast --> adjust for Seattle Archidiocese --> adjust for Domincan parish --> adjust for collision of adjustments ...
Therefore for each lectionary Logos carries (Jewish or Christian) I think that Logos should simply show both possibilities - Liturgical year and sanctoral cycle and let the user determine what applies to them. I also would like to have the votive readings available via query even though they are never shown in the calendar.
Agree with Martha on all points
I would like to just say I would really appreciate a full Catholic Lectionary. I was a little disappointed to see that it only included Sundays. I further disagree that the lectionary defies any algorithm, it is just a complex algorithm at times.
I confess -- we don't have lectionary experts on staff. We have some employees who go to churches that follow the lectionary, but I don't think we have anyone who understands at Martha's level.
In Logos 4, lectionaries are books in which the Bible references are "replacable" with the text of the passage:
Title of Day
Whatever I want
More text: <John 3:1-10>
Another label: <Gen 1-2>
The software then replaces the references in <> with the text of the passage. And instead of trying to implement algorithms to get the right day/reading/etc., this time we just built a book with entries a few years into the future.
We can pretty easily build more lectionaries if we get data in a similar format. If you want to provide some, that would be fantastic. Or if you'd like to help us understand it better, providing web links or being available for a phone call would be helpful.
Thanks!
Phil also has my email from when I developed a daily Catholic Lectionary for v3.
I'm happy to help - and with a few of us we can produce variants for different countries.
I will do whatever is needed to help build a fully functional lectionary.
Information which I sent to Phil when creating my lectionary in September 08:
A few difficulties with the Catholic Lectionary:It has 3 years of Sundays and 2 years of Weekday readings - so there are six possible permutations (A1,A2,B1,B2,C1,C2). I haven't started on the weekdays in ordinary time yet, these use the same Gospel but different first readings and psalms (I'd love to be able to use the Year-id for this).The Lectionary in use in the USA is slightly different from the Lectionary used in the rest of the English speaking world. I'm an Aussie, so I'm actually using the rest-of-the-world one. The differences are minor and can be easily changed, consisting of slight differences in where pericopae start and end.Each country has different Calendars - This is not surprising, Australia Day is not a public holiday in the US and Thanksgiving is not a holiday here. We also remember different saints (St Patrick is the Patron of Australia). These differences are also easily tracked.The Catholic Calendar is mighty complicated - with a complex ranking system! I'm grateful to universalis.com for one version (though not 100% correct). A web-page listing the General Calendar followed by national calendars is:http://www.nationmaster.com/encyclopedia/Roman-Catholic-calendar-of-saints. I know that it's right for Australia - can't verify the USA one. Some countries celebrate Epiphany and Ascension on Sundays. Some dioceses in the US celebrate Ascension on a Sunday and some celebrate it on the traditional Thursday.Occasionally, instead of a psalm, we recite a canticle. It would be good to have this option in the reading types.On feast days, practice varies whether one uses the prayers and readings of the saint or the prayers of the saint and the readings of the day (eg Monday of the 3rd Week in Ordinary Time - Year I). It is necessary in the calendar to offer both sets.There are occasions (such as the last 7 days of Advent), when the prayers related to particular saints may be said but the readings are never to be used. I can find no way to list the title of the saint and the <description> tag without also including a set of readings. Not an insurmountable problem but a bit deceptive.I'm not sure of the value of the "dawn" "day" "evening" set-ids. These don't actually show up anywhere on the lectionary viewer.I'd love for the <title> to be in bold. It disappears on the page more than a bit. The date is BIG and BOLD - the actual celebration is a bit hard to find.When there are two sets of readings, thre is no space between them in the Lectionary viewer - it looks very crowded.
I don't know if this ever got anywhere as I never received a response
Thanks for your input Damian. I think that Logos may have headed the correct direction by treating lectionaries as a book. That means that one can find the entries through a search ... this allows for finding entries that apply in specific locales or for particular order without making the calendar try to handle them. I think this is an excellent choice - to try to handle the calendar beyond the basics is too complex to be cost effective. I say that even knowing that there are some reasonably decent shareware "solutions".
I intend to send Logos the Jewish reading cycle soon - my schedule has been more hectic than I intended. I'm working on it because the reading cycle for the Torah also represents the early Biblical divisions (prior to chapter-verse). I also want to see if I can get the named Torah readings into the topic db with web references.
If you work the Catholic side, I'll try to push on some of the others.
One additional item I want to push is the recognition of the readings of the lectionaries as pericopes in pericope comparisons etc.
I do think that most of the problems with the L3 lectionary have been addressed - but we'll verify with actual data.
Here is my temporary solution.....
Create a link on your "desktop" to http://www.usccb.org/nab/today.shtml for the united states catholic lectionary. (go to the link in IE and then drag the "url icon" to your desktop to make a link)
Then drag the desktop link to the toolbar in Libronix 4.0.
Not an elegant solution ... but it works. I'm still hoping for an upgrade of the Catholic Lectionary (currently Sunday only) to include the daily catholic lectionary that is on par with what is on the USCCB site. Having the "Sunday only" version just reminds me of its shortcomings
Steve
... to try to handle the calendar beyond the basics is too complex to be cost effective. I say that even knowing that there are some reasonably decent shareware "solutions".
We have a dedicated liturgical program in Australia with all prayers and readings for each day (and sanctoral cycle readily accessible). Sadly, it comes with a version of another bible program which I uninstall. It also produces perfectly dreadful handouts
The real benefit is that we get the Jerusalem Bible texts as well as the CEV (used for the children's lectionary).
I tried suggesting that they changed over to Logos as the partner for the bible side (this program is enormous in Oz / NZ with hundreds / thousands of parishes using it) but was met with the telephone equivalent of a blank stare.
I'm not so sure that all the issues I raised have been addressed. Then, there is the question of who is providing the proofing. On November 1st we were offered the readings for the 31st Sunday in Ordinary Time and not the readings for All Saints.
I assume you mean timelines? Smile
Re: All Saints
In the RCL we got both. It wasn't clear which readings were for which, but they all were there.
However, navigation through the lectionary is still awkward at times. As Dale D pointed out, the Lectionary feature is still much more useful in 3.0 than 4.0, even if they are books in 4.0.
Then, there is the question of who is providing the proofing. On November 1st we were offered the readings for the 31st Sunday in Ordinary Time and not the readings for All Saints.
I agree that there are still some problems - but the design approach is much more solid. It appears that if the data was supplied it will handle the various antiphons, Liturgy of the Hours etc. I'm a little over half way done with the Jewish Torah reading cycle. If it can be handled in a reasonable manner (note reasonable not perfect), Logos will at least be far enough along to make it worth my time to convert other lectionaries into spread sheets.
And trust me, I will needle them on errors I think they should be able to handle. [:)]
Where is the RCL? I cannot find it and even if I could, I can't figure out how to change to homepage from the Catholic Lectionary.
Monroe,
1. Open your library
2. Type title:"revised common lectionary" in your navigation bar
3. Right click the appropriate entry and select "prioritize this resource"
4. Restart Logos
Second, for example Ascension Sunday, there are two sets of readings for which the reader picks the appropriate one for their diocese, as some parts of the country celebrate the Seventh Sunday of Easter, and other parts (most actually) celebrate Ascension this Sunday. The Logos Catholic lectionary does not have Sunday Ascension readings. This is because the bishops have the authority to change feast days in their own diocese.
Don, the option for celebrating Ascension on Sunday is included in the 4.0 Catholic Lectionary.
Moreover, as Martha notes, some of the problems with variations are eased a bit with the 4.0 format. Although dates are given, the Contents Pane is simply organized by Year and Sunday/Feast, so you can easily find where you want to go. We don't currently have data for votives (see below), but I think we could easily integrate them into the 4.0 book by placing them at the end.
Most of the limitations of our Catholic Lectionary (no psalms, no daily lectionary, lack of feasts including All Saints--hence the wrong readings for Sunday, Nov. 1--etc.) are due to limitations of the data set we have. We're still hoping to get a more complete set. I would have to defer to someone more knowlegable about the rights issues involved, but suffice it to say that although this data is available on web (and from several users), Logos is a bit more careful about just grabbing such material and making it our own. I'll do some follow up on this to see if we can work with the USCCB to get more complete data (or permission to use what's out there).
Also, not to contradict the boss, but even if we don't have top liturgical experts in Bellingham, Logos has at least two former Benedictine novices on staff. I hope we're not total slouches [:)].
All kidding aside, please don't think your concerns fall on deaf (or tone-deaf ... or even psalm-tone-deaf) ears.
NJB and CEV available in Logos...
I think that in evaluating Logos 4 implementation of lectionaries we need to keep in mind that there are two separate issues/resources:
The Lectionary should be, I believe, complete and accurate ... and carefully identified i.e. not just "Roman Catholic Lectionary" but specifically Australian, Canadian, ... so that people are not misled. Ordos, on the other hand, should be on a "good enough" basis - if we need greater accuracy we can purchase other software and add a shortcut (when shortcuts actually work all the time. [:)]). We always need to go back to a true lectionary site anyway to check for incipits, etc.
The only real problem that I have found with the current lectionary implementation is on the attaching of notes.
Choice in window
Reference
Selection
Bible
on citation (general)
on text (specific)
Lectionary
calendar date (specific)
liturgical date (general)
Sorry - cut and paste had some problems.
I've held off creating notes on the lectionary hoping that this inconsistency will be fixed.
I understand Logos' concerns regarding copyrights although I would be surprised if the citations (opposed to the texts) are copyright in any major denominations. What I think we need to do is:
have the lectionary specify a permissible translation (US: NAB; Canada:NRSV(?))
I'm not sure what you mean by this Martha?
The lectionaries are already keyed to particular translations. The Catholic Lectionary is keyed to the NAB. This ensures that the pericopae are correct (right click on a reference in the Lectionary to see NAB clearly displayed).
Wrt the Catholic Lectionary pericopae, copyright is simply not a problem.
The first thing that I would do if I were the Logos person in charge of Lectionaries would be to contact Fr Felix Just of Loyola and read all the information on his site concerning lectionaries (http://catholic-resources.org/)
When I click on the Lectionary, it pops up in my favorite translation not the NAB for the USA or the NRSV for Canada or ... It would be more accurate for the translation being used to be specified on each citation so that differences in versification does not lead you to the wrong boundaries. I am particular aware of this at the moment because I'm working with lectionaries based on the JPS (I think).
This is particularly interesting in the USA lectionary immediately preceding our current one - rubrics allowed the use of 4 translations.
When I click on the Lectionary, it pops up in my favorite translation not the NAB for the USA or the NRSV for Canada or ... It would be more accurate for the translation being used to be specified on each citation so that differences in versification does not lead you to the wrong boundaries. I am particular aware of this at the moment because I'm working with lectionaries based on the JPS (I think). This is particularly interesting in the USA lectionary immediately preceding our current one - rubrics allowed the use of 4 translations.
I'm glad that it uses my preferred translation because the NJB is the closest I can come to the JB.
But, it follows the versification of the system default (the NAB in the Catholic Lectionary case):
I'm glad that it uses my preferred translation
Me, too, though it's because I don't particularly like the NAB. Thanks for showing me where the reference base is - I'd not thought to click.
The Lectionary should be, I believe, complete and accurate ... and carefully identified i.e. not just "Roman Catholic Lectionary" but specifically Australian, Canadian, ... so that people are not misled.
Someone from outside the States could correct me, but, as it stands, with only the Sunday data and the ability to choose your own translation, there's very little that's specifically American about our Catholic Lectionary. If we're ever able to add readings from the sanctoral calendar, we may have to add appropriate qualifications.
As for being complete, please keep in mind that what we currently have is simply derived from the 3.0 lectionary reports, which usually have data derived from charts of readings--more a quick reference and devotional aid for getting Sunday's readings (and studying them in Logos) than an authoritative or exhaustive source. The 4.0 format gives us much more flexibility, so we certainly have the capability for much more, but a "real" lectionary, as complete as a print edition, and organized by propers and commons, would probably be a heftier project for us with fewer people who understand how to use it. (Not saying we can't dream ... just keeping expectations realistic.)
I'm afraid I'm not quite following you. In the context menu, the "Reference" is giving the current active data type reference. Bibles are indexed by Bible reference (Bible data type), lectionaries are indexed by date (YearMonthDay data type). "Selection" gives the text you have highlighted. You're wanting to attach a note that appears at every instance of, say, "Second Sunday of Advent" just as you might do for a verse in the Bible?
I'm not quite so sure. I'm no expert, but I don't see any particular reason why the substance of an arrangement of scripture readings, such as the Ordo Lectionum Missae, wouldn't be subject the normal laws ruling intellectual property, even if, in practice, the information is shared quite freely. At any rate, I have confirmed with our Publisher Relations department (who are quite knowledgable about such things) that we're seeking permissions to more complete data for the Catholic Lectionary.
Someone from outside the States could correct me, but, as it stands, with only the Sunday data and the ability to choose your own translation, there's very little that's specifically American about our Catholic Lectionary..
Louis, some of the pericopae vary. Did you look at the site to which I referred you of Fr Just.
As for being complete,
We have different solemnities...
As for being complete...
Obviously, without Psalms / Canticles, they are not complete.
I'm no expert, but I don't see any particular reason why the substance of an arrangement of scripture readings, such as the Ordo Lectionum Missae, wouldn't be subject the normal laws ruling intellectual property, even if, in practice, the information is shared quite freely. At any rate, I have confirmed with our Publisher Relations department (who are quite knowledgable about such things) that we're seeking permissions to more complete data for the Catholic Lectionary.
This is true. But, until the last years of JPII, all documents in their original form (not the translations) were released with no copyright claim. It's very possible that the American version, because its pericopae vary from the universal calendar may be under copyright (or the USCCB may chose to exercise their rights under copyright laws).
If you need someone to contact wrt these issues, I can refer you. One of my close priest friends was a member of the International Committee on English in the Liturgy until its unfortunate demise.
Damian,
Thanks for the clarification. I'm familiar with Fr. Just's site, but haven't specifically reviewed his information on regional differences. I mainly had calendar and translation differences in mind, but the adjustments to the selections made by the US bishops would, of course, make our data specifically American at those points.
As to solemnities, most differences there won't become an issue until some of the holes in our data are filled ...
I'll follow up on rights to the universal Ordo. I'm not sure if this was precluded for some reason or if, working in an American context, we just didn't think to pursue it.
there's very little that's specifically American about our Catholic Lectionary.
Damian correctly pointed out that the basic lectionary is approved at the "National Conference of Bishops" level. I think you may wish to support the Roman typico lectionary and those of the major countries of your customers. The local and religious orders, when provided to you, should be simple, partial overlays to the standard. For details between US and Canadian see http://catholic-resources.org/Lectionary/Differences-Canada-USA.htm
You're wanting to attach a note that appears at every instance of, say, "Second Sunday of Advent" just as you might do for a verse in the Bible?
Exactly, if you look at resources such as the Lectionary Reflections sold by Logos, the primary method of indexing is by liturgical date. This is the primary item to which notes would be attached. For a few things, such as homilies, the actual calendar date is important but it is, in general, secondary.
I don't see any particular reason why the substance of an arrangement of scripture readings, such as the Ordo Lectionum Missae, wouldn't be subject the normal laws ruling intellectual property
I agree you should double-check. However, it is common in such materials for the published edition to specifically allow reuse of the tables while retaining the copyright on the actual translation (with any additional editting for the lectionary). There is also a fair amount of lectionary material especially in the Lutheran and Anglican traditions in which any copyright claim has long since expired.
lectionaries are indexed by date (YearMonthDay data type)
This statement concerns me, if I understand it correctly. To support historic lectionaries (unfortunately, the best source of these is now off-line) only liturgical dates are really applicable. Obviously, I wouldn't expect this to be linked into the lectionary home page display, but I would expect to have them behave as lectionaries in the library.
Eventually I would like the lectionary to include all the Scripture of a particular liturgical day - i.e. the antiphons and the Liturgy of the Hours. My dream, which I believe the current Logos approach supports, is to be able to have the passage guide give me the use of a passage throughout history in the major liturgical traditions. I am anxiously awaiting the PBB tool for such use.
At any rate, I have confirmed with our Publisher Relations department (who are quite knowledgable about such things) that we're seeking permissions to more complete data for the Catholic Lectionary.
I would hope that you are also working to bring us:
If Logos can handle all of these, it can handle anything I can think of to throw at it. Note, I would expect only the first two to appear linked to calendar date. Thanks with your patience with me on these issues.
You might be reading too much into what I'm saying, which is only that the lectionary resources we have use calendar dates to support finding the current reading (or next week's reading, etc.) so that they work somewhat like the 3.0 lectionary report. These resources are organized primarily for that use rather than the sort of comparative liturgical study you seem to have in mind. There's no technical reason we couldn't make a resource organized like a print lectionary or otherwise, but it would be a different animal.
Thanks for the suggestions for other lectionaries to look into.
There's no technical reason we couldn't make a resource organized like a print lectionary or otherwise, but it would be a different animal.
This is what I feared - ordo and lectionary are still viewed as a single entity. It concerns me in that most likely it duplicates information (increasing opportunities for error) and increases maintenance over time. I do understand the advantages of the combined form.And if my concerns are accurate, the problems will likely be invisible to the user, so kudos for the vast improvement on functionality. [C] (hey, after a new release I'm sure you need a cup from ______)
I would like to see the RCL with DAILY support including all 3 readings and psalms
It should also incude alternate celebrations that can occur at times of feast days
I would hope that the conditional logic available in the programs could handle this and a lection ary based on the "rules" be developed.
As it is now .. I don't use it (no daily readings .. no psalms on Sunday) and just go to the USCCB site. http://www.usccb.org/nab/today.shtml But would love to have the resource correctly done in Logos 4.0
Do you mean the Revised Common Lectionary (RCL) or the Roman Catholic Lectionary (of the USCCB site)? There is a provisional RCL lectionary published by Augsburg that would likely have copyright issues. Most of the data for the Roman Catholic daily lectionary can be retrieved from files previously sent to Logos (by Damian if my memory serves). There are a few issues - votive Mass readings, for example that need to be addressed. I'll start pushing Logos on them after the Christmas season.
FYI - I would also like to see the readings from the Liturgy of the Hours or at least the Office of Readings to also be available via the lectionary function.
This XML to .logos4 transition is an issue for other datasets as well. I'm thinking of Parallel Passages where I have some custom databases I'm no longer able to use.
Most of the data for the Roman Catholic daily lectionary can be retrieved from files previously sent to Logos (by Damian if my memory serves)
Most of the data is in a lectionary file on the old newsgroups. I actually deleted all these old files to create room on my old laptop - my bad....
I'd love to see Logos negotiate the availability of the Jerusalem Bible for the readings and the Grail for the Psalms (and the Contemporary English Version for the Children's Lectionary). Other computer programs have been able to do it.
MJ, yes the readings from the USCCB site.
The Litergy of the Hours woud ROCK and be a great boon to devotional reading. Great Idea ... I would think it would be harder to do ...
I have "saved" quite a few XML lectionries that Don Awalt created and they go back to 2006 (although there may be some gaps) . I'd be happy to send them to whoever if it would help in the creation of a usable Lectionary.
The Litergy of the Hours woud ROCK and be a great boon to devotional reading. Great Idea ... I would think it would be harder to do ... I have "saved" quite a few XML lectionries that Don Awalt created and they go back to 2006 (although there may be some gaps) . I'd be happy to send them to whoever if it would help in the creation of a usable Lectionary.
Send me a personal message and I'll send you my email address. There is a long story behind it but I have a friend who is helping with input if I do the editing. I can at least figure out how much work it would take to make them complete. Actually because the Liturgy of the Hours has short sections that repeat frequently the hardest part is the two reading readings for the office of readings.
MJ .... have no Idea how to send a personal message ... clicked on everything including your personal page ... no dice ... it doesn't come up as an option on this system as far as I can tell.
So I'll throw my email out there... steveegge at comcast dot net
Stephen,
It would be a good idea to click the green MORE button next to your post, and select EDIT. At least take the @ out of your email so that spammers can't scrape the site and get it.
name at email dot com is a pretty common way to do this.
Thanks Thomas.
Most of the data is in a lectionary file on the old newsgroups.
I can recover and reformat - I saved off nearly all the newsgroup files ... some other commitments to do first that I think are better tests of the new Logos format - specifically the Jewish Torah cycle and some historic ("dead" lectionaries) for which I'm using Lutheran daily data. But I've gathered BCP, Byzantine, Syriac, Mozarabic (or was it Ambrosian?) ... I'll be busy for a while.
some other commitments to do first that I think are better tests of the new Logos format
Martha,
Do you know what the new Logos format actually is?
only that a spreadsheet can be "easily" converted into the XML format and that a specific link format is what includes the text of the lection.
