SDI: Agenda for July 8 meeting in Bethesda

From NAMIC
Jump to: navigation, search
Home < SDI: Agenda for July 8 meeting in Bethesda

Agenda Items July 8 (2005) NIH Roadmap Software and Data Integration (SDI) meeting Bethesda MD

Marriott Bethesda North Hotel and Conference Center, 5701 Marinelli Road, North Bethesda, MD 20852 (301-822-9200)


Introduction

This will be the first in-person meeting held under the auspices of the Software and Data Integration team comprised of the Working Group of NIH-staff plus the Centers' liaisons. Currently there are four Centers, and three more will be added early in the Fall of 2005. Hence we expect to add the new Centers to the discussion later in the Fall.

The Charter of SDI is: The RFA states the goal of creating “the networked national effort to build the computational infrastructure for biomedical computing for the nation”. Here is a link to relevant text in the Announcement RFA-RM-04-003. In furthering this, the goals of the SDIWG in concert with the Project Team and Centers staff are:

1. To advance the domain sciences, and promote software interoperability and data exchange.

2. To capture the collective knowledge of software engineering and practices among the Centers and publish this knowledge widely.

By the time we meet on July 8 we will have had a series of monthly tcons, summarized in the minutes pages on this wiki and in the ongoing thread, and decide on a path that will further the networked national effort.

Detailed Agenda

Thursday July 7

  • 8 PM: Informal gathering of PIs and Liaisons with Peter Lyster after the conclusion of the Evaluation meeting

Friday July 8

  • 10:00 - 10:15 AM: Coffee Break
  • 10:15 - Noon: Discussion of Software Engineering and NIH-forge
  • Noon set up for working lunch
  • 1:30 - 3:00 PM: National Infrastructure Demonstrations
  • 3:00 - 3:30 PM: Wrap Up and Action Items

Proposed Outline for 20+5 min NCBC Center talks (Ivo Dinov)

1. Science developments

2. Center Grand Challenges

3. Progress on SW development, CCB Software Management System (SMS)

3.a Internal SW design, policies, SMS

3.b External SW design, policies, SMS

4. Data Sharing

5. Center interactions with other NCBCs

6. NCBC as a National infrastructure for biomedical computing - should stress out the collaborative NCBC Center-linked projects as the backbone for the infrastucture, instead of asking for 4 (or 7) NCBC centers to be fully interoperable and "uniform"

7. SW and Data Licenses


Proposed Meeting Goals

1 To identify the elements and activities the Centers believe describe a broad national biomedical computing framework--this includes interactions among the Centers as well as with other related efforts in biomedical computing. An important consideration is the appropriate balance between (i) the SDI efforts within each Center, and (ii) the combined SDI efforts across all Centers and the broader community.

2 To identify the role of the Centers in this broader framework.

3 To identify steps necessary to exploit opportunities and address gaps for achieving a national biomedical computing framework. Substantive efforts may include:

  • a. NCBC Portal.
  • b. Explore NIH-forge, Frameworks, or Clearinghouse. A substantive effort may involve the development of common federated software repositories and the associated community software building effort that such repositories entail read further. These may be used to foster software reuse and/or concurrent software development. The key to federation is that control of software repositories is retained at the developer sites, while a lightweight overarching management structure means that the broad developer community is not confronted with balkanized access, change, test, and build procedures.
  • c. Data repositories: issues include the temporal order of creation, maintenance, and their independence/dependence.
  • d. Interoperability: the broad issues are developed in the caBIG Compatibility Guidelines [5]. One suggestion is the use of interoperability demonstrations as a driver. The Centers have already identified areas of common domain overlap (these will be described briefly on July 8), and these will be a logical choice for meaningful interoperability demonstrations.
  • e. The use of Pipelines (e.g., CCB Pipeline). This may be used to foster software reuse and flexible composition of applications.
  • f. Certification of software quality, levels of trust (component or application level).
  • g. Other? Add new items here

4. To define players, milestones and timelines for implementing these efforts

Source Documents

  1. The Cathedral and the Bazaar: Manifesto of the Open Source movement by Eric S. Raymond
  2. The caBIG Compatibility Guidelines. The NCI Center for Bioinformatics Open Development Initiative.
  3. Recent talk by P. Lyster on Open Source Software Frameworks.
  4. Zerhouni-gram matrix: as generated from the original Roadmap meetings on Bioinformatics and Computational Biology.
  5. Presentation by Ivo Dinov at 07/22/05 NCRR-NIBIB P41 meeting: Center for Computational Biology;
  6. Presentations by Bill Lorensen at 07/22/05 NCRR-NIBIB P41 meeting:Open, Distributed and Collaborative Software Development & Open Software Engineering.
  7. Presentation by Isaac Kohane 07/22/05 NCRR-NIBIB P41 meeting: Turning Healthcare System into Reseaerch Engine

File:CCB NCBC Presentation July08 05 Dinov.ppt

Feel free to add others…