[This is a cross-post from the LIXI Mortgage Insurance Working Group. The MI Group has been inactive for so long that I expect there are people who aren't signed up to it who nevertheless would be interested in this topic.]
Some of you will be aware that we've been developing a business process model of online mortgage insurance as a prelude to developing some LIXI standards in this area to replace and improve upon the current ad-hoc usage of LIXI CAL derivatives. The model is available for review and we'd welcome feedback on it.
The model is very simple as it focuses on normal, high-volume transactions and does not try to capture less common transactions. Interestingly the model suggests, to me at least, that defining some LIXI standards in this area should be a very quick and simple project. If you consider the transactions required (dashed lines in the diagram) they appear to boil down to:
1. A MIRequest - this would need a Type attribute to distinguish between requests that are for simulations vs. actual commitment requests and to distinguish initial requests from additional-data and modified requests. It should also be "batch-able" to support scenarios where the MIRequest is really a notification of deals insured over a given period under DUA. But in any case the total number of new fields we need to define in the standard is minimal because the vast majority of data can be handled by allowing LIXI/CAL (and LIXI/Valuation?) instances as included or attached payloads.
2. A MIResponse - which is very close to being just another backchannel message, so we could create it by copying and only slightly changing the existing CAL 1.3 Response schema.
I'd be very interested to hear from anyone who thinks it's really more complicated than this. The only major wrinkle I can see at the moment is the question of how physical documents (by which I mean images of physical documents) can be exchanged - but that's a bigger question of relevance across many LIXI standards.
Recent Comments