automating X

Bible Reading Planner XML File

Home Macros Scripts Weblinks Other Tools FAQ Links About			Opening the BRP XML file in notepad you will see a strange mix of tags, attributes, and values that can be a little bit daunting at first but are not that difficult to understand.
			<?xml version="1.0"?> <lbx-bible-schedule version="0.91" name="Solomon Buids Temple" category="BibleReadingPlans" hide-read="no" calendar-view="yes" resource="LLS:1.0.10"><passage>2 Chronicles 2-3 | 1 Kings 5-6</passage> <days>0123456</days><start-date>20030713</start-date><sessions>3</sessions> <days-read>0</days-read><plan-summary><s d="20030713" r="14.2.1-14.2.10;11.5.1-11.5.18"/> <s d="20030714" r="14.2.11-14.2.18;11.6.1-11.6.14"/><s d="20030715" r="14.3.1-14.3.17;11.6.15-11.6.38"/> </plan-summary></lbx-bible-schedule>
			Taking a look at a graphical view of the file makes the structure of the tags, their attributes and values easier to understand.
			The root element of the is lbx-bible schedule. This tage has associated with it the following attributes: version (internal LDLS BRP version number), name (name you give to BRP when you save it), category (internal LDLS attribute set to BibleReadingPlans), hide-read ( show/hide read passages), calander view (display in calender or list format), and resource (Book Id of bible version to be used by plan) and child elements: passage (scripture selection), days (days which readings are to take place), start date (date of first reading), sessions (number of sessions plan is to be spread over), days read (how many reading sessions completed), and plan summary. The plan summary has a number of child elements, s, that corresponds to the value of the element sessions. Hence in this example sessions is 3 so there are 3 child elements s under plan summary. Each occurence of element s inlcudes two attirubutes: d to indicate the date of the reading session and r which indicates the passage to be read. Notes: where dates are used the format is yyyymmdd for the element days the numbers 0-6 refer to Sunday to Saturday respectively ie if you include 0123456 as the value for this element this indicates you want reading sessions to occur everyday but if you only wanted monday to friday reading sessions then the value used would be 12345. the value of the attribute r , indicates what verses are to be read for that session are in the internal LDLS format: book number.chapter.verse eg. Genesis is book number 1, Exodus book number 2 etc so 14.2.11-14.2.18 is equivalent to 2 Chron 2: 11-18. If more than one passage is to be read in the same session then separte the two different pages by a semi-colon eg: 14.2.11-14.2.18;11.6.1-11.6.14
			IMPORTANT NOTE: If you manually edit the plan summary tags in a BRP XML file DO NOT use the BRP module in LDLS to open the file otherwise the module's own internal algorithms will over write the manual changes you have made. You must only display a manually edited file on a Home Page within LDLS.
			In order to complete the picture I have include an image below of what this plan would look like in the BRP module. By comparing the text file, the graphical view and this image should help you correlate the tags with the settings you choose when creating a BRP in LDLS. (Just don't forget the important note - once you have manually edited the reading sessions DO NOT open the file in BRP module otherwise you will loose those edits.

	Return
This site is maintained and updated by Andrew. Page Created:13/7/2003. Page Updated: 13/7/2003 Current Date: