Agenda Tuesday (sign up sheet, minutes taker) Ballot Review (David Fusari) Persistent Links (David Fusari) Inactive Context corner cases (Darrell Hansen) Wednesday Kerberos support (John Moerhke) 1.5 Next steps – membership ballot or wait (open discussion) Action items
To: CCOW Committee From: Rob Seliger Date: January 20, 2004 For the first time since hosting the founding meeting in December 1996, I am unable to attend a CCOW meeting. A combination of work and personal commitments coupled with the complexities of getting to/from a cross-country venue (at a warm location no less!) made it impossible for me to attend. However, with yet another unanimous ballot completed, and some very interesting new topics for discussion and analysis, I am confident that you all will have a productive forum. I look forward to hearing about this week’s meeting and most certainly look forward to seeing you all again in at the spring meeting. Sincerely,
Ballot Stats Committee Ballot Requirements Affirmative vote of at least 66.66% of combined affirmative and negative votes cast. Does not include abstentions. Must have quorum of 60% for any of the above (i.e., 60% of the pool must cast their vote). Results 95.92% of the pool voted (47 of 49 people) 39 voted Yes 8 abstained 0 voted No CCOW continues its perfect track record of ballots passing on the first round of voting.
Ballot Issues See spreadsheet and comments from David Tuma.
Persistent Subjects Use Case A user has launched multiple applications that are use link enabled. During the course of working with the applications the user had suspended an application from participating in the context. The user then logs out of an application still in context which prompts the user to signoff from all clinically linked applications. The user selects “OK”. All other apps still participating are notified that the user has signed off because the user context is now empty and logoff or terminate accordingly. The issue is that the user may assume they are signed off from the workstation but they have not, because the app that has suspended from the context was never notified of the context change. The next user then comes to the workstation and can potentially rejoin the context with the suspended app left running and, if the app has privileges, set the user subject to the apps current user and the new user can launch apps as the prior user. Possible Solution Characterize the user subject as being persistent (we now have characterizations such as transient and constant synchronization in 1.5). Which means even if an app is suspended it will still be notified when the user subject changes. Standards ramifications GUI Link status App behaviors for apps already CCOW enabled, can they handle being informed of a context change when they think they are in a suspended state?