I've been thinking a lot about tModels lately and keep noticing peculiarities that endear the structure to me even more. So, I'll be posting some thoughts on the oddities of tModels over the next couple days.
Odd Fact #1 - They can never be deleted. Once you create a tModel, you can't get rid of it. Yes, there is a delete_tModel API message, but calling that API does not delete the tModel (as it purports to do); it "hides" it. We aren't talking about a latency behavior here; we are talking about deceptive semantics for the purpose of preserving referential integrity.
In fact, you can resurrect a deleted tModel from the dead by "re-saving" a deleted tModel. This resurrection behavior, however, is not true for any other entities in UDDI.
All in all, tModels are very persistent critters; you might think you exterminated them, but you didn't.
Stay tuned for other strange facts about tModels...