<title>Background</title> <p>The abundance of data in the post-genomics era is a major boon for life science researchers. However, data from disparate sources arguably have the most value when considered in context with each other. For example, manually curated experimental evidence may be more reliable than computational predictions, but the latter may offer greater coverage. Whilst drawing conclusions based on the results of multiple experiments is by no means a new concept in biology, <italic>omics </italic>data and <italic>in silico </italic>analyses make traditional <italic>ad hoc </italic>methods of publishing and sharing data impractical. With the trend for data expansion set to continue and the highly collaborative approaches of major projects such as ENCODE [##REF##17571346##1##], integration is likely to become an increasingly important focus of bioinformatics.</p> <p>Efforts to integrate data sources may be broadly categorised by their motivation:</p> <p>1. aggregating and presenting data in an accessible format</p> <p>2. computational analysis of combined data sets</p> <p>3. federation of disparate resources</p> <p>Each of these goals, although not necessarily mutually exclusive, has its own requirements. For example, whilst user interfaces must be responsive and accessible, computational analysis requires robust semantics.</p> <title>DAS overview</title> <p>The Distributed Annotation System (DAS) [##REF##11667947##2##] was originally conceived as a mechanism to aggregate and display genome sequence annotations such as transcript predictions. It is built upon the principle that data should remain spread across multiple sites, rather than aggregated into centralised databases. Thus data providers retain control over data access, releases can be more dynamic and changes to file formats or database structures are transparent. DAS has a "dumb server, clever client" architecture, which holds a number of advantages. For example, the minimal resources and time required of data providers to expose their data means more sources can be integrated and more readily. Conversely, one of the main reasons for this ease of implementation is a lack of enforced semantics, which limits applications primarily to visual display. In addition, DAS has been lacking a central registry of available data sources.</p> <p>DAS was developed by WormBase [##REF##17099234##3##] for sharing genome annotations, and was adopted by the Ensembl project [##REF##18000006##4##] to facilitate the display of such distributed data in its genome browser. The applicability of DAS was extended to protein sequence and structure data by the efforts of the eFamily project to integrate five of the major protein databases [##UREF##0##5##,##REF##17850653##6##]. It was subsequently adopted by the BioSapiens Network of Excellence as the mechanism of sharing proteomics data among member institutions [##REF##15980514##7##,##REF##16651373##8##], and also by the ENCODE project to dynamically share the latest data between collaborators. Many other individual projects across the world also expose their data and/or operate integration services via DAS.</p> <p>As a standard for the sharing of biological information, the DAS protocol defines how data should be represented and communicated. It takes the form of a web service based upon the open standards of Hyper-Text Transfer Protocol (HTTP) for data transmission and Extensible Markup Language (XML) for data format. A DAS server may host a number of sources, each differing in the services it provides and the type of underlying data it is based on.</p> <title>Coordinate systems</title> <p>DAS may be used to annotate different types of data. In order to distinguish these, <italic>coordinate systems </italic>describe the various reference data types DAS supports. Each coordinate system may be thought of as a model that bioinformaticians commonly use to denote biological entities and locations of features within them. A coordinate system has four parts:</p> <p>1. The <bold>category </bold>or type of annotatable entity. For example a chromosome, gene, protein sequence or protein structure.</p> <p>2. The <bold>authority </bold>or project responsible for defining the coordinate system. For example NCBI, UniProt or Ensembl.</p> <p>3. The <bold>version</bold>, used where entities themselves are not versioned (as in genomic assemblies).</p> <p>4. The <bold>species</bold>, for coordinate systems containing only entities from a single organism.</p> <p>Though coordinate systems are normally used to describe the location of a feature within a reference entity (for example residue 26 of UniProt sequence P15056), some annotations are not always associated with a sequence location but rather the entity itself (for example database cross-references). Such features are commonly called <italic>non-positional features </italic>and are used most when annotating genes, which themselves are often thought of as abstract entities. The difference between annotating an entity versus a region of an entity's sequence is conceptual and requires no special implementation for a data source, but does have implications for a client's display.</p> <title>DAS commands</title> <p>A DAS source may offer one or more different services to clients, determined by the <italic>commands </italic>it implements. A DAS command is a request issued by a client for a certain class of data, such as a sequence or annotations of a sequence. The server responds with an XML document representing the requested data. DAS defines a model for constructing the query (a specific URL format), a model for representing the data (an XML document type) and its means of transport (HTTP). Each command has similar but distinct query and data models. Version 1.53 of the DAS specification [##UREF##1##9##] has five main commands:</p> <p>1. <bold>entry points </bold>– fetches a list of entities a source can annotate</p> <p>2. <bold>sequence </bold>– fetches the sequence of a segment of DNA, protein <italic>et cetera</italic></p> <p>3. <bold>features </bold>– the most commonly implemented command; fetches annotations located within a segment</p> <p>4. <bold>types </bold>– fetches a list of the types of feature a source or segment has</p> <p>5. <bold>stylesheet </bold>– fetches instructions for displaying features</p> <p>DAS sources that offer sequences are often referred to as <italic>reference sources </italic>because they provide the reference entry points for other commands on the same or different servers. Sources implementing the features command are by contrast referred to as <italic>annotation sources </italic>because they provide annotations based on a reference sequence. This distinction is largely historical since some DAS sources are conceptually both reference and annotation sources, and DAS has since expanded to cover non-sequence data.</p> <p>The DAS specification has also been extended with several other commands, such as those offering 3D structures and alignments. These are discussed in the Results section.</p> <title>DAS registry</title> <p>The steady growth in both the number and diversity of publicly available DAS sources necessitated the development of a method for the discovery of DAS services. Previously reported is the implementation of such a mechanism in the form of the DAS Registry [##REF##17850653##6##,##UREF##2##10##]. This service allows data providers to publish their DAS sources, allowing their automatic discovery by compatible clients. This discovery feature has been incorporated into most client implementations and libraries. The registry also performs service validation on registered sources to check that they are both functioning and conforming to the DAS specification. The number of registered sources has steadily increased since the DAS registry was created, to date totalling 383.</p>
<title>Results</title> <p>In recent years the DAS protocol has been expanded beyond the core specification to cater for the data integration needs of additional areas of biological research. However these extensions have yet to be incorporated into the specification itself, the latest version of which is 1.53. Instead, collectively they form an extended version of the DAS protocol, version <italic>1.53E</italic>. This protocol, documented at <ext-link ext-link-type="uri" xlink:href="http://www.dasregistry.org/spec_1.53E.jsp"/>, comprises five additional commands, an ontology for protein features, a server-side data preparation option (binning) and additional options for stylesheets. The extensions it offers are all optional for both servers and clients.</p> <title>New commands</title> <p>The DAS 1.53E specification defines five new commands.</p> <title>Structure</title> <p>Similar to the "sequence" command, this command allows DAS sources to act as reference sources for 3D structures. Clients may request the structure of a given entity, and the source responds with an XML representation of the atomic structure. PDB structures are currently served by a data source maintained by the Wellcome Trust Sanger Institute.</p> <title>Alignment</title> <p>This command provides a flexible mechanism for exposing pairwise and multiple alignments of entities. As well as full alignments, clients can request partial alignments containing entities within a given range of a query entity. This is particularly useful for clients wishing to display alignments containing large numbers of entities, such as the protein family alignments displayed on the Pfam website [##REF##18039703##11##].</p> <p>DAS alignments may additionally be used by clients as a means of converting between coordinate systems. For example, the Sanger Institute maintains an alignment DAS source that offers mappings between the UniProt and PDB databases. Using an alignment as an intermediary, it is possible for clients such as SPICE [##REF##16204122##12##] to project features from one coordinate system to the other.</p> <title>Interaction</title> <p>The interaction command is used for unifying and integrating different sources of molecular interaction data. A DAS source implementing this command supplies XML representations of molecular interactions.</p> <p>The DAS representation of an interaction is flexible enough to allow many types of interactions, including those for which the interacting region is known and those for which it is not. The XML document contains a list of interactions and a list of the interacting entities (termed "interactors"), with each interaction referencing two or more interactors. In addition to standard attributes such as name and database source, both interactions and interactors may be further described with additional custom properties.</p> <p>An interaction DAS source can be queried using one or more interactor identifiers, whereupon the DAS source returns interactions involving them all. The client can also request that interactions be filtered by their custom properties, specifying either interactions for which a given property is defined or those for which the property matches a given value.</p> <title>Volmap</title> <p>The volmap command is used for syndicating 3D structure volume map data from electron microscopy. It accepts a single "query" ID, and the simple XML response contains metadata for the volume map and a link to the raw data. Unlike other DAS commands, the data itself is not encapsulated in XML due to its large size. The 3DEM group at the Spanish National Center for Biotechnology offers DAS reference and annotation servers for volume map data, and have developed the PeppeR client to facilitate its display [##REF##17400476##13##].</p> <title>Sources</title> <p>The sources command is different from other DAS commands in that it is not implemented by individual DAS sources. Instead it is typically implemented by the servers on which DAS sources are hosted, and provides metadata describing their DAS sources. This allows clients and end users to discover the services a server offers. The command details for each source:</p> <p>1. The capabilities (commands) the source responds to.</p> <p>2. The coordinate systems the source offers data for.</p> <p>3. A contact email address.</p> <p>4. Custom properties that describe the source further (such as the project the source belongs to).</p> <p>Through the sources command, the DAS Registry can automatically 'mirror' individual servers, significantly augmenting the federation capabilities of the DAS protocol.</p> <title>Protein feature ontology</title> <p>The DAS protocol is intended to facilitate user-driven data integration such as graphical interfaces, and to enable data providers to quickly and easily expose their data. For these reasons, although the data transport mechanism has a defined structure, unlike other data integration technologies DAS does not impose strict semantic constraints on the data itself. Whilst this has resulted in widespread adoption, data shared via DAS are typically not amenable to automated analysis because the relationships between data types cannot be reliably inferred and it is difficult to assess their relative significance. To address this shortcoming, the DAS/1.53E specification defines an ontology for sharing protein feature annotations within a controlled vocabulary, developed jointly by the BioSapiens, UniProt and Gene Ontology projects. Currently, 34 BioSapiens DAS sources are committed to implementing the ontology in their annotations, though any source may choose to do so.</p> <p>The ontology is an optional extension to the <italic>features </italic>DAS command, and because it is implemented by convention rather than by modifying the XML schema it is fully backwards compatible. The ontology itself is actually a composite of three ontologies:</p> <p>1. Sequence Ontology [##REF##15892872##14##], an established ontology describing features of biological sequences.</p> <p>2. PSI-MOD, an ontology for post-translational modification terms.</p> <p>3. A new ontology for BioSapiens-specific terms not covered elsewhere, such as literature references and other non-positional annotations.</p> <title>Command extensions</title> <p>The DAS 1.53E specifications defines two new optional extensions to existing commands.</p> <title>Binning</title> <p>A core principle of DAS is the notion of servers being relatively simple, which lowers the requirements for data providers to expose their data. However, some DAS sources can potentially serve very large numbers of annotation features for a given segment of sequence. This creates problems for user-driven clients that rely on fast response times. Often, the client is not capable of rendering all these features because the user interface has insufficient resolution. For example, a DAS source might annotate every base in a megabase region of the genome, but the user of a graphical client will not be able to see every annotation.</p> <p>To solve the speed issue, the Ensembl DAS client takes advantage of this fact. It adds a <italic>maxbins </italic>parameter to a "features" command request. This parameter informs the DAS source of the client's maximum available rendering space by means of the number of 'bins' that features may be placed into. The DAS source may then choose to optimise its response by only returning features that are renderable by the client (<italic>i.e. </italic>maximum one per bin). It is up to the DAS source to decide which features it should filter. This process is illustrated in Table ##TAB##0##1##.</p> <title>Advanced stylesheets</title> <p>Some DAS sources opt to provide stylesheets – generic blueprints that allow a client, if it so wishes, to render features according to the intention of the DAS source provider. The core specification defines several <italic>glyphs </italic>that a feature can be rendered as such as boxes, lines and arrows. Stylesheets, as in other DAS commands, are provided in XML format and work by specifying the size, colour and type of glyph to be rendered for each type of annotation provided by the features command.</p> <p>Though stylesheets work well in representing sequence annotations such as exons, it is often desirable for some feature annotations to be rendered in more elegant formats. The 1.53E specification contains new glyph types for the "stylesheet" command that allow a server to define new ways of rendering data. The most notable of these are instructions for rendering plots according to a feature's <italic>score </italic>property. Different plot types include histograms, colour gradients, line plots and tiling arrays (wiggle plots). Figure ##FIG##0##1## shows some examples of these formats.</p>
<title>Discussion</title> <p>DAS is a widely adopted protocol for the integration of biological data types in user-driven contexts, commonly used by consortia of distributed institutions such as BioSapiens and ENCODE. Though originally designed for aggregating genomic data, over recent years it has been extended to cover additional data types such as protein structures and molecular interactions. Thus DAS continues to increase its penetration as a data integration platform. The increase in the number of available DAS data sources has necessitated the development of a syndication and discovery service, which was recently established in the form of a DAS Registry. In addition, a Protein Feature Ontology has been developed to fulfil a desire to constrain data to a controlled vocabulary so that it may be treated in a more intelligent manner. Together, these developments are ratified into a new <italic>extended </italic>DAS specification, version 1.53E. This consolidation serves to present a more coherent view of DAS as a flexible data integration platform. The principal strength of DAS lies in the ease with which data providers can expose their data, specifically for visual display. This simplicity makes it a good choice for smaller or experimentally-focussed groups with limited informatics resources wishing to allow their data to be visualised alongside other resources. Its decentralised structure also makes it ideal for clients when integrating frequently changing data. Similarly, since data offered via DAS always adheres to a defined format, changes in data structure are invisible to clients. This is in contrast to other data integration methods such as data warehousing and mediators that wrap individual data sources.</p> <p>However, other integration strategies do have their advantages. For example, other more complex middleware solutions may offer more advanced querying capabilities or more rigid semantics, which make them more suitable than DAS for data mining or as primary interfaces. Their disadvantages typically lie in the inevitably more involved setup process, textual display and reduced performance. Data warehouses have the capacity to provide high performance and powerful querying for analysis applications, but are often limited by the range of data sources they can integrate. This is due to the resources required to integrate each resource, with imports and structural changes typically being handled by the integrator rather than the data provider.</p> <p>The DAS protocol will continue to evolve in response to new requirements, enabled largely by the flexibility and simplicity of the original design. Future improvements may include the addition of server-side filtering for sources providing large amounts of data, a <italic>writeback </italic>function for sequence or annotation submission and "come back later" responses for exposing software as a DAS service. Additional commands for new data types such as small molecules are also likely.</p>
<title>Conclusion</title> <p>DAS is a data integration mechanism gaining greater popularity in the bioinformatics community, due largely to its simplicity of design. We have expanded the applicability and functionality of the DAS protocol with five new commands, two command extensions and a protein feature ontology. We have consolidated these disparate extensions into a new extended DAS specification, version 1.53E. As a result, DAS now represents a flexible and more coherent data integration platform that spans several areas, from genomic sequences to protein interactions.</p>
<p>This is an open access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/2.0"/>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</p> <title>Background</title> <p>The Distributed Annotation System (DAS) is a widely adopted protocol for dynamically integrating a wide range of biological data from geographically diverse sources. DAS continues to expand its applicability and evolve in response to new challenges facing integrative bioinformatics.</p> <title>Results</title> <p>Here we describe the various infrastructure components of DAS and present a new extended version of the DAS specification. Version 1.53E incorporates several recent developments, including its extension to serve new data types and an ontology for protein features.</p> <title>Conclusion</title> <p>Our extensions to the DAS protocol have facilitated the integration of new data types, and our improvements to the existing DAS infrastructure have addressed recent challenges. The steadily increasing numbers of available data sources demonstrates further adoption of the DAS protocol.</p>
<title>Implementation</title> <p>The DAS specification has several client implementations. The Ensembl genome browser [##REF##18000006##4##] incorporates a DAS client for several of its "views", and is able to display data from a wide variety of genomic, gene and protein sequence coordinate systems. It also integrates with SPICE [##REF##16204122##12##], a Java Web-Start application that uses DAS alignments to combine protein sequence and structural annotations. Using SPICE, protein sequence annotations can be projected onto and visualised within a 3D structure. The DASMIweb portal [##UREF##3##15##] integrates protein-protein and domain-domain interaction datasets. The iPfam website also integrates interaction data, comparing the interaction topologies of different sources by overlaying them in a node graph [##UREF##4##16##]. Other clients include Dasty [##REF##15905273##17##], a web-based standalone DAS client implemented in Javascript, and the Pfam [##REF##18039703##11##] website.</p> <p>Several solid client implementations are based on open source libraries, which are available for the Perl and Java programming languages. These include <italic>Bio::Das::Lite </italic>[##UREF##5##18##] and the <italic>Dasobert </italic>component of BioJava [##UREF##6##19##]. DAS server implementations are also provided for both languages: ProServer [##REF##17237073##20##] and LDAS [##UREF##7##21##] for Perl; Dazzle [##UREF##8##22##] and MyDas [##UREF##9##23##] for Java.</p> <title>Availability and requirements</title> <p>• Project home page: <ext-link ext-link-type="uri" xlink:href="http://www.dasregistry.org"/></p> <p>• Operating system(s): Platform independent</p> <p>• Programming language: Java, Perl</p> <p>• Other requirements: Internet Browser</p> <p>• License: GPL and other open source</p> <p>• Any restrictions to use by non-academics: none</p> <title>Competing interests</title> <p>The authors declare that they have no competing interests.</p> <title>Authors' contributions</title> <p>AMJ extended and maintains the ProServer library, contributed to the Bio::Das::Lite library, contributed to the Ensembl client, implemented and maintains a variety of DAS servers and wrote the manuscript. MA, HB, RDF, JRM and AP designed the various extensions. MA and HB implemented DASMIweb. TD was involved in the design of the project and is the original author of the Dazzle library. EB and TH contributed guidance throughout the project. RDF is responsible for the Pfam resources and extended the ProServer and Bio::Das::Lite libraries. HH and PJ implemented proteomics DAS resources and the MyDas server library. RCJ implemented Dasty. AK implemented various DAS servers. EK implemented the Ensembl client and server. JRM implemented PeppeR. GAR implemented the ontology. AP co-ordinated the 1.53E specification, implemented SPICE and the DAS registration server and extended and maintains the Dazzle and Dasobert libraries.</p>
<title>Acknowledgements</title> <p>We would like to acknowledge the contribution of all those who provide data to the community via DAS, without which the system would not function. Parts of this work were conducted in the context of the BioSapiens Network of Excellence funded by the European Commission under grant number LSHG-CT-2003-503265.</p> <p>This article has been published as part of <italic>BMC Bioinformatics </italic>Volume 9 Supplement 8, 2008: Selected proceedings of the Fifth International Workshop on Data Integration in the Life Sciences 2008. The full contents of the supplement are available online at <ext-link ext-link-type="uri" xlink:href="http://www.biomedcentral.com/1471-2105/9?issue=S8"/>.</p>
<fig position="float" id="F1"><label>Figure 1</label><caption><p><bold>Advanced stylesheets</bold>. Examples of advanced rendering techniques possible with DAS: colour gradients and tiling arrays, as displayed in Ensembl.</p></caption></fig>
<table-wrap position="float" id="T1"><label>Table 1</label><caption><p>Binning: illustration of how a DAS source may implement binning.</p></caption><table frame="hsides" rules="groups"><thead><tr><td align="left">Positions</td><td align="center">11</td><td align="center">12</td><td align="center">13</td><td align="center">14</td><td align="center">15</td><td/><td align="center">16</td><td align="center">17</td><td align="center">18</td><td align="center">19</td><td align="center">20</td><td/><td align="center">21</td><td align="center">22</td><td align="center">23</td><td align="center">24</td><td align="center">25</td></tr></thead><tbody><tr><td align="left">Available bins</td><td align="center" colspan="5">Bin 1</td><td/><td align="center" colspan="5">Bin 2</td><td/><td align="center" colspan="5">Bin 3</td></tr><tr><td/><td colspan="5"><hr/></td><td/><td colspan="5"><hr/></td><td/><td colspan="5"><hr/></td></tr><tr><td align="left">Annotation score</td><td align="center">8</td><td align="center">3</td><td align="center">9</td><td align="center">1</td><td align="center">4</td><td/><td align="center">7</td><td align="center">6</td><td align="center">7</td><td align="center">2</td><td align="center">0</td><td/><td align="center">2</td><td align="center">4</td><td align="center">4</td><td align="center">3</td><td align="center">5</td></tr><tr><td align="left">Features returned</td><td/><td/><td align="center">9</td><td/><td/><td/><td align="center">7</td><td/><td/><td/><td/><td/><td/><td/><td/><td/><td align="center">5</td></tr></tbody></table></table-wrap>
<table-wrap-foot><p>In this contrived example a client requests feature annotations for a segment of sequence between bases 11 and 25, with a <italic>maxbins </italic>parameter of 3. The DAS source has an annotation for every base but, after sorting each into its appropriate bin, returns only those features with the highest scores.</p></table-wrap-foot>
<graphic xlink:href="1471-2105-9-S8-S3-1"/>
[{"surname": ["Finn", "Prlic", "Das", "McNeil", "Mulder", "Velankar", "Andreeva", "Howorth", "Dibley", "Hubbard", "Apweiler", "Henrick", "Murzin", "Orengo", "Bateman", "Cox SJ"], "given-names": ["RD", "A", "U", "P", "N", "S", "A", "D", "M", "T", "R", "K", "A", "C", "A"], "article-title": ["eFamily: Bridging Sequence and Structure"], "source": ["Proceedings of UK e-Science All Hands Meeting 2004 (AHM04): 31st August \u2013 3rd September 2004; Nottingham, UK"], "year": ["2004"], "publisher-name": ["EPSRC"], "fpage": ["1069"], "lpage": ["1072"]}, {"article-title": ["The DAS 1.53 specification"]}, {"surname": ["Prlic", "Birney", "Cox", "Down", "Finn", "Gr\u00e4af", "Jackson", "K\u00e4h\u00e4ri", "Kulesha", "Pettett", "Smith", "Stalker", "Hubbard", "Leser U, Naumann F, Eckman B"], "given-names": ["A", "E", "T", "TA", "R", "S", "D", "A", "E", "R", "J", "J", "TJP"], "article-title": ["The Distributed Annotation System for Integration of Biological Data"], "source": ["Data Integration in the Life Sciences Third International Workshop, DILS 2006: 20\u201322 July 2006; Hinxton"], "year": ["2006"], "publisher-name": ["Springer"], "fpage": ["195"], "lpage": ["203"]}, {"article-title": ["The DASMIweb portal"]}, {"article-title": ["iPfam interaction graph"]}, {"article-title": ["Bio::Das::Lite DAS client library"]}, {"article-title": ["Dasobert DAS client library"]}, {"article-title": ["LDAS DAS server"]}, {"article-title": ["Dazzle DAS server"]}, {"article-title": ["MyDas DAS server"]}]
BMC Bioinformatics. 2008 Jul 22; 9(Suppl 8):S3