Synthetic Biology:Semantic web ontology

From OpenWetWare

(Difference between revisions)
Jump to: navigation, search
(Miscellaneous)
(Miscellaneous)
Line 59: Line 59:
*[http://slam.bs.jhmi.edu/gd/ GeneDesign β2.0]
*[http://slam.bs.jhmi.edu/gd/ GeneDesign β2.0]
*[http://researchweb.watson.ibm.com/journal/sj/402/haas.html IBM DiscoveryLink] provides users with a virtual database to which they can pose arbitrarily complex queries, even though the actual data needed to answer the query may originate from several different sources, and none of those sources, by itself, is capable of answering the query (data integration)
*[http://researchweb.watson.ibm.com/journal/sj/402/haas.html IBM DiscoveryLink] provides users with a virtual database to which they can pose arbitrarily complex queries, even though the actual data needed to answer the query may originate from several different sources, and none of those sources, by itself, is capable of answering the query (data integration)
 +
 +
===Lowercase semantic web===
 +
*[[Wikipedia:Microformats|Microformats]]
Contact: [[User:Ilya|Ilya Sytchev]]
Contact: [[User:Ilya|Ilya Sytchev]]

Revision as of 02:36, 6 September 2006

Home        About        Conferences        Labs        Courses        Resources        FAQ       

Overview

This is a part of the effort to provide a standardized, extensible, scalable and machine-processable interface for the Registry of Standard Biological Parts. The ideas of the Semantic Web seem to provide a solution to this problem. The success of developing a Synthetic Biology ontology depends in part on a good definition of the BioBricks abstraction hierarchy.

Registry features

Compiled from meetings and Registry_of_Standard_Biological_Parts

  • Subpart Search: search for parts that match a portion of this part or this sequence of parts. Software agent would take a part name and using the ontology definitions would query other registries via their semantic web interfaces (no need to know about schema: e.g., just say "need all <#part>s that match a <#component> of the given <#part>"). Software agent can search anyone's registry if they use a common ontology: simply follow URLs (or use query language) and add triples to the local RDF store.
  • Superpart Search: search for parts that contain the given parts
  • What about sub- and superpart searches in distributed registries?
  • Search for function (case insensitive): repressor, reporter, inverter, etc.
  • What are the available (instances of) parts? Are they used in any devices already? (saves time for constructing expression device). Problem: different names for exactly same DNA sequence
  • What kinds of devices/systems have been built?
  • Search for "similar" parts
  • Find all parts of the form promoter.Q04400 where promoter can be any promoter. It would also be nice to specify whether you want any parts, just available parts or available and working parts.

Implementation

  • Possible initial architecture of the Registry: Adapting SQL Databases (slide 20)
    • Persistent RDF store (MySQL + Jena)
  • Possible final architecture of the Registry: Triple Store (slide 19)

Meetings

First meeting

Tuesday (9/20/05) at 3pm, room 68-674
Minutes

Second meeting

Friday (9/23/05) at 10am, room 68-121
Minutes

References

Miscellaneous

Lowercase semantic web

Contact: Ilya Sytchev

This site is hosted on OpenWetWare and can be edited by all members of the Synthetic Biology community.
Making life better, one part at a time.


Personal tools