[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp][all] First version of WSRP Overview Presentation
Sasha, thanks for your comments. Good that you spotted the relict "visual" at page 5. In the example on page 7, actually the control in the document is just a client that uses the WSRP protocol and thus does not behave different from a portal. The mention of document context is indeed misleading, I removed "document". Page 8 does not show bind/unbind, just create/destroy instance and the action/markup loop in quite an apstract manner. Page 10 - people are asking all the time how Portlet API and WSRP can fit together, so it important to show how WSRP and Portlet API fit. You are right that a local Portlet API from a WSRP perspective is an implementation detail of portals, I've changed the chart to reflect that the Portlet API is an internal aspect of portals. Page 15 - typo corrected. Best regards, Thomas Sasha Aickin <AlexanderA@plumtree.com> on 04/12/2002 05:28:39 AM Please respond to Sasha Aickin <AlexanderA@plumtree.com> To: Thomas Schaeck/Germany/IBM@IBMDE, wsrp@lists.oasis-open.org cc: Subject: RE: [wsrp][all] First version of WSRP Overview Presentation Thomas, My comments: On page 5, you use the term "visual WSRP services" but provide VoiceXML, a non-visual presentation markup, as an example of a supported markup type. I think we agreed to change our references to "visual" to instead be "presentation", although I might be misremembering. On page 7, are we really committed as a group to the notion of passing document context in the plugin case? I think this is significantly off of our main mission of creating things that can be integrated into portals. On page 8, I think that a lot of the lifecycle there is still under debate. It seems a little early to me to present the action handling and bind/unbind model when we seem to disagree about a lot of it. On page 10, I don't think that it's important from a WSRP perspective to include either a Portlet API or Local Portlets in the diagram. Portlet APIs seem right now to be an internal implementation detail of particular portals, and local portlets are orthogonal to what we have been talking about. On page 15, there is typo ("requets" should be "requests"). Cheers, Sasha. -----Original Message----- From: Thomas Schaeck [mailto:SCHAECK@de.ibm.com] Sent: Monday, April 08, 2002 3:03 PM To: wsrp@lists.oasis-open.org Subject: [wsrp][all] First version of WSRP Overview Presentation Here's the first version of the WSRP Overview Presentation: (See attached file: WSRP Overview.ppt) I would like to gather feedback until next Monday; then update the presentation and put it on the web site as the first version of the canned presentation. I'll update the presentation on a regular basis, including more technical content as we make progress in our technical discussions. Best regards, Thomas ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC