[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp] navigationParameterDescriptions clarification
I agree that this needs clarification. The whole point about coordination is providing the same value of a given property/parameter to all parties intersted in it. The only means for that is the Qname. In your example if portlets don't intend to share the same value then it's not a shared nav param, but that's basically it. We don't have a means in the protocol that allows a "context sensitive" grouping. Therefor I would really make even a stronger statement. Mit freundlichen Gruessen / best regards, Richard Jacob ______________________________________________________ IBM Lab Boeblingen, Germany Dept.8288, WebSphere Portal Server Development WSRP Team Lead & Technical Lead WSRP Standardization Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888 Email: mailto:richard.jacob@de.ibm.com Subbu Allamaraju <subbu@bea.com> To 02/10/06 02:54 PM OASIS WSRP TC <wsrp@lists.oasis-open.org> cc Subject [wsrp] navigationParameterDescriptions clarification Regarding the text that describes navigationParameterDescriptions field, I have a few questions. 1. "Consumers SHOULD supply the same value to Portlets which provide a navigationParameterDescription referencing the same QName for the parameter’s name." Does this imply that if two portlets having the same QName for the name of the parameter, SHOULD receive the same value barring consumer policy decisions? Since this is a SHOULD and not a MAY, I would expect most general purpose consumers to supply the same value as long as the name matches. 2. "An example of when this might not be appropriate is when the Portlets are related to the same Producer offered portlet handle. The context in which the Consumer is using Portlets related to the same Producer offered portlet handle will determine whether or not such Portlets will share the same values for their navigation parameters." The example seems incomplete. Depending on the nature of the parameter, it might make sense to supply the same value, e.g. a user's last name. An example where it might not make sense is a stock symbol supplied to a charting portlet. Subbu --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. You may a link to this group and all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]