In programming context, we can see a framework as a standard (De jure) that newer things can EMERGE from. It is excepted that such newer things must have obeyed the set rules/standards. Then we can say framework provides us with reusable components. Another keywords that I have come across is distribution system when reading about frameworks. In programming, we have come across emormous frameworks such PEAR, DotNetNuke, PHPNuke, CAKEPHP, SMARTY and recently ZEND.
I observed that some are specifically needed to accomplish certain tasks like portal development. In this case, we can talk of DNN(DotNetNuke). But it is different in the case of PEAR. One may need PEAR to develop his custom application. This is different from out-of-box solutions like DNN. I see ZEND in the same direction with PEAR.
In conclusion, portal frameworks are out-of-box solutions for web portal development. And these include DNN, PHPNUKE, PLONE while custom-based application frameworks include PEAR, ZEND, SMARTY and CAKEPHP to mention a few.
What comes to my mind is that a custom-based application framework like ZEND, PEAR can be used to generate new portal framework or other frameworks.
If that is the case, expect emmmm…. : A framework for multichannel application using single authoring soon.
Will talk more on that in future.