ATTN: Sean and Kyle - pericope data set
The Pericope data set is very useful but incomplete. First, it does not display the pericopes defined by the lectionaries despite these being for centuries the primary definition of pericopes. Second, it does not display the pericopes used by the major commentaries - despite these being the pericopes that are best documented on the "why" of the divisions. If users were to provide the basic data for these additional pericopes, would Faithlife be willing to add them -- either in separate tools or merged into the current tool? If so, what format would be most useful to FL?
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
Comments
-
I’m definitely interested in mining lectionary data, mostly for passage ranking data. I don't know enough about the data, but it might be possible for us to come up with one or more sets of "lectionary pericopes" that we could ship. I don't know when we might get around to this, though.
I'm less optimistic about commentary units: there's so much diversity, and different perspectives on "major".
The internal format we use is quite simple: an ordered list that pairs references (in our internal format, like `bible.1.1.1-1.1.25`) with a title. That could be CSV, JSON, or any number of other formats. We have to cover the complete corpus.
0 -
The internal format we use is quite simple: an ordered list that pairs references (in our internal format, like `bible.1.1.1-1.1.25`) with a title. That could be CSV, JSON, or any number of other formats.
I imagine that there's something to indicate which versification scheme one is using?
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
The internal format we use is quite simple: an ordered list that pairs references (in our internal format, like `bible.1.1.1-1.1.25`) with a title. That could be CSV, JSON, or any number of other formats.
I imagine that there's something to indicate which versification scheme one is using?
Well, there are already details. Specific bible data types (like `bible.`) encode a versification scheme: we have several of them.
Here's an alternate suggestion (hat tip to Rick Brannan): use NRSV and specify a readable reference, like "Gen 1:1-25". We have code that can parse that into an internal data type as long as we can assume NRSV.
0
