Re: [wsrp] Navigational parameter restrictions

[Stefan Hepper <sthepper@hursley.ibm.com>]

I would be also in favor of this approach. It would make the alignment 
with JSR 286 simpler as in the JSR 286 we only support Strings as 
navigational parameters.

Stefan

Michael Freedman wrote:
> Should we restrict the returned navgiationalParameters in UpdateResponse 
> to only be values representing xml scalar types [int, string, etc.]?  
> The issue here is similar to the one that caused us to restrict what the 
> producer can encode in the URLs it writes into markup, namely many 
> consumers will prefer to manage these values in the same way they manage 
> navigational state.  As this is commonly handled by writing the state 
> into every URL in the page, shouldn't we make it easy for a consumer to 
> do so?  If so, should we back track all together and only support scalar 
> types?  Or do we preserve the full open model for those properties that 
> aren't set by producers and might presumably either be computed by the 
> consumer vs. being encoded?
>    -Mike-
> 
> ---------------------------------------------------------------------
> 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
> 
>