Copy of email summary and a link to go with.
At JHU we (the JH central IT department and the Library) are currently in the midst of providing a reference implementation of a portal, with the goal of demonstrating its features and getting buy-in from other departments and divisions to develop loosely coupled services using well-defined API's.
We chose uPortal for our reference implementation poortal platform due to its features, wide adoption, commitment to standards (supporting JSR168 portlets and WSRP for example), and existing community of implementors and developers.
One of the Very Important take-home points from the aforementioned demonstration will be to show interoperabilty between different portal implementations. The RI portal will be uPortal, but we hope to demonstrate that a single portlet can be implemented in a portal-platform-agnostic way, facilitating reusablity and reducing the vendor-lockin associated with proprietary commerial softare.