1. 2005 All Hands Meeting Data & Data Integration Working Group Summary

2. Data interchange and identification Objectives  Requirements Ability for users and applications to access data using a “simple” identifier - uniquely identify data objects Ability for users and applications to understand data sets or objects they download - XML data descriptions Ability for data to be exchanged between applications and data stores - Data Services (w/ Workflow Working Group) Ability to query distributed and heterogeneous data - Semantic Data Integration (w/ Ontology Working Group)

3. Data interchange and identification Objectives  Requirements Ability for users and applications to access data using a “simple” identifier - uniquely identify data objects Ability for users and applications to understand data sets or objects they download - XML data descriptions Ability for data to be exchanged between applications and data stores - Data Services (w/ Workflow Working Group) Ability to query distributed and heterogeneous data - Semantic Data Integration (w/ Ontology Working Group)

4. Data Identification in Support of Data Sharing  BIRN is making data available for public use  Researchers need a way to cite/reference BIRN data  BIRN needs a way to provide unique identifiers to all BIRN data (i.e. similar to an accession number) Life Science Identifiers

5. Ability for users and applications to access data using a “simple” identifier - uniquely identify data objects Life Science Identifiers (LSIDs; http://lsid.sourceforge.net/ ) are the standard adopted by the Object Management Group (OMG) for the identification of life science data objects. They are a little like DOIs (http://www.doi.org/) used by many publishers. They provide a standard mechanism for retrieving data and metadata across different life science databases, containing diverse information and information types.http://www.doi.org/) LSID are used to refer to one unchanging data object each. Unlike the familiar URLs of the World-Wide-Web, LSIDs are location independent. This means that a program or a user can be certain that what they are dealing with is exactly the same data if the LSID of any object is the same as the LSID of another copy of the object obtained elsewhere.

6. Utilization of LSID in BIRN  Develop draft of BIRN LSID implementation Participants from each test bed and BIRN-CC Preliminary set of requirements gathered at this AHM Draft of implementation & target datasets - Early December  Finalize policies for BIRN LSID usage Spring 2006  Beta Implementation for 4.0 release Each test bed selects one data set to identify with BIRN LSIDs Register data from each data set

7. Data interchange and identification Objectives  Requirements Ability for users and applications to access data using a “simple” identifier - uniquely identify data objects Ability for users and applications to understand data sets or objects they download - XML data descriptions Ability for data to be exchanged between applications and data stores - Data Services (w/ Workflow Working Group) Ability to query distributed and heterogeneous data - Semantic Data Integration (w/ Ontology Working Group)

8. Improving Data Description and Interchange  Is there a way to describe & annotate BIRN data in a common framework Test-beds are developing “similar” XML schema  Is a cross test-bed XML representation a possibility?  A cross test-bed XML Working Group is being formed to investigate XML representation (e.g. XCEDE, WashU, Mouse BIRN)

9. XML Working Group  Dave Keator, Syam Gadde, Jeffrey Grethe – XCEDE  Dan Marcus – XNAT  Karen Crawford -- Mouse BIRN  Jeremy Bockholt – MIND Clinical Assessments  Relevant XML descriptions to be provided by end of November  First draft of merged schema - end of January  Face to Face meeting to resolve conflicts - fBIRN AHM

10. Data interchange and identification Objectives  Requirements Ability for users and applications to access data using a “simple” identifier - uniquely identify data objects Ability for users and applications to understand data sets or objects they download - XML data descriptions Ability for data to be exchanged between applications and data stores - Data Services (w/ Workflow Working Group) Ability to query distributed and heterogeneous data - Semantic Data Integration (w/ Ontology Working Group)

11. Data interchange and identification Objectives  Requirements Ability for users and applications to access data using a “simple” identifier - uniquely identify data objects Ability for users and applications to understand data sets or objects they download - XML data descriptions Ability for data to be exchanged between applications and data stores - Data Services (w/ Workflow Working Group) Ability to query distributed and heterogeneous data - Semantic Data Integration (w/ Ontology Working Group)

12. Use of Ontologies  Provide an “intuitive” and “natural” interface for the researcher based on concepts they are familiar with. Ontological Based Queries Data Source Requirements

13. Ontologies and Data Integration  Mark up will be provided to approved ontologies by the source provider All registered sources will export ontology mark up, definitions and relationships  Form, procedures and tools for source markup will be provided by Data Integration Team  The OTF will arrange for training sessions for BIRN participants in two areas: “Ontology Mark Up Boot camp”  December or January, prior to the test bed AHM’s Ontology development workshop in conjunction with the Stanford Team Conceptual issues involved in mapping sources

14. Concept Based Query Builder  User interface for ontology based query Consider recommendations of existing interfaces and preliminary discussions held at this AHM Project managers identify a group of test bed users to form a focus group (by SFN) Gather feedback at boot camp  Sit down with the domain scientists to review design Prototype by Spring (to be reviewed at the testbed AHM’s)