A MUST of this sort would need to really describe what "personalization"
is, and I wouldn't want to go to that route! With a SHOULD, I think we can go
with a vague definition of "personalization".
-----Original Message-----
From: Rudnicki Joseph G CONT NSSC
[mailto:]
Sent: Mon, December 02, 2002
17:55
To: 'Tamari, Yossi';
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:]
Sent: Sunday, December 01, 2002 1:18
PM
To:
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:]
Sent: Sunday, December 01,
2002 1:13 PM
To:
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
