[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp-wsia] [change request #206] Values for extensible items suchas modes
The interaction that I understand the spec to lay out for areas such as modes is: 1. Portlets can specify what modes are supported prior to registration, though I suspect many implementations will restrict access to such information until after registration. 2. Consumer tells Producer what modes it uses for its aggregated pages. 3. After registration, PortletDescription specifies what std + Consumer + custom modes the portlet understands. 4. There is a conformance statement in 6.1.9 that requires Consumers to use one of the modes from #3 for perform*Interaction & getMarkup. What is missing from this set that this change request is trying to add? Rich Thompson Rich Thompson/Watson/IBM@IBMUS 03/04/2003 10:50 AM To: wsrp-wsia@lists.oasis-open.org cc: Subject: [wsrp-wsia] [change request #206] Values for extensible items such as modes Document: Spec Section: 6.1.9 and 7.1.1 Page/Line: 31/13 Requested by: Andre Kramer Old text: mode: New text: mode: Values for mode may be taken from the RegistrationData.consumerModes list provided by the consumer on registration but not all values sent need have been declared on registration. Reason: Should we remove consumerModes in registration data or make a conformance statement? Similar change request for windowStates and RegistrationData.consumerWindowStates. ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- 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] | [List Home]