OASIS Web Services for Remote Portals (WSRP) TC

WSRP/WSIA Telecon 01/07/2003

Roll

27 of 38 voting members attending

Meeting started at 12:05pm EST

Minutes from 19 December 2003 approved with 3 corrections made by Rich.

These items should read as follows:

#154 Discussion

• We are not currently synchronized with JSR168
• We have not decided to synchronize with JSR168
• Gil will produce 3 versions for the Primer (such as configuredPortlet)
  Will not change API names

#173 Summary not yet added

• Will will try the overview section in the next version

#174 Roles: Change "must" to "must not"

• no objections, but this is tentative relative to resolution of #185

Minutes from 2 January 2003 approved

Gil will post an updated issue list.

Rich will post an updated version of the spec by the end of the week (maybe called version .87 or .88).

#169 Does refresh page (F5/Ctrl+R) re-invoke performBlockingInteraction?

• Up to the Consumer implementation.
• Many will do a redirect so a refresh is just a getMarkup()
• Producer must be prepared for End User pusihg the button a second time
• Resolved to add text to spec and primer

#183 markup charset differen to the same as the XML response charset?

• resolved: set a note to the editors that they are to be kept the same (attachments are excluded)

#170 Scope of Producer-Consumer HTTP session

• resolved: maximum scope is the scope of the Consumer client's logical session (vague about what a session is)

#154 Rename "entity" to "portlet" (re-opened due to JSR168 change)

• resolved:Use "portlet" where no distinction is necessary. Use Producer configured-portlet and Consumer configured-portlet where the distinction is necessary

#185 Remove concept of Roles from the spec

• resolved: Rename "role" to "usercategory"
• resolved: Leave "usercategory" in userContext

#174 The Consumer SHOULD NOT assert a role for a role which ...

• tentative resolve: change to 'MUST NOT"
• tentative resolve: add text that all supported userCategories MUST be declared (including predefined terms)

#175 Roles should be per-Entity and not per-Producer

• resolved: leave as is

#184 Can performInteraction return new navigationalState?

• resolved: No, cannot return new navigationalState. Operation is just getMarkup() plus interactionParams

#181 Registration Changes

• resolved: leave in for version 1. May still need to work out the details
• Revisit for version 2.

#179 requestParameter semantics unclear

• resolved:
  • Remove requestParameters
  • Add interactionState to interactionParams
  • Add text about navigationalState reflects how to regenerate the page, interactionState reflects input to perform*interaction
  • Add text around what navigationalState to use when returning markup from BlockingInteraction
  • Add text about Consumer's processing URL activation

Next meeting will be Thursday, 9 January at 5pm German time/11am EST/8am Pacific

Details about the next face-to-face meeting will be posted on the website tomorrow.

meeting ended 1:39pm EST