With UNO service information changed from active to passive, XML-based representation a while ago, UNO type information is the remaining topic that needs some love, clean-up, and improvement. From a curiously verbose UNOIDL syntax, to the awkward binary .rdb format, to the fact that type information is duplicated in different formats for binary UNO and Java UNO, all the way to the still unsolved great challenge of becoming incompatible compatibly, etc. etc. -- you get the idea.