<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<a class="moz-txt-link-freetext" href="http://www.lcms.org/resources/worship/churchyear">http://www.lcms.org/resources/worship/churchyear</a> is the given
lectionary for the Lutheran Church - Missouri Synod. Note the 3
year lectionary adopted a few years ago. Many of us still use the
traditional 1 year lectionary. For practical matters, that listed
in the hymnal is the most likely to be used. There are still many
of our churches using the older hymnal and so both lectionaries are
in use.<br>
<br>
The catch for most people is that there are more than 52 Sundays in
the church year in order to account for Easter, primarily. Easter
is a lunar calendar time rather than our normally used solar year.
<br>
<br>
Speaking personally, I find that as you noted, the lectionary forces
you to speak about more than your favorite topics. The exciting
part is that as I do so, I find there is far more in each pericope
than I realized before having to preach on them.<br>
<br>
art<br>
<br>
<div class="moz-cite-prefix">On 1/22/2014 7:40 PM, DM Smith wrote:<br>
</div>
<blockquote
cite="mid:D1139F1C-FC86-4049-ADC6-5D7EB673D59E@crosswire.org"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
Art,
<div>Is the lectionary online? Can you give us a link?</div>
<div><br>
</div>
<div>There was a study done a long time ago that found that
pastors that preached from the lectionary covered more biblical
content and those that didn't covered the same few themes/topics
over and over.</div>
<div><br>
</div>
<div>The United Methodists also have a lectionary.</div>
<div><br>
</div>
<div>In Him,</div>
<div><span class="Apple-tab-span" style="white-space:pre"> </span>DM</div>
<div><br>
</div>
<div><br>
<div>
<div>On Jan 22, 2014, at 8:35 PM, Arthur Bolstad <<a
moz-do-not-send="true" href="mailto:tolonaro@gmail.com">tolonaro@gmail.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000"> Lutherans often
organize devotions and sermon thoughts by the lectionary
location or the church year. This would be different
organization for the material but on the same idea of a
yearly bible reading. More thinking out loud.<br>
<br>
art bolstad<br>
<br>
<div class="moz-cite-prefix">On 1/22/2014 10:17 AM, DM
Smith wrote:<br>
</div>
<blockquote
cite="mid:D75BC23A-67B6-47B9-9528-A2BC56E0E65D@crosswire.org"
type="cite">
<pre wrap="">On Jan 21, 2014, at 8:42 PM, Peter von Kaehne <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:refdoc@gmx.net"><refdoc@gmx.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Tue, 2014-01-21 at 15:05 -0500, DM Smith wrote:
</pre>
<blockquote type="cite">
<pre wrap="">JSword does support these. A SWORD Daily Devotion is far more than just a list of verses per day, though it can be that.
</pre>
</blockquote>
<pre wrap="">Yes, I thought that (both statements above). Which makes me think what
is the benefit of encouraging people to create Bible reading plans which
would not be usable by libsword users? Conceptually Bible reading plans
are nothing but very simple daily devotionals, but they have a huge
value for users.
</pre>
</blockquote>
<pre wrap="">We've talked about user sharing content before and it never really went anywhere. Typically it is concerning personal commentaries. Or with personal modules.
Agreed that they are very simple daily devotionals.
We also need a simple way to create them. Some have suggested a rule engine that would construct a listing of passages.
</pre>
<blockquote type="cite">
<pre wrap="">I agree that the localisation you mention of references is a useful
feature of JSword reading plans over daily devotional modules, but am
wondering if this could be implemented within the engines in other way?
</pre>
</blockquote>
<pre wrap="">I didn't mean the references. JSword already does that when it can. Especially, converting the numbers into Arabic.
I meant the title of the reading plan, which is something like "NT 2x and OT 1x per year".
</pre>
<blockquote type="cite">
<pre wrap="">If we had the ability to tag and interpret appropriately:
<reference osisRef="Luke.1.1"><div
x-translatable="true">Luke.1.1</div></reference> or some such
we could then create a filter item for parsing and converting acc user
desired locale the <div x-translatable="true">Luke.1.1</div> bit (or
however we want to tag that central bit.
</pre>
</blockquote>
<pre wrap="">Yes today's representation is not appropriate for full internationalization.
As long as OSIS references do not contain extraneous content (such as commas, words like "and"), this can already be done by the engine.
Having it be more than a file w/ one line (or two) per day is overkill. The module format is overkill and hard for sharing as it is many files. But it is easy.
$$$01.01
Gen.1 Mat.1 Ezr.1 Act.1
$$$01.02
Gen.2 Mat.2 Ezr.2 Act.2
$$$01.03
Gen.3 Mat.3 Ezr.3 Act.3
$$$01.04
Gen.4 Mat.4 Ezr.4 Act.4
One problem with such a devotional is that it is presented by days of the year. (Bible Desktop does it this way)
It might be nicer to have it be a check list. One can start at any time during the year. When the reading is done, it is checked off. The next request, which may not be the next day, gets the next unchecked entry.
Another problem with using OSIS, ThML, ... for such a module is that it presumes a particular way of rendering the content. It uses a general purpose filter for rendering.
The above is in text form of osisRefs. but is not marked up as OSIS. It would be up to the front-end to format this in a meaningful way. E.g. a bullet list, all on the same line, reference followed by the first 10 words of content from a default module (perhaps a commentary), ...
</pre>
<blockquote type="cite">
<pre wrap="">All required infrastructure is available in both engines, adding it
would be useful in way more places than just daily devotionals.
</pre>
</blockquote>
<pre wrap="">JSword lacks the ability to create such a module. It would be fairly straight forward to add it.
</pre>
<blockquote type="cite">
<pre wrap="">Just thinking loud....
</pre>
</blockquote>
<blockquote type="cite">
<pre wrap="">Peter
</pre>
</blockquote>
<pre wrap="">Me too...
DM
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jsword-devel mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
</pre>
</blockquote>
<br>
</div>
_______________________________________________<br>
jsword-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
jsword-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>
<a class="moz-txt-link-freetext" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>