[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [wsrp][interfaces] separate administration interface, requirements
Alejandro - I do not agree with the requirement that we MUST have a separate administration interface. Everything could be done reusing the current concepts: - if the consumer is able to do so it can just display the portlet in config mode to let the portlet configure itself. This way the portlet can present its configuration data in a convenient form and especially make sure that the modifications the user makes to the data are consistent - the consumer can also enumerate the properties AT RUNTIME and display them in a property editor to the user (or use a console application for this purpose). This is not very user friendly but possible. One problem is that the consumer could not check for data consistency (e.g. verify the data), but we can live with that. So why do we need a separate administration interface. This only complicates the standard. Why would the consumer need to publish all its parameter (names) as metadata if they can also be queried at runtime? This introduces redundancy, Best regards Carsten Leue ------- Dr. Carsten Leue Dept.8288, IBM Laboratory Böblingen , Germany Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401 |---------+----------------------------> | | Alejandro | | | Abdelnur | | | <alejandro.abdeln| | | ur@sun.com> | | | | | | 06/12/2002 05:37 | | | AM | | | Please respond to| | | Alejandro | | | Abdelnur | | | | |---------+----------------------------> >---------------------------------------------------------------------------------------------------------------------------------------------| | | | To: Carsten Leue/Germany/IBM@IBMDE | | cc: wsrp@lists.oasis-open.org, Thomas Klein6/Germany/IBM@IBMDE | | Subject: Re: [wsrp][interfaces] separate administration interface, requirements | | | | | >---------------------------------------------------------------------------------------------------------------------------------------------| Carsten, Thanks for you answer. I think we are not agreeing with the requirements, let me rephrase things: WSRP must have an administration interface for administering portlet configuration and settings attributes. A producer must provide metadata about the portlet configuration and settings attributes. Forcing the consumer to display the portlet to administer/configure is too restrictive. Not requiring an administration interface and the corresponding metadata will force the consumer to display the portlet for its administration. Do we want a consumer to be able to have tools (other than a markup based ones) administer/configure portlets in a producer? For example, command line tools or fat client tools. Regards. Alejandro. Carsten Leue wrote: >Alejandro - in principle I agree with the requirements. Here are my >comments (I modified your wording): > >[R-##1] WSRP SHOULD allow portlets to administer portlet >configuration and settings. > >Your original wording sounds to me as if the WSRP interface needs to supply >some additional mechanism for this administration. I believe that it could >also be achieved by letting the portlet display >administration/configuration screens and/or use the get/setProperties >mechanism. > >[R-##2] >I don't see the point behind this requirement. Can you detail? > >[R-##3] WSRP MAY provide a mean to describe the configuration and >setting attributes of a portlet as metadata. > >These attributes can also be discovered at runtime and change dynamically. >Why would they need to be exposed as metadata. > >[R-##4] > >Agreed. > >[R-##5] WSRP SHOULD NOT require a portlet to be displayed by a consumer >in order to be administered. > >The current concept uses the template for this purpose. So maybe this >fulfills the requirement. However the template would have to be >instantiated and displayed. But that's not the portlet itself. > >[R-##6] > >Agreed. > > > >Best regards >Carsten Leue > >------- >Dr. Carsten Leue >Dept.8288, IBM Laboratory Böblingen , Germany >Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401 > > > >|---------+----------------------------> >| | Alejandro | >| | Abdelnur | >| | <alejandro.abdeln| >| | ur@sun.com> | >| | | >| | 06/11/2002 01:38 | >| | AM | >| | Please respond to| >| | Alejandro | >| | Abdelnur | >| | | >|---------+----------------------------> > > ---------------------------------------------------------------------------------------------------------------------------------------------| > | | > | To: wsrp@lists.oasis-open.org | > | cc: | > | Subject: [wsrp][interfaces] separate administration interface, requirements | > | | > | | > > ---------------------------------------------------------------------------------------------------------------------------------------------| > > > > >As promised, I've compiled a list of requirements on this matter. Please >let me know of any corrections/additions. > >Regards. > >Alejandro > > >* Definitions for the purposes of the requirements that follow: > >'Configuration and settings' of a portlet are attributes that act as >parameters for the behavior or functionality of a portlet. For example, >a NewsPortlet could be configured to display sport news from Europe. > >'Personalization' of a portlet is when users customize the configuration >and settings of a portlet for themselves. > >'Administration' of a portlet is when users customize the configuration >and settings of a portlet for users other than themselves. > >* Requirements: > >[R-##1] WSRP SHOULD provide a mechanism for administering portlet >configuration and settings. > >[R-##2] WSRP SHOULD NOT assume that administration of portlet >configuration an settings is dependent on any particular UI framework. > >[R-##3] WSRP SHOULD provide a mean to describe the configuration and >setting attributes of a portlet as metadata. > >[R-##4] WSRP SHOULD NOT impose a specific configuration and settings >attributes data model on the producer. > >[R-##5] WSRP SHOULD NOT require a portlet to be displayed by a consumer >in order to be administered. > >[R-##6] WSRP SHOULD allow different security requirements for >administration and personalization functions. > > > > > >---------------------------------------------------------------- >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