OASIS Web Services for Remote Portals (WSRP) TC

WSRP Minutes February 13, 2003

Voting Members Attending:

Total voting members: 31
Voting members in attendance: 20 (65%)
A quorum was present.

Call began at 9:27 after some technical difficulties with the conferencing system.

Minutes were accepted from the F2F meeting without comment
(There was no meeting last week.)

Times were set up for some of the sub-committees. Details will be forthcoming in the emailed invitations.

conformance: Thursdays 8:00-8:30 PST
interoperability: Thursdays 8:30-9:00 PST
Markup: Wednesdays 8:00 PST

Eventing sub-committee will be the portlet coordination sub-committee. Currently planning on having a monthly call.

Jacob taking over web-site webmaster duties for WSRP at the OASIS site. Minutes and specs should be sent to him.

CHANGE REQUESTS

Change Request 128: Cache invalidation due to perform*Interaction()

The proposal was to state that the Consumer-side cache for a portlet should/must be flushed as a result of an action targeting that portlet. The concern here is that the portlet currently has no control over the invalidation of the Consumer-side cache, and you could end up with inconsisten behavior for some portlets.

Michael and others pointed out that there was agreement at the November F2F was that version 1 would not deal with an invalidation caching mechanism. The concern was that this was a complex subject and more time was required in order to do it right. Part of this concern was that by specifying any type of behavior related to invalidation you could hamper the implementation of more sophisticated extensions or hamper the ability to specify a mechanism in a future specification version.

Resolved:
Will provide guidance (not at a conformance level), that the COnsumer may want to consider the cache invalid after and action. Will also add a comment that future versions of the specification would address invalidation caching explicitly.

Change Request 129: wsrp-url portlet URL parameter

Would require the Consumer to propagate the same type of request (e.g. GET, POST) for a resource.

Michael: prefer to leave the flexibility, for Consumers that want to only do POST. See no value in going this tight.

Resolved:
Will provide guidance (not at a conformance level) that the Consumer should use the same method it received.

Change Requests 130.131.132 WSDL updates

Resolved: Changes accepted without objection

Change Request 133: Wild card mime types for MarkupType structure

Not every portal is aggregating portlets. Portlets are accessed by individual requests. Some portlets may generated varying types of markup.

Resolved: Accepted without objection

Change Request 134: Make MarkupType.locales optional

Portlets may not know all the locales it supports since content may be pulled from another source.

Resolved:
Make it optional: semantic is that if absent, any locale will be accepted.

Add in wildcard support as described in Change Request

Change Request 135: Add Display Name

Display Name: name designed to be used in Portlet repository toolbox displayed to page designer

Title: Meant to be displayed in portlet banner shown to end-user.

Resolved: accepted without objection

Will resume with Change Request 136 at the next meeting.

Meeting adjourned at 10:05 PST