WSRP F2F Meeting Eleventh face to face meeting April 27 th – 29 th, 2005 New Orleans

WSRP F2F Meeting

Eleventh face to face meeting

April 27th – 29th, 2005

New Orleans

WSRP Technical Committee 2April 27, 2005

F2F Goals

Resolve those open issues that will make it into v2 and defer the rest


Agenda - Wednesday, April 27th

08:00 Coffee

09:00 Welcome, agenda, elect new secretary, changes at OASIS09:30 Carol Geyer & Andy Moir (OASIS)10:00 v2 Primer - Subbu10:30 Break

11:00 Change Requests CR310 – Add doctype related fields? CR311 – Use “event driven Consumer application”?

12:00 Lunch Break

13:00 Change Requests (cont) CR312 – Clarify InvalidSession fault CR313 – Clarify cookie usage CR314 – Change URI references to IRI?(see:

http://lists.w3.org/Archives/Public/www-xml-schema-comments/2005AprJun/0000.html) 15:30 Break

16:00 Versioning issues


Agenda - Thursday, April 28th

08:00 Coffee

09:00 Forms and Portlets – Mike10:00 FAQ - Clinton10:30 Break

11:00 Open Issues #21 – Introduce indications of Consumer functionality? #28 – Change requiresSecureDistribution to

authorizedNonSecureDistribution?12:00 Lunch Break

13:00 Open Issues (cont) #33 – Should leasing operations take a userContext? #34 – Why wildcards in publishedEvents? #35 – Policy changes that impact a registrations' lifetime

15:30 Break

16:00 Issue #37 – Encourage POP handles be UIDs


Agenda - Friday, April 29th

08:00 Coffee

09:00 Security Tech Note – Richard09:30 PFB Tech Notes – Richard10:00 Leveraging XOP/MTOM – Andre10:30 Break

11:00 Open Issues (cont) #38 – Operation signature style #39 – Default value for supportsExportByValue

12:00 Lunch Break

13:00 Open Issues (cont) #42 – Metadata needed concerning support for leasing?

14:00 Other items15:30 Break

16:00 Roadmap


Other items

Custom user profile items (see: http://www.oasis-open.org/archives/wsrp/200502/msg00020.html)

Blocking semantics of handleEvents? Config mode (see:

http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/download.php/9546/Consumer_Defined_Hierarchies.htm)

Popup windowstate (see: http://www.oasis-open.org/apps/org/workgroup/wsrp/email/archives/200504/msg00042.html)

URLs within resources (see: http://www.oasis-open.org/archives/wsrp-interfaces/200503/msg00034.html)

Define “renderEvents”? (improve fragment cachability) Others?


Items Mike F. raised recently

Page 10 Section 1.2.3: Description of Consumer -- I would like to extend/alter are description of the Consumer -- basically to move us to extend a notion of a consumer to those applications that view portlets as another type [albeit special] of view component in its toolset. "A Consumer is an application that incorporates, in part or as whole, an intermediary function that communicates with presentation-oriented web services (i.e. Producers and the Portlets they host) on behalf of its users. It gathers and aggregates the markup delivered by the Portlets and its other view components and presents this rendition to the End-User ..." and then leave the rest as is. However when we get down to the next section [1.2.4] it would be better worded as "The main purpose of a Consumer acting as a content intermediary for various Producer/Portlets is the preparation and presentation of markup to an End-User...." leave the rest as is.



Interface organization:1. I don't understand the logic for separating the Lifetime interfaces from their

natural interfaces. It would be okay if the natural interface were Lifetime independent -- but its not. -- give us fewer ports/interfaces to deal with.

2. Does anyone [consumer or producer] use the PortletManagement Property interface? This seems like it was a mistake. Even if not it seems of least importance in PortletManagement Interface. Can we move these methods to a new interface? Can we talk about deprecating them in the future?

3. Let's move CopyPortlet and ImportExport back into the PortletManagement Interface. PM is already an optional interface -- CopyPortlets/Import/Export are significantly more important to real consumer/producer portlet management then the property stuff ever was -- this will strongly encourage their implementation/support. If we do this merely add UnsupportedOperation Fault which can be thrown to signify lack of support/implementation.



Types for Event payloads, public parameters, and registration xxxx: We should have/use wording similar to extensions: "The use of types defined within the WSRP extra namespace is encouraged as this increases the likelihood of the Consumer being able to serialize/deserialize the data in a useful manner.

Section 5.1.11: EventTypeDescription: Does requiresSecureDistribution really mean requiresSecureTransport -- i.e. only that a secure transport mechanism must be used -- but not other security required? I assume so, however I wonder if we need to adjust these names as it may be somwhat confusing in the future when security is better supported.



Section 5.1.12: Should publicParameterDescriptions be of type ModelDescription not PropertyDescription? If so need to move this type as well [see editorial comment #10]

Section 5.2: lines starting at 43. Do the portletHandles have to reference POPs or can they reference cloned portlets? I prefer POPs -- if so need to restrict this in the language.

Section 6.1.18: HandleEventsFailed type: Should detail field really be an any? Better to make a string and leave the any for the extensions?



Section 6.1.19: handleEventsResponseType: Why does an event response return a redirect? How does this impact event processing?

Naming inconsistency between copyPortlets and Import/Export: CopyPortlet returns copySuccess/copyFailure fields with correpondingly named types. Import/Export returns imported/exportedPortlets;importFailure/exportFailure with corresponding types. We should reconcile.



The description for wsrp-urlType = resource is written with an eye towards consumers that don't support calling getResource() -- i.e. use of wsrp-resourceID and the wsrp-preferOperation parameters hint [strongly] for using the method call but don't require it -- however is this really true. Can't the Producer merely set wsrp-url to ""? Or do we strongly discourage producers from doing so. We might need to be more explicit as to our intentions here.

"While the Consumer MAY invoke handleEvent() multiple times for any one portlet while preparing to gather markup, it MUST NOT invoke handleEvent() an additional time while the portlet is already processing an event for the same End-User." This implies the consumer can't implicitly timeout an event call without dropping subsequent events from being distributed. Is this what we want? (sections 3.11 & 6.4.2.1)


Deferred items

Asynchronous notifications (leverage WSN?) Add a spec defined event for MetadataChanged

The portlet impacting other places on the page Consumer resources

needed for nested scripting Additional query args on a render url (see:

http://www.oasis-open.org/apps/org/workgroup/wsrp/email/archives/200504/msg00048.html)

Portlet URLs to other portlets Non-blocking performInteraction operation Event subscription (if experience warrants it) Portlet hierarchies Cache invalidation others?


Teleconference calendar

Wednesday 9 PT / 12 ET / 6 CET –Interfaces SC (as needed)

Thursday 8 PT / 11 ET / 5 CET – TC (biweekly)

Followed by Conformance/Interoperability/WSDL 8 PT / 11 ET / 5 CET – Primer (non-TC week)


WSRP Target Timeline

4/27-29/2005 F2F (New Orleans?) 5/20/2005 WSRP v2.0 at Committee draft 7/31/2005 WSRP v2.0 public review ends 8/15/2005 WSRP v2.0 submitted to OASIS 9/??/2005 F2F (Europe)

Discuss v3 use cases Host?

9/30/2005 WSRP v2.0 => OASIS standard

Documents

WSRP F2F Meeting Eleventh face to face meeting April 27 th – 29 th, 2005 New Orleans