Difference between revisions of "SDIWG:Meeting Minutes 20080222"

From NAMIC Wiki
Jump to: navigation, search
m
m
 
Line 20: Line 20:
 
**Overview of how iTools accesses the current corpus of three proto-biositemaps (google”filtetype:xml biositemap”). (Ivo)  
 
**Overview of how iTools accesses the current corpus of three proto-biositemaps (google”filtetype:xml biositemap”). (Ivo)  
 
**Overview of plan for next 2 to 4 months (Peter)  
 
**Overview of plan for next 2 to 4 months (Peter)  
***(1) In the next two months NCBO develops a stable platform for content development and content repository in bioportal relating to the resource ontology, culminating in ½ to 1 day tcon with authorized seven Center reps to finalize v1.0 resource ontology (I may add rep from NITRC and NIF, Bill Bug).  NCBO is generating and executing the plan for the ‘stable platform’
+
***(1) In the next two months NCBO develops a stable platform for content development and content repository in bioportal relating to the Biomedical Resource Ontology (BRO), culminating in ½ to 1 day tcon with authorized seven Center reps to finalize v1.0 resource ontology (I may add rep from NITRC and NIF, Bill Bug).  NCBO is generating and executing the plan for the ‘stable platform’.  It is likely that this will involve some merging of the development process with NIF and NITRC, but that is yet to be resolved.
 
***(2) After that Lyster contacts each PI and get personal commitment to create biositemaps.xml content on their web sites.
 
***(2) After that Lyster contacts each PI and get personal commitment to create biositemaps.xml content on their web sites.
 
*
 
*
Line 39: Line 39:
 
**Daniel will put the current BRO on a Stanford gforge where it can be used by the NCBC SDIWG contacts to agree on a common BRO.   
 
**Daniel will put the current BRO on a Stanford gforge where it can be used by the NCBC SDIWG contacts to agree on a common BRO.   
 
