> For example, lets say you need to store a bunch of contracts (as in your industry) in PDF/TIFF or whatever. Contracts are not as unstructured as you would th

> For example, lets say you need to store a bunch of contracts (as in your industry) in PDF/TIFF or whatever. Contracts are not as unstructured as you would think. At least in my part of the insurance world, most of them are produced by a contract writing system of some kind. Think of it as assembling as a series of contract provisions, each having a valid set of choices to select. Use your auto policy as an example - Liability - $100k Comprehensive - $10k / $1000 Deductible Collision - $50k / $1000 Deductible Yes there are other attributes captured, but you see the pattern. It's provisions and boilerplate. The use cases needing the imaged executed contract where the attribute/provision soup is not sufficient is uncommon. The operational terms of the contract exist in some other system (and database) where it's consumable in some structured way.