cardinality doesn't evoke the idea of bringing a set of things together (sometimes quite unrelated) to achieve a user view from many parts in my mind. I don't dispute that "mashup" has a bit of a hack idea to it (the quick, yet elegant hack, but not really designed as a lasting solution).

They are supposed to be rather quick and dynamic. Enterprise shouldn't always result in a long drawn-out optimization of planning process. That's one of the key reasons users get fed up waiting for IT to get anything done and hack a view together in excel drawing on 5 database sources themselves. And then pulling it into access (or even just continuing in excel), adding their own data to it, and creating yet another island of unknown critical data in the organization.

Mashup should be a proving ground. If a mashup gets hacked together and draw a lot of use and desire from the people in the organization, refactor it and polish it up into the internal portal as a supported view. The enterprise word for mashup is "no longer relevant" by the time it's deployed. ;-) Let them innovate, then adopt and support the best of the crop.

Not we cannot use "cardinality". Perhaps "composite applications" can be the posh term for mashups though.