OASIS Web Services for Remote Portals (WSRP) TC
WSRP/WSIA Telecon 02/20/2003
Meeting began at 9:09 PST
Roll Call
|
Voting Members In Attendance: |
Company |
|
|
Abdelnur, Alejandro |
Sun |
Yes |
|
Aickin, Sasha |
Plumtree |
Yes |
|
Allamaruaju, Subbu |
BEA |
Yes |
|
Atkinson, Olin |
Novell |
Yes |
|
Blich, Amir |
SAP |
Yes |
|
Braun, Chris |
Novell |
No |
|
Brooks, Rex |
Starbourne |
Yes |
|
Cox, T.J. |
Novell |
No |
|
Cox, William |
BEA |
No |
|
Dirking, Brian |
Stellent |
No |
|
Freedman, Michael |
Oracle |
Yes |
|
Fubini, Ross |
Plumtree |
Yes |
|
Jacob, Richard |
IBM |
Yes |
|
Klien, Jon |
Reed-Elsivier |
Yes |
|
Kramer, Andre |
Citrix |
Yes |
|
Kropp, Alan |
Vignette Corporation |
Yes |
|
Leue, Carsten |
IBM |
Yes |
|
Machak, Dan |
Tibco |
Yes |
|
Mitsuoka, Madoka |
Fujitsu |
No |
|
Nolen, Adam |
Reed-Elsivier |
Yes |
|
Ramesh, Raj |
CommerceOne |
Yes |
|
Randhawa, Sunit |
Fujitsu |
No |
|
Ratcliffe, Nigel |
Factiva |
No |
|
Schaeck, Thomas |
IBM |
Yes |
|
Shumaker, Gennady |
SAP |
No |
|
Smith, Steven |
Capitol College |
No |
|
Tamari, Yossi |
SAP |
Yes |
|
Tayar, Gil |
WebCollage |
Yes |
|
Thompson, Rich |
IBM |
Yes |
|
van Lydegraf, Eric |
Kinzan |
No |
|
Wiecha, Charles |
IBM |
No |
|
Young, Michael |
Plumtree |
No |
Total voting members: 32
Voting members in attendance: 20 (62%)
A quorum was present.
|
Prospective Members in Attendance: |
Company |
|
|
Batra, Atul |
Sun |
Yes |
|
Observers in Attendance: |
|
|
|
Martin, Monica |
Drake Certivo |
No |
|
Members on Leave of Absence: |
|
|
|
Filicetti, Gino |
Bowstreet |
No |
|
Palas, Petr |
Moravia IT |
No |
|
Reshef, Eilon |
WebCollage |
No |
|
Rudnicki, Joe |
U.S. Navy |
No |
The minutes were accepted from the teleconferance on 2/13/02
Rich started addressing the outstanding change requests.
All of the following changes were accepted without objection:
Small editorial/grammar changes :
145 - Missing 'the' in 6.1.10
146 - Rearrange phrases in 6.2.1.1
148 - Explicitly "session" scope
149 - Respecting grouping
150 - Typing of extensions
152 - Drop "is"
154 - false -> "false"
159 - Delete reference to included field
160 - Update useCachedMarkup description
161 - Ports, not bindings
163 - Plural field names for arrays
Summary of the substantive changes:
|
139 - Add UpdateResponse.isSecure? |
TABLED |
|
140 - Add PortletDescription.onlySecure? |
ACCEPTED |
|
141 - Add previous windowState and mode? |
TABLED |
|
157 - Add pushesPersistentState? |
NOT ACCEPTED |
|
136 - Producer supported user profile types |
ACCEPTED |
|
137 - Producer supported window states and modes |
ACCEPTED |
|
138 - How does info get to proxied resources |
TABLED |
139 - Add UpdateResponse.isSecure?
Reasoning: This is the only case where the Producer cannot control security of the transport.
Tabled for this week. Discussion was taking too long.
140 - Add PortletDescription.onlySecure?
Reasoning: JSR-168 Alignment. A JSR-168 portlet can describe itself as always being secure. The technical reason is that this allows the Consumer to optimize the user experience.
Resolved: the flag will be added to PortletDescription
141 - Add previous windowState and mode?
Reasoning: JSR-168 Alignment. This will allow the Producer to get back to the mode or window state it was in prior to being changed by the Consumer.
Tabled for this week. Allow people to think about it
157 - Add pushesPersistentState?
Reasoning: Allow Producers to specify that it will require Consumers to store persisted state.
Mike raised the point that it is not optional for Consumers to support persistence.
Resolved: Don't do this in version 1. Perhaps in a future version, we may relax the constraint on Consumers having to support persistence.
136 - Producer supported user profile types
Reasoning: JSR-168 Alignment. Allows having localized descriptions of the profiles. This will be similar to userCategoryDesciptions
Resolved: Will define userProfileDescription similar to userCategoryDescription. Provided in Producer description.
137 - Producer supported window states and modes Reasoning: JSR-168 Alignment. Same behavior as for userProfileDescriptions in CR 136.
Resolved: accepted
138 - How does info get to proxied resources (Insert a new section 10.4?)
Reasoning: Some proxied resources need to have access to additional state in order to execute properly.
Question on whether Consumers need to handle cookies in accordance with the cookie spec.
Resolved: The section will probably be useful, but there are still some open questions. Continue with email discussion
Next week will do a 1-hour call on Tuesday and a 2-hour call on Thursday.
Meeting adjourned at 10:10 PST