Re: [wsrp] comments draft 18

[Michael Freedman <michael.freedman@oracle.com>]

Additional items:
Section 5.1.13: Says: "The ModelTypes structure contains the payload mechanism for declaring the types referenced by a description types." 

singular/plural mismatch -- either "the desctripton types" or "a description type".


Section 6.1.19: Says:
"Note that for this version of the specification, these URLs are required to be absolute URLs, however, they are allowed to include values for parameters which utilize the URL rewriting defined in [Section 10.2.1] and Consumers MUST rewrite these URLs in the same manner as those contained within markup the Portlet might return. An example of when this might be useful is passing a parameter containing a url for returning to the current page when redirecting the End-User to a general page which handles a user sign-in process."

Better (changes in parens):
"Note that for this version of the specification, these URLs are required to be absolute URLs, however, they are allowed to include values for parameters which utilize the URL rewriting (mechanism) defined in [Section 10.2.1](.)  Consumers MUST rewrite these URLs in the same manner as those contained within markup the Portlet might return. An example of when this might be useful is passing a parameter containing a url for returning to the current page when redirecting the End-User to a general page which handles a user sign-in process."

Like Stefan, I would be conservative and remove the "wsrp:modifiedCoordinationContext" because though useful/needed, as I am not sure we have completely thought it through and hence are clearly defining it.


    -Mike-

Stefan Hepper wrote:

Hi Rich,
here my comments on the updated draft:

3.10:
- "This specification defines a state distribution mechanism for navigational state. This mechanism exposes a portion of the Portlet's navigational state to the Consumer such that coordinated updates across multiple Portlets can be effected"
I think this should be more specific, like this:
"This specification defines a state distribution mechanism for navigational state. This mechanism exposes a portion of the Portlet's navigational state to the Consumer such that coordinated updates of the shared navigational state across multiple Portlets can be effected"

- why do we still have the wsrp:modifiedCoordinationContext event?

6.1.2:
- now that we removed the properties from session params, shouldn't the session id be required?

6.1.13:
- "The public portion of navigational state could be set by the Consumer even if not supplied by the Portlet."
seems like I missed that discussion, why would I get nav state that I don't set? What is the contract here? That I can get always any nav state that I've declared as public? Is the consumer required to always send me all nav state that I've declared?

6.11.2:
- if we leave this event in the spec we should further explain it. What is a coordination context? I couldn't find a definition for this in the spec.

Appendix D:
- why are the session properties removed completely? Isn't that also a coordination mechanism between consumer and producer to coordinate on a user session concept?


Stefan


---------------------------------------------------------------------
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