Difference between revisions of "ConCall-20070124"
(Draft - being edited -) |
|||
| Line 15: | Line 15: | ||
:not https://www.gotomeeting.com/join/873285595 | :not https://www.gotomeeting.com/join/873285595 | ||
:GoToMeeting ID: 873-285-595 | :GoToMeeting ID: 873-285-595 | ||
| − | = | + | =Present= |
Beeler, Blobel, Buitendijk, Case, Hammond, Lorenzi, McCaslin, McCay, Parker, Walker | Beeler, Blobel, Buitendijk, Case, Hammond, Lorenzi, McCaslin, McCay, Parker, Walker | ||
| − | =Homework= | + | =Prior Homework= |
Review/update working items as: | Review/update working items as: | ||
*[[Core Challenges For T3F]] | *[[Core Challenges For T3F]] | ||
| Line 28: | Line 28: | ||
#''(10 min)'' Review, update [[T3F Action item list]] | #''(10 min)'' Review, update [[T3F Action item list]] | ||
## Review list of documents (McCay) | ## Review list of documents (McCay) | ||
| − | + | =Architecture= | |
| + | We moved architecture discussion to the beginning to accomodate Bert's time. He had concerns that the architure features and basic principles needed work and pointed everyone to the papers he has posted on this subject. He noted that quality, usability, scalability, and portability should be included. It was agreed that readability could be removed. He might draft suggestions on how to improve. Others on the call expressed an interest that we focus more time in the immediate future on operational and organizational aspects of T3F rather than architecture, that is, defining how the T3F will effectively ensure compliance with a technical architecture | ||
| + | =Core Challenges= | ||
| + | We discussed the role of "arb" during the transition. It was recommended that arb continue to do what it does today but should report to the T3F. | ||
| + | #Charlie edited the Core Challenges section on the wiki based on discussions. | ||
| + | #We discussion TD organization and the organizational charts presented. It was noted that the charts we've stored on the wiki are both somewhat misleading. The one from ORC looks "messy" but really represents the three areas - Foundation | ||
| + | rather than what it is. | ||
=[[T3F Agenda item list|Agenda item list (our sand box for future meetings)]]= | =[[T3F Agenda item list|Agenda item list (our sand box for future meetings)]]= | ||
=[[T3F Action item list|Click for T3F Action Item List]]= | =[[T3F Action item list|Click for T3F Action Item List]]= | ||
Revision as of 21:56, 27 January 2007
T3F - Transitional Technical Task Force
Conference Call is scheduled for 1.0 hour
Wed Jan 24, 2007 12:00 PM (US Eastern Time, GMT -5)
Please consult http://www.timeanddate.com/worldclock for your local times
Telephone conference Information - HL7 Conference Service
- Phone Number: 973-582-2813
- Participant Passcode: 124466
Online Meeting service - GoToMeeting
- for this meeting only : https://www.gotomeeting.com/join/949147364
- not https://www.gotomeeting.com/join/873285595
- GoToMeeting ID: 873-285-595
Contents
Present
Beeler, Blobel, Buitendijk, Case, Hammond, Lorenzi, McCaslin, McCay, Parker, Walker
Prior Homework
Review/update working items as:
Accepted Agenda
- (05 min) Roll Call & Accepted agenda
- (20 min) Refine Core Challenges For T3F
- Need Success Criteria
- (20 min) Complete top-level representation of Six Core Architecture Features
- (10 min) Review, update T3F Action item list
- Review list of documents (McCay)
Architecture
We moved architecture discussion to the beginning to accomodate Bert's time. He had concerns that the architure features and basic principles needed work and pointed everyone to the papers he has posted on this subject. He noted that quality, usability, scalability, and portability should be included. It was agreed that readability could be removed. He might draft suggestions on how to improve. Others on the call expressed an interest that we focus more time in the immediate future on operational and organizational aspects of T3F rather than architecture, that is, defining how the T3F will effectively ensure compliance with a technical architecture
Core Challenges
We discussed the role of "arb" during the transition. It was recommended that arb continue to do what it does today but should report to the T3F.
- Charlie edited the Core Challenges section on the wiki based on discussions.
- We discussion TD organization and the organizational charts presented. It was noted that the charts we've stored on the wiki are both somewhat misleading. The one from ORC looks "messy" but really represents the three areas - Foundation
rather than what it is.