**Daniel has written, after the tcon, a brief description for immediate conversion from biositemaps based on xml to biositemaps: First, we will translated BRO to OWL (BRO.owl) and create a new class in the BRO ontology called "ResourceDescription" which represents the collection of all descriptions of resources (each instance of this class will be equivalent to a single resource description in a biositemaps.xml file). Then BRO.owl would be published to the Web so the world can reference this class and create instances of it; the preferred tool for doing that will be Protege. So each NCBC would launch protege, then open the URL to the BRO.owl file, and create instances of the ResourceDescription class for each tool they wish to describe (what they are doing is creating a new OWL file which stores only instances of the ResourceDescription class). Then they save their OWL file and publish it on the Web on their own server (we'll call that file a ResourceDescription.owl file; Peter would prefer if it were named the biositemaps.owl for the sake of continuity). Then Ontrez (this has been since renamed the Resources Tab) would consume the ResourceDescription.owl files from all NCBCs that are published to the Web and index them using BRO, resulting in a demo similar to that I showed today. But now we're totally operating within Semantic Web technologies--others on the Semantic Web could also consume the ResourceDescription.owl files for their own purposes independent of Ontrez.  This change would require Ivo to do some re-coding so that iTools consumes (parses) the ResourceDescription.owl files instead of parsing the biositemaps.xml files. This should not be a very tedious operation, and only need be done once.
 
**Daniel has written, after the tcon, a brief description for immediate conversion from biositemaps based on xml to biositemaps: First, we will translated BRO to OWL (BRO.owl) and create a new class in the BRO ontology called "ResourceDescription" which represents the collection of all descriptions of resources (each instance of this class will be equivalent to a single resource description in a biositemaps.xml file). Then BRO.owl would be published to the Web so the world can reference this class and create instances of it; the preferred tool for doing that will be Protege. So each NCBC would launch protege, then open the URL to the BRO.owl file, and create instances of the ResourceDescription class for each tool they wish to describe (what they are doing is creating a new OWL file which stores only instances of the ResourceDescription class). Then they save their OWL file and publish it on the Web on their own server (we'll call that file a ResourceDescription.owl file; Peter would prefer if it were named the biositemaps.owl for the sake of continuity). Then Ontrez (this has been since renamed the Resources Tab) would consume the ResourceDescription.owl files from all NCBCs that are published to the Web and index them using BRO, resulting in a demo similar to that I showed today. But now we're totally operating within Semantic Web technologies--others on the Semantic Web could also consume the ResourceDescription.owl files for their own purposes independent of Ontrez.  This change would require Ivo to do some re-coding so that iTools consumes (parses) the ResourceDescription.owl files instead of parsing the biositemaps.xml files. This should not be a very tedious operation, and only need be done once.
 +
**Overview of plan for next 2 to 4 months (Peter)
 +
***(1) In the next two months NCBO develops a stable platform for content development and content repository in bioportal relating to the Biomedical Resource Ontology (BRO), culminating in ½ to 1 day tcon with authorized seven Center reps to finalize v1.0 resource ontology (I may add rep from NITRC and NIF, Bill Bug).  NCBO is generating and executing the plan for the ‘stable platform’.  It is likely that this will involve some merging of the development process with NIF and NITRC, but that is yet to be resolved.
 +
***(2) After that Lyster contacts each PI and get personal commitment to create biositemaps.xml content on their web sites.
  
 
*Go over dates for next year's meetings:
 
*Go over dates for next year's meetings:
Line 50: Line 53:
 
* Convert Biositemaps method to owl
 
* Convert Biositemaps method to owl
 
* Convene SDIWG tcon (probably lasting 1/2 day to agree on a common BRO)
 
* Convene SDIWG tcon (probably lasting 1/2 day to agree on a common BRO)
 +
**Overview of plan for next 2 to 4 months (Peter)
 +
***(1) In the next two months NCBO develops a stable platform for content development and content repository in bioportal relating to the Biomedical Resource Ontology (BRO), culminating in ½ to 1 day tcon with authorized seven Center reps to finalize v1.0 resource ontology (I may add rep from NITRC and NIF, Bill Bug).  NCBO is generating and executing the plan for the ‘stable platform’.  It is likely that this will involve some merging of the development process with NIF and NITRC, but that is yet to be resolved.
 +
***(2) After that Lyster contacts each PI and get personal commitment to create biositemaps.xml content on their web sites.
  
  

Latest revision as of 17:53, 7 March 2008

Home < SDIWG:Meeting Minutes 20080222

Agenda: NCBC Joint Working Group Meeting

Top page of SDIWG web site

Notes

Friday February 22, 2008: 2:30 -- 3:30 PM EST
Please contact Peter Lyster for information Peter Lyster
SDIWG Meetings Page
Save the date for the next SDWIG tcon/Connect, three months from now: Friday May 16, 2008

Tcon DRAFT Agenda

  • Roll Call/Note-taker (Henry Chueh) (5 min)
  • Minutes from most recent SDIWG tcon Nov 16, 2007 (5 min)
  • NCBC All Hands Meeting, August 13-15, 2008. Planning & Brainstorm discussion (Peter, Karin, All)
  • Status check on three working groups: Biositemaps Resourceome, Scientific Ontologies, NCBC Driving Biological Projects Interactions and Impact
  • Demo on Biomedical Resource Ontology (see BRO Requirements document) (Daniel Rubin). The demo will describe a stable development environment for the BRO and repository in BioPortal. This is a key component of the Biositemaps effort.
    • Overview of white paper (‘the biositemaps concept’) (Daniel, Ivo, Peter)
    • Overview of (i) collaborative development environment for BRO and (ii) BioPortal repository of BRO (how is BRO accessed through API?) (Daniel)
    • Overview of how iTools accesses the current corpus of three proto-biositemaps (google”filtetype:xml biositemap”). (Ivo)
    • Overview of plan for next 2 to 4 months (Peter)
      • (1) In the next two months NCBO develops a stable platform for content development and content repository in bioportal relating to the Biomedical Resource Ontology (BRO), culminating in ½ to 1 day tcon with authorized seven Center reps to finalize v1.0 resource ontology (I may add rep from NITRC and NIF, Bill Bug). NCBO is generating and executing the plan for the ‘stable platform’. It is likely that this will involve some merging of the development process with NIF and NITRC, but that is yet to be resolved.
      • (2) After that Lyster contacts each PI and get personal commitment to create biositemaps.xml content on their web sites.
  • Upcoming meetings: AMIA translational, Zac, ...
  • Next 2 meeting date (Friday May 16 2:30 PM ET and three months after that)
  • Questions/Information Sharing


Minutes

Note taker: (Peter Lyster) [Suggested order of note takers for future meetings: Chueh (this one); Sherman; Schroeder; Floratos; Rubin; Jags, Dinov]

  • Review of November 16, 2007 Minutes
  • Attendees: Daniel Rubin, Ivo Dinov, Karen Skinner, Karin Remington, David Kennedy, Olivier Bodenreider
    • Daniel showed Biomedical Resource Ontology (BRO) and other ontologies/terminologes (e.g., NCI Thesaurus) in Bioportal
    • Daniel described the link between the BRO and Ontrez which is the NCBO tool for curated indexing of resources (this uses the terminologies, including BRO that are in Bioportal); Daniel shows the Mapping capability
    • There was a general discussion of the development environment for the BRO—currently it exits as (i) the primary content is in Daniel’s private repository (CVS) (thus the full complement of old versions are not propagated into BioPortal, although BioPortal does show the difference between the current and immediately previous version); (ii) annotations that can be entered directly into Bioportal.
    • Daniel will put the current BRO on a Stanford gforge where it can be used by the NCBC SDIWG contacts to agree on a common BRO.
    • Daniel has written, after the tcon, a brief description for immediate conversion from biositemaps based on xml to biositemaps: First, we will translated BRO to OWL (BRO.owl) and create a new class in the BRO ontology called "ResourceDescription" which represents the collection of all descriptions of resources (each instance of this class will be equivalent to a single resource description in a biositemaps.xml file). Then BRO.owl would be published to the Web so the world can reference this class and create instances of it; the preferred tool for doing that will be Protege. So each NCBC would launch protege, then open the URL to the BRO.owl file, and create instances of the ResourceDescription class for each tool they wish to describe (what they are doing is creating a new OWL file which stores only instances of the ResourceDescription class). Then they save their OWL file and publish it on the Web on their own server (we'll call that file a ResourceDescription.owl file; Peter would prefer if it were named the biositemaps.owl for the sake of continuity). Then Ontrez (this has been since renamed the Resources Tab) would consume the ResourceDescription.owl files from all NCBCs that are published to the Web and index them using BRO, resulting in a demo similar to that I showed today. But now we're totally operating within Semantic Web technologies--others on the Semantic Web could also consume the ResourceDescription.owl files for their own purposes independent of Ontrez. This change would require Ivo to do some re-coding so that iTools consumes (parses) the ResourceDescription.owl files instead of parsing the biositemaps.xml files. This should not be a very tedious operation, and only need be done once.
    • Overview of plan for next 2 to 4 months (Peter)
      • (1) In the next two months NCBO develops a stable platform for content development and content repository in bioportal relating to the Biomedical Resource Ontology (BRO), culminating in ½ to 1 day tcon with authorized seven Center reps to finalize v1.0 resource ontology (I may add rep from NITRC and NIF, Bill Bug). NCBO is generating and executing the plan for the ‘stable platform’. It is likely that this will involve some merging of the development process with NIF and NITRC, but that is yet to be resolved.
      • (2) After that Lyster contacts each PI and get personal commitment to create biositemaps.xml content on their web sites.

Action Items

  • Convert Biositemaps method to owl
  • Convene SDIWG tcon (probably lasting 1/2 day to agree on a common BRO)
    • Overview of plan for next 2 to 4 months (Peter)
      • (1) In the next two months NCBO develops a stable platform for content development and content repository in bioportal relating to the Biomedical Resource Ontology (BRO), culminating in ½ to 1 day tcon with authorized seven Center reps to finalize v1.0 resource ontology (I may add rep from NITRC and NIF, Bill Bug). NCBO is generating and executing the plan for the ‘stable platform’. It is likely that this will involve some merging of the development process with NIF and NITRC, but that is yet to be resolved.
      • (2) After that Lyster contacts each PI and get personal commitment to create biositemaps.xml content on their web sites.


Appendix: Biositemaps white paper