I've got the whole tree we worked out on the whiteboard converted to an ODD file, with some changes to keep element names unique and rationalize some things; I have new data types of various kinds, and I have a test file which is working well. The process of looking at the real data has raised a number of very complicated issues -- it turns out that partial lots can be included in titles, and titles can combine lots and partial lots from disparate blocks; e.g. title id 203 from the existing database contains 8 lots and one partial lot, from four distinct blocks. Combine this with a variety of semi-documented ownership splits and you have such a potential source of inaccuracy and confusion that a very clear policy on handling this sort of thing must be established in advance.

One outstanding issue for my ODD: should I combine all my customizations into their own distinct module? I think probably yes, but our documentation says nothing about this. When I've done with this ODD file, I'll use it as an example for the "Getting started with P5 ODDs" document I'm supposed to be working on, and I think it should also be built into TEIP5-Test as a validation test (today it uncovered a problem with handling of multiple constraints in a constraintSpec which took some sorting out across the two Jinks boxes).