[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Groups - WSRP TC call modified
WSRP TC call has been modified by Rich Thompson Date: Thursday, 13 January 2005 Time: 11:00am - 12:00pm ET Event Description: USA Toll Free Number: 1-866-769-7222 USA Toll Number: 1-203-566-0687 PASSCODE: 849091 Agenda: 1. Accept F2F minutes? Need a new secretary ... volunteers? 2. SC reports/issues 2.a Interoperability (Richard) 2.b Conformance (Rich) 2.c WSDL (Andre) 2.d PFB (Richard) 2.e Coordination (Rich) 2.f Interfaces (Rich for Mike) - SC recommends moving copyPortlet and import/export proposals into the spec 2.g Primer (Subbu) 3. FAQ issues/discussion (Chris) 4. Errata items 4.1 CR304a - Rich to generate a schema file for an extension namespace and copy relevant definitions to there. 4.2 CR309 - Subbu to explore whether an extension element could turn on strict validation if the extensions element specifies lax validation. 5. V2 Specification 5.1 New version posted (draft 04). Any issues with the changes? 5.1.1 Note impact of CR306 on conformance statement in 6.1.10 - Mike proposed the wording be "If the cacheControl field is not supplied, the Portlet is indicating it does not consider the markup cacheable. This is without prejudice to consumer specific caching policies." 5.1.2 Andre pointed out the need to define semantics for the optional "scheduledDestruction" being missing. Rich suggests "When this field is missing from a response message, scheduled destruction is not in use and the explicit destruction operations MUST be used instead." 5.1.3 Mike has pointed out that the Consumer can consider publicParameters.capabilities to always be optional and mutable. 5.1.4 Andre pointed out that 'immutable' can be taken as unchanging and suggests using modifiable instead. 5.1.5 Suggest deleting the comment in 5.1.12. This is a left over question from early in the Coordination discussions and doesn't really fit with the current draft. 5.2 Open Issues: 5.2.1 #29 & 36: Apparent concensus on adding a wsrp-resourceID url parameter and change the semantics of wsrp-useOperation to be Portlet perference. The wsrp-url parameter indicates if/how the resource can be fetched using http and wsrp-resourceID parameter indicates if/how the resource can be fetched using the getResource operation. 5.2.2 #30: No one has stood up for InteractionParams other than portletStateChange. 5.2.3 #37: Recommend portletHandles be some form of UID. 6. While not definite yet, preliminary indications are that we will be able to have a 3-day F2F in New Orleans. 7. Other items? Minutes: This event is one in a list of recurring events. Other event dates in this series: Thursday, 09 December 2004, 11:00am to 12:00pm ET View event details: http://www.oasis-open.org/apps/org/workgroup/wsrp/event.php?event_id=6451 PLEASE NOTE: If the above link does not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]