[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 Atul Batra Date: Thursday, 10 March 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 previous two sets of minutes? 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 (Mike) 2.g Primer (Subbu) 3. FAQ issues/discussion (Clinton) 4. Errata items 4.1 CR304a - Rich updated the schema file for the extension namespace, comments? 4.2 CR309 - Specify lax validation on our extension element? 5. V2 Specification 5.1 Draft 05 is the current version. 5.2 Open Issues and Proposed resolutions: 5.2.1 Issue #32 (Proposed resolution): 1. Add a Lifetime parameter to register, modifyRegistration, clonePortlet, copyPortlets and exportPortlets operations. 2. Define semantics that the presence of a Lifetime parameter on these requests indicates: a. The Consumer prefers the returned resource be leased b. The supplied Lifetime value indicates what the Consumer would otherwise supply in a subsequent setxxxLifetime invocation 3. Define semantics that the absence of a Lifetime parameter on these requests (other than modifyRegistration) indicates the Consumer prefer the resource not be leased. For modifyRegistration, the absence of a Lifetime parameter indicates the Consumer is not requesting a change to the lease expiry on the registration resource. 5.2.2 Issue #41 (Proposed resolution): At least for draft 06 of the specification, move the new factories (copyPortlets and exportPortlets) to new portTypes, remove ServiceDescription metadata about supported factories and consider under issue #40 whether import and export should be in separate portTypes. 5.2.2 Issue #40 (open): Question raised about Producers separating support for import and export. 5.2.2 Issue #42 (new): Metadata needed concerning support for leasing? 5.2.2 Issue #43 (new): Collapse HandleEventResponse and BlockingInteractionResponse? 6. April F2F: April 27-29 (follows OASIS Symposium in New Orleans) - plan for 9-5 all three days - Goal: Close all issues which will be allowed to impact v2. - If possible hosts for the following F2F could contact Rich, it would assist planning. - Note: Rich will start enforcing attendance rules for the purpose of attaining quorum in New Orleans 7. Other items? Minutes: Minutes of WSRP TC Call 10 March 2005 Meeting started at 8:00AM PST ==================================================================== Quorum was reached (13 members in attendance) 1. Accept previous two sets of minutes? Yes, accepted. 2. SC reports/issues None of the SCs met since the previous TC call. 2.a Interoperability (Richard) 2.b Conformance (Rich) 2.c WSDL (Andre) Andre gave the update that Atul tested the JAX-RPC RI v1.2.2_01 with the v2 draft WSDLs and did not run into any issues with the tools. He also mentioned that one remaning Axis bug is being addressed Clinton and Andre noted that usage of handlekey and handle types were the main issues for stacks in the past. In the past main issues were realted to to xml schemas. WS-I is helping here. 2.d PFB (Richard) Update from Richard on UDDI TN. He is trying to get the partition scheme into the OASIS naming convention documents with the help from the TC Charis. and Bill Cox. There will be no impact of this on the ebXML TN. 2.e Coordination (Rich) 2.f Interfaces (Mike) 2.g Primer (Subbu) Rich enquired if it was time to start looking into the Primer for v2. Subbu to initiate that. 3. FAQ issues/discussion (Clinton) Clinton noted that he had uploaded a new copy of the FAQ based on suggestions send by Subbu. 4. Errata items 4.1 CR304a - Rich updated the schema file for the extension namespace, comments? Rich asked folks to review changes (document is the extention types). Namedstring change was discussed. Moved the effective content from namedstring in a element to being an attribute. No need to keep the overhead of keeping the element around (Rich's preference is to have the type namespace to import and use it). Subbu noted that it is confusing if there are two namedstrings from two namespaces. Rich - real quesiton is that do we need to have 3 -- i.e. for v1, v2 and the extra. 4.2 CR309 - Specify lax validation on our extension element? There was no qurom last time so we need to decide now. So any objections to setting extention elements to have a processContexts that can equal to lax None, consider that approved. Subbu asked if this was also an errata item for 1.0. Yes. 5. V2 Specification 5.1 Draft 05 is the current version. Rich mentioned that the draft was sent out so all should review. 5.2 Open Issues and Proposed resolutions: 5.2.1 Issue #32 (Proposed resolution): 1. Add a Lifetime parameter to register, modifyRegistration, clonePortlet, copyPortlets and exportPortlets operations. Add param to lifetime operations? 2. Define semantics that the presence of a Lifetime parameter on these requests indicates: a. The Consumer prefers the returned resource be leased b. The supplied Lifetime value indicates what the Consumer would otherwise supply in a subsequent setxxxLifetime invocation 3. Define semantics that the absence of a Lifetime parameter on these requests (other than modifyRegistration) indicates the Consumer prefer the resource not be leased. For modifyRegistration, the absence of a Lifetime parameter indicates the Consumer is not requesting a change to the lease expiry on the registration resource. Richard noted that this may collide with another issue. What if the consumer wanted infinite lifetime, i.e. if the consumer did not provide a lifetime, then the lifetime was infinite. Atul noted that this would be an issue if there was an initial lifetime, and then the consumer wanted to make that infinite, how to accomplish via modifyRegistration? Rich clarified that answer would be use lifetime operation to make that change (not modifyRegistration). So esentially for factory operations -- it it's passed, consumer is requesting leasing. if it's absent, consumer is requesting it not be leased And -- drop lifetime from modifyRegistryation This one is considered resolved and approved. 5.2.2 Issue #41 (Proposed resolution): At least for draft 06 of the specification, move the new factories (copyPortlets and exportPortlets) to new portTypes, remove ServiceDescription metadata about supported factories and consider under issue #40 whether import and export should be in separate portTypes. Considered approved. 5.2.3 Issue #40 (open): Question raised about Producers separating support for import and export. Andre has raised this one in the context of meta-data using flags. After discussion, leaning on not allowing seperate, but rather allow producer to throw faults to indicate supported/ non-supported for the import or export. 5.2.4 Issue #42 (new): Metadata needed concerning support for leasing? Today we implicitly assume that consumers support lifetime. Producer indicates that it supports leasing by the port types, but it does not indicate if it requires leasing. Issue is that the Producer may expire a lifetime, and the consumer may try and keep using the portlet. How about introducing meta data in the Service Description that indicats that leasing is "required" by the Producer. Just be explict in the spec - leasing is required if the port types are exposed. Richard noted a use case whereby gold customer may require infinte leasing. This one to be discussed further. 5.2.5 Issue #43 (new): Collapse HandleEventResponse and BlockingInteractionResponse? Artem had raise the issue of keeping distinct. Currently in the WSDL -- both are of the same type, but distinct elements. Rich mentioned that jax-rpc requires the response type to be named after the operations. Andre - issues earlier with tools, we should try and collapse now. 6. April F2F: April 27-29 (follows OASIS Symposium in New Orleans) - plan for 9-5 all three days - Goal: Close all issues which will be allowed to impact v2. - If possible hosts for the following F2F could contact Rich, it would assist planning. - Note: Rich will start enforcing attendance rules for the purpose of attaining quorum in New Orleans Rich noted that folks should play for 9 to 5pm on all three days since this F2F is shorter. 7. Other items? We need to look for sites for the next F2F (after New Orleans). West Coast or Europe? New Orleans considered part of the West Coast rotation, next one can be Europe. Folks to try and look for suitable facilites in Europe. Meeting ended 9:00AM PST ================================================================================== This event is one in a list of recurring events. Other event dates in this series: Thursday, 27 January 2005, 11:00am to 12:00pm ET Thursday, 10 February 2005, 11:00am to 12:00pm ET Thursday, 24 February 2005, 11:00am to 12:00pm ET Thursday, 24 March 2005, 11:00am to 12:00pm ET Thursday, 07 April 2005, 11:00am to 12:00pm ET Thursday, 21 April 2005, 11:00am to 12:00pm ET View event details: http://www.oasis-open.org/apps/org/workgroup/wsrp/event.php?event_id=6795 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. Referenced Items Date Name Type ---- ---- ---- 2005-03-10 minutes_03102005.txt Minutes
BEGIN:VCALENDAR METHOD:PUBLISH VERSION:2.0 PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN X-WR-CALNAME:My Calendar BEGIN:VEVENT CATEGORIES:MEETING STATUS:TENTATIVE DTSTAMP:20050310T000000Z DTSTART:20050310T160000Z DTEND:20050310T170000Z SEQUENCE:8 SUMMARY:WSRP TC call DESCRIPTION:USA Toll Free Number: 1-866-769-7222\nUSA Toll Number: 1-203-566-0687\nPASSCODE: 849091\n\nGroup: OASIS Web Services for Remote Portlets (WSRP) TC\nCreator: Rich Thompson URL:http://www.oasis-open.org/apps/org/workgroup/wsrp/event.php?event_id=6795 UID:http://www.oasis-open.org/apps/org/workgroup/wsrp/event.php?event_id=6795 END:VEVENT END:VCALENDAR
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]