TextCritical.net

Note that the reference in the URL works. The reference jump fails and selecting the verse causes a new request to be made to the server.

Providing all of the verse IDs to a list allows the verse jumps to works provided you don't leave the chapter. The only way to get this to work is to provide all odd verse IDs to the front-end code. This would need to need to mapped to chapters too. Ugh.

Here are some options to address this:

1. Change URL design to take entire reference as a string
2. Add REST endpoint which takes a reference string and returns a path
3. Add Javascript that splits up the reference and performs a REST call to get the list of verse IDs with spaces or dots in them within the given chapter
4. Add Javascript that performs a REST call to get the list of division and verse IDs with spaces or dots in them

Option 4 will not be able to distinguish between verse IDs with dots in them and separate verses. That is, it couldn't tell you if "Ecclesiasticus 1:1.2" should be Ecclesiasticus/1/1/2 or Ecclesiasticus/1/1.2.

Solution two (REST API that provides a reference) is likely the best approach. I just need to define the algorithm though.

This is working now. I just need to:

• Generalize the code for attempting a parse of a reference in order to break out the functions and clean up the code
• Update the JS to use the online version of the reference check and remove the local version

Might want to have the AJAX update done locally with no re-post of the main page; this would avoid one HTTP request.