Probably nobody cares about this topic and absolutely nobody has an opinion on it, but how should we do Biblical notation?

[[Gen 1:1]] leads to

Book of Genesis, chapter 1, verse 1

??

+[John 1–3; 3:16; 6:14, 44]+

Or we use crosses?

Do we ask for a certain translation like

+[KJV ~ Gen 1:1]+

Or something?

What sort tags does each verse need?

πŸ€”

nostr:nevent1qvzqqqqqqypzplfq3m5v3u5r0q9f255fdeyz8nyac6lagssx8zy4wugxjs8ajf7pqy2hwumn8ghj7un9d3shjtn0wfk8jtnyv4mz7qguwaehxw309a3ksunfwd68q6tvdshxummnw3erztnrdakj7qpqmpq8uwta40y4fwc97kqfdte6xkx94n7a8aqyfyq2p7wyeea5lh2sppmc2k

#christian #biblestr #bible

Reply to this note

Please Login to reply.

Discussion

Specific translations are important for sure; not sure how to implement though.

Yeah a bit tricky, but it's basically that we have to think of what we'd want to search for.

We already published the KJV and Douay-Rheims, by chapter, but it's not really useful that way. I keep wanting to embed verses in notes with a link.

[[Gen 1:1]] is the same as a wililink, so that was a dumb suggestion.

Need some other bracketing.

:[Gen 1:1]: is very clean. I low-key love the +, tho.

How does biblegatway do it? They probably have a good system. (Not sure this is relevant as I don't really know what is going on in this note lol)

Their website is blocked im Europe.

I thought you were in the US

I'm German.

I know:) but I thought you were based in the US tho

No, I just lived there, for a while.

Wikipedia does it like

{{Bibleverse|Genesis|1:1|KJV}} β†’ Genesis 1:1

I like the +[Gen 1:1]+. Traditionally, Bible verses may be cited in a different way than other works, so it seems sensible to have a unique citation style as an AsciiDoc extension.

We can also include the translation abbreviation, e.g. +[Gen 1:1 KJV]+ or [Gen 1:1 RSV]+.

We'd want to publish a table of supported abbreviations for book and translation names.

Ah, yeah, didn't realize that we could just use whitespace as a book delimiter. Cleaner.

3 votes for +[ ]+, so far.

No opinion on the notation per se, but the translation call out should be optional. Also, a good reader should provide the option to override a specified translation. For example, notation calls for KJV, but I only want to see NET.

Also, it might be helpful to look over OSIS. This is a Bible & related text encoding standard that is gaining cross-platform traction:

https://crosswire.org/osis/

They include a lot of obscure stuff, but some of it is interesting. Like "canonical".