2006-06-07 Conference Call

Minutes recorded here: 2006-06-07 Conference Call Minutes

Conference Details

Draft Agenda (please comment)

  1. Development status update

    1. DXTrackWorkplan status update (Emek/Gary)

    2. Late 2005 Proposal for BioPAX Development/Discuss related tools update: ReleaseToolsProposal (Dan)

    3. BioPAX Validator / PAXerve interoperability (Ranjani)

    4. [WWW] debugging the bug E.coli data merge project (Jeremy/Alan) ([WWW] code repository) status update DebuggingTheBugMetabolicExample200606

  2. Governance. Gary action item to provide alternative wording for BioPAX Governance (action item from 3 calls ago). Wording is at CommunityDevelopmentProcess, and discussion at CommunityProcessDiscussion/Discussion_page

    1. Access control lists on wiki pages

    2. Status of [MAILTO] pax@cbio.mskcc.org email list

    3. Discussion: BIND patent - can it affect us or our users?

    4. Publication Guidelines?

  3. Future meetings

    1. Cold Spring Harbor meeting organization report (Emek) CSHF2Fmeeting/OrganizationMeetingNotes

      1. Budget - who is not going to use the CSHL meal plan?

      2. Discussion: What does acceptance of a DX proposal imply. Following up on an action item from the organizers meeting, Alan has drafted wording to set expectations:

        • DX proposals for consideration at this meeting will have two (different) data providers, present at the meeting, who would agree to use BioPAX to exchange data using the proposals. The decision we are trying to reach is whether the proposal doesn't have any obvious troubles for them to do that, and the community is being asked help them make sure that is the case.

          Following the meeting the next step in the process would be for those stakeholders to do the export. They would supply the BioPAX files created and two things would happen 1) Members of the community would review the exported data to see that it conforms to the spec, that it covers what it intends to cover, and to see what, if any, new problems arise. The stakeholders would then try to import the other one's generated BioPAX files and report on what issues, if any, arise. A subsequent meeting or set of teleconference calls would decide, based on these results, whether the proposals are accepted, and what to name them.

          This workshop will not address whether these proposals become part of a level 2 or level 3 release.

    2. ISMB

    3. ICSB/SBGN

last edited 2006-06-07 16:30:08 by JoanneLuciano