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

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

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


Subject: RE: [wsrp-wsia] [I#164] An entity SHOULD support help,and CAN su pport edit


Hello,
 
Perhaps, "...MUST support edit mode if it allows personalization?"
 
Take care.
 
Joe
 
 
-----Original Message-----
From: Tamari, Yossi [mailto:yossi.tamari@sap.com]
Sent: Sunday, December 01, 2002 1:18 PM
To: wsrp-wsia@lists.oasis-open.org
Subject: RE: [wsrp-wsia] [I#164] An entity SHOULD support help, and CAN su pport edit

I second this. Many entities simply do not have (need) an edit mode. A "Top business news" portlet may not be personalizable.
Maybe the wording should be "... SHOULD support edit mode if it allows personalization".
 
    Yossi.
-----Original Message-----
From: Gil Tayar [mailto:Gil.Tayar@webcollage.com]
Sent: Sunday, December 01, 2002 1:13 PM
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [I#164] An entity SHOULD support help, and CAN support edit

Issue: 164
Status: Active
Topic: interface
Class: Minor_Technical
Raised by: Gil Tayar
Title: An entity SHOULD support help, and CAN support edit
Date Added: 1-Dec-2002
Document Section:   v0.85/5.10
Description:
In v0.85, an entity SHOULD support both edit and help. I think SHOULD for edit is too strong a recommendation, as it puts a fantastic burden on the portlets. As Help is very simple to implement, I think the wording should be changed to: "an entity SHOULD support help, and CAN support edit".
 
Gil Tayar
WebCollage
 


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


Powered by eList eXpress LLC