[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp-wsia] Agenda for WSRP TC Call 9/19 8AM PST / 11 am EST / 5pm CET
Yes, those were the changes I have pointed to in a note yesterday or the
day before - the elapsed time for approval of new TC specs as OASIS
standards has been reduced significantly, a public review is now required
before submission.
Best regards,
Thomas
Rudnicki Joseph G CONT NSSC <RudnickiJG@NAVSEA.NAVY.MIL> on 09/18/2002
08:31:13 PM
To: Thomas Schaeck/Germany/IBM@IBMDE, wsrp-wsia@lists.oasis-open.org
cc:
Subject: RE: [wsrp-wsia] Agenda for WSRP TC Call 9/19 8AM PST / 11 am
EST / 5 pm CET
Hello,
If you have not had time, you may want to look at the new (as of two days
ago) OASIS TC process at http://www.oasis-open.org/committees/process.shtml
. There are some changes to specification approval.
Take care.
Joe Rudnicki
-----Original Message-----
From: Thomas Schaeck [mailto:SCHAECK@de.ibm.com]
Sent: Wednesday, September 18, 2002 2:11 PM
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] Agenda for WSRP TC Call 9/19 8AM PST / 11 am EST /
5 pm CET
Dear WSRP and WSIA TC Members,
here is the Agenda for the call tomorrow, Thursday 19th, 8 AM PST / 11 AM
EST / 5 PM CET:
Accept WSRP Minutes from 3rd Face to Face Meeting
-------------------------------------------------
For your reference, here are the minutes with a clarification from
Alejandro:
(See attached file: WSRP Meeting Sept 10th - 12th Minutes.doc)
Motion to allow the chair to place resolutions up for e-mail votes
------------------------------------------------------------------
At the last face to face meeting, it was proposed that we should in
addition to decisions made in phone calls and at face to face meetings
enable the TC to vote on certain topics by e-mail. This requires a motion
to be accepted by at least a 2/3 positive vote.
How do we handle voting on the TC Specification ?
-------------------------------------------------
The question was raised how we should handle voting on the TC
Specification. We need to discuss how we want to handle this.
Review schedule proposal and agree on further schedule
------------------------------------------------------
After the recent face to face meeting, I have discussed the schedule for
the WSRP 1.0 TC spec with Charlie and the spec editors. This is our
proposal:
Sept 27th Spec Editors provide draft 0.7 for review
Oct 7th TC has provided all comments on 0.7 draft
Oct 20th Spec Editors provide draft 0.8 for review
Nov 4th-8th 4th F2F: Resolve remaining tech. issues
Last opportunity to raise *tech.* issues for 1.0 Spec
Nov 22nd Editors finish draft 0.9 Proposal
Dec 16th TC provided all *editorial* comments on draft 0.9
Jan 7th Finish draft 0.9 reflecting edit. comments from TC
Put draft 0.9 on WSRP Web Site to get feedback
Jan 13th-17th 5th F2F: Finalize 1.0 TC Specification
If time permits discuss 2.0 direction/concepts
and compliance test kit
Location: West Coast Host: tbd
Jan 31st Release of WSRP 1.0 Technical Commitee Specification
Release of WSRP 1.0 Open Source Impl. at Apache
??? Compliance Test Kit ?
Issues to be discussed / resolved as of Rich's note:
----------------------------------------------------
1. (#1) No need for discussion of SOAP Proxy's
- More generally, how much should the spec teach general issues
rather than ones specific to WSRP/WSIA?
2. (#7) the Consumer must group together in the same shared context all of
the portlets that it is aggregating on behalf of a single End User session.
- Suggested addition: If the Consumer has no explicit reason to
provide a different groupID for entities from a given Producer, then it
SHOULD use the same groupID in order to enable Producer mediated sharing.
3. (#10) Collapsing consumerState into consumerHandle
- Suggest additional verbiage about invariance of handles vs the
variability of state pushed to the Consumer for storage.
4. (#16) Adding "lease" concept for registration
- Suggest deferring consideration out of v1.0
5. (#42) Why does consumer need to tell producer which extended attributes
it supports?
- Suggest adding verbiage about cases where data provided at
registration time impacts metadata returned in the context of that
registration.
6. (#44) Rename "expires" to "sessionExpires" in ResponseContext
- Since the sessionID field has been renamed newRefHandle, suggest
renaming this to handleExpires.
7. (#45) Signaling state change in InteractionResponse
- Suggest adopting the proposed semantics that navigationalState and
entityState are only returned when they change rather than carrying
additional changed flags or requiring Consumers to computationally
determine they have changed.
8. (#48) Should an entity's metadata state that it is cloneable?
- yes
9. (unassigned) Relation of Portlets, Portlet Instances and Producer
Offered Entities / Consumer Configured Entities
- Suggest guidance type statements either in the Intro or in the
discussion of cloneEntity(), whichever would provide the appropriate
context for the statements.
Callin info:
TIME: 08:00 AM PACIFIC TIME (11:00 Eastern)
DURATION: 2 hours
USA Toll Free Number: 877-302-8255
USA Toll Number: +1 303-928-2609
PASSCODE: 8814427
Best regards,
Thomas
Thomas Schaeck
Chairman OASIS WSRP TC
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC