I am sure that this is a most useful exercise and the sort of information collated so far shows just how useful it will be. I do have a reservation about organising the information and making it available electronically. Ideally the data should be organised into records such that the user can extract the information to suit them - this probably means that the number of records required would be well in excess of the number of knots in Ashley but it can be started and tested with one knot (eg the bowline) and built from there over time - it’s also easier to correct and update in this form. I haven’t as yet looked at a practical way of organising the info - a spreadsheet is probably as good a tool as any for prototyping but I do think it would be useful spending time looking at data management as well as the actual data itself.
Happy to help in any way I can (I do know more about data management than I do knot tying but unfortunately that’s not saying much!)
Since posting this I’ve thought some more about the issue and therefore added this bit (the above is a bit cryptic perhaps). Although presentation is important this comes at the end rather than the beginning - although it’s vital to know what you’re aiming to provide. The cross references etc will fall out of an analysis of Ashley automatically if you record the basic knot data in a simple form - clearly there has been a lot of effort expended so far but as progess is made it may become very difficult to sustain ie you can read forward to where a clove hitch is repeated or used as the basis or start of another knot but when you index the later knot how do you refer back to the origin without a lot of effort again? I appreciate that this may still be as clear as mud but rather than confuse the issue any further I’ll await comments.