JVP,
The distinction is one that your customers should not be aware of. i.e., it is not a matter of forcing a cognizable thing down your customers's throat. Rather, it is an issue of application design - the details of which - your customers should be buffered from... Sounds really compelling... but how would you advise somebody to implement an Oracle-dependent system at a customer that does not use Oracle? I know my customers would prove resistant to "buffering" about that sort of stuff and would notice quite quickly.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
