OASIS Web Services for Remote Portals (WSRP) TC

WSRP Conference Call - May 30, 2002

Roll Call

Alan Kropp, Epicentric
Aditi Karandika, France Telecom
Rich Thompson, IBM
Thomas Schaeck, IBM
Charlie Weicha, IBM
Lothar Merk, IBM
Petr Palas, Moravia IT
Mark Cassidy, Netegrity
Mike Freedman, Oracle
Sasha Aickin, Plumtree
Jane Dynin, Plumtree
Michael Young, Plumtree
Adam Nolen, Reed-Elsivier
Chris Braun, Silverstream
Alejandro Abdelnur, Sun
Yossi Tamari, SAP
Joe Rudnicki, US Dept. of Navy
Andreas Kuehne

Agenda

Finalize specification breakup

• Markup fragments and SSO - Jeff & Alan to split
  • ChrisB - they're scheduling a meeting on Friday, probably Jeff to take markup and Alan to do SSO/Security

Next F2F Meeting

• June 24-26th
  • Two days of WSRP
  • Third day is common meeting with WSIA
  • WSIA to continue on Thursday (not Friday at this point)
• Hosted by Oracle
  • MikeF -- Oracle conference center at Oracle HQ about 10 miles south of SFO airport (in Redwood Shores, CA)
  • Please send back the short survey letting us know if you are coming to the F2F in person or on the phone
  • Agenda is 9-5
  • Sasha - will there be a dinner?
    • Mike/Thomas - we'll work on it, figure Tuesday for dinner
    • Oracle hosting lunches and snacks, dinner we're on our own

Wireless Use Case (Aditi)

• Telecom company/mobile service provider
  • Consuming things like stock portlet
  • Consumed by telecom company and offered to end user
  • Has realtime, offline, and alerts
  • Offline can be accessed when network is down
• Roles
  • Application Provider who makes the content available as a WSRP service
• Requirements
  • Multi-modality important (voice & web, e.g.)
  • Should be able to support different markup languages like VXML, WML, HTML
  • Should work offline and in sync mode
  • Should easily integrate into telecom's environment
  • End user should be able to modify easily
• Questions?
  • Thomas - this is more describing a complex system that involves offline mode without service
    • Aditi - It's important to be able to read things offline
    • Thomas - this and alerts seem to not involve the protocol we are talking about
  • Sasha - Do you see alerts as happening out of band?
    • Aditi - you should be able to specify which alerts you want, but they may not go through WSRP.
    • MikeF - Are these different from other preferences?
      • Aditi - Not really.
  • Thomas - Maybe we should factor out some of these things and specify what is WSRP specific?
  • Aditi - Is multi-modality important for WSRP?
    • Thomas - it is important for WSRP to support multiple markups, but do you mean one request containing multiple markups?
      • Aditi - the former
  • Sasha - It seems that the offline case has implications for caching
  • Thomas - what do you mean by sending information through multiple channels?
    • Aditi - republishing as a web service
• Aditi to update with info about what is important for WSRP

Multimedia Sports Portal (Aditi)

• Multimedia company that wants to syndicate different backend services and offer single interface to end user
  • On the screen you should have a clickable map with different cameras that send video feeds
  • All these providers will provide portlets that will be registered
• Requirements
  • Must be able to support real time syndication of content where appropriate
  • Must be able to provide multimedia content (i.e. MPEG4, Flash)
• Functionality
  • Plug and play portlets
  • Real time syndication of content
  • Maintain a user profile to track user interest
• Questions?
  • Thomas - are multimedia resources directly streamed to the client or through the service?
    • Aditi - streamed directly, the markup from the service will provide the endpoint of the feed

News Feed Use Case (Adam)

• This revision is to address some comments on the original
  • About where persistent state is stored
  • About roles like administrator
  • Wasn't specifying what info the consumer would give to the provider specifically
• On ambiguity of preference info
  • Preferences from both user and admin
  • All preference data owned by portlet, portlet container only has to send a small set of prefs back and forth
  • Portlet container will send
    • End user id
    • Unique consumer id
    • Portlet instance id
    • Authentication info
  • Rest of info sent through explicit service calls
  • In the security group, we've talked about the portal saying to the portlet how it has been authenticated
    • Question: if there is republishing going on, the republishing consumer may not know how the end user was authenticated
• Cache behavior is important
  • Portlet container should update cache at a interval specified by admin
• Security
  • This should be dynamic, a bind time activity
• Questions?
  • No.

Call Adjourned