During our call this morning to talk about fleshing out the Embedded Use Case requirements, Rich Thompson and I thought it would be a useful exercise to build a comprehensive list of typical look and feel abstractions that a portlet could or should expose, in addition to the common properties we're considering (e.g., locale, supported content types, etc.) Plenty of people in both tc's have direct experience creating portal/portlet-related technology, so we figure that perhaps just passing along a list of the abstractions (CSS classes, etc.) that you're working with in your own products or environments would be a good start, and we can then work on normalizing it for inclusion in the requirements. Alan