OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


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.






[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC