<?xml version='1.0'?>
<!DOCTYPE art SYSTEM 'http://www.biomedcentral.com/xml/article.dtd'>
<art>
	<ui>gb-2006-7-5-402</ui>
	<ji>GBJ</ji>
	<fm>
		<dochead>Correspondence</dochead>
		<bibl>
			<title>
				<p>The success (or not) of HUGO nomenclature</p>
			</title>
			<aug>
				<au id="A1" ca="yes">
					<snm>Tamames</snm>
					<fnm>Javier</fnm>
					<insr iid="I1"/>
					<insr iid="I2"/>
					<email>tamames@cnb.uam.es</email>
				</au>
				<au id="A2">
					<snm>Valencia</snm>
					<fnm>Alfonso</fnm>
					<insr iid="I2"/>
				</au>
			</aug>
			<insg>
				<ins id="I1">
					<p>Instituto Cavanilles de Biodiversidad y Biologia Evolutiva, Universidad de Valencia, Apartado Postal 22085, 46071 Valencia, Spain</p>
				</ins>
				<ins id="I2">
					<p>Centro Nacional de Biotecnolog&#237;a - CSIC, Avenida Darwin 3, 28049 Cantoblanco, Madrid, Spain</p>
				</ins>
			</insg>
			<source>Genome Biology</source>
			<issn>1465-6906</issn>
			<pubdate>2006</pubdate>
			<volume>7</volume>
			<issue>5</issue>
			<fpage>402</fpage>
			<url>http://genomebiology.com/2006/7/5/402</url>
			<xrefbib>
				<pubidlist><pubid idtype="pmpid">16707004</pubid><pubid idtype="doi">10.1186/gb-2006-7-5-402</pubid>
				</pubidlist></xrefbib>
		</bibl>
		<history>
			<pub>
				<date>
					<day>15</day>
					<month>5</month>
					<year>2006</year>
				</date>
			</pub>
		</history>
		<cpyrt>
			<year>2006</year>
			<collab>BioMed Central Ltd</collab>
		</cpyrt>
		<shorttitle>
			<p>The success (or not) of HUGO nomenclature</p>
		</shorttitle>
		<shortabs>
			<p>A literature search shows that biologists do not follow the official nomenclature guidelines for a substantial fraction of gene names.
</p>
		</shortabs>
		<abs>
			<sec>
				<st>
					<p>Abstract</p>
				</st>
				<p>Current usage of gene nomenclature is ambiguous and impairs the efficient handling of scientific information. Therefore it is important to propose guidelines to deal with this problem. This study attempts to evaluate the success of HUGO nomenclature for human genes. The results indicate that HUGO guidelines are not supported by the scientific community.</p>
			</sec>
		</abs>
	</fm>
	<meta>
		<classifications>
			<classification type="BMC" subtype="man_spc_id" id="30010002">Bioinformatics</classification>
			<classification type="BMC" subtype="man_spc_id" id="30010009">Genetics</classification>
		</classifications>
	</meta>
	<bdy>
		<sec>
			<st>
				<p/>
			</st>
			<p>Ambiguous gene names impose a serious hurdle for the analysis of a wide range of high-throughput data, such as microarray experiments or protein-interaction maps. This sort of ambiguity also limits the efficiency of genome analysis and annotation and slows the implementation of automatic text-mining systems for using bibliographic information <abbrgrp><abbr bid="B1">1</abbr><abbr bid="B2">2</abbr></abbrgrp>. While systems for automatic gene name recognition in other domains (such as in business or news reports) perform very well, the best systems in the biological field perform just slightly better than 80% <abbrgrp><abbr bid="B3">3</abbr></abbrgrp>.</p>
			<p>Genes are commonly named using functional terms, such as 'insulin' or 'tumor necrosis factor', or symbols consisting of abbreviations such as <it>INS </it>for insulin or <it>TNF </it>for tumor necrosis factor. Functional names are usually unique, in the sense that a given name refers only to one gene family, even if not always to a single gene of the family. Ambiguity exists because often more than one functional name is used to refer to the same gene (synonymy), and also many functional names are descriptive of some phenotype of the gene (such as '<it>deafness</it>' or '<it>wingless</it>'), a practice that creates many complications <abbrgrp><abbr bid="B4">4</abbr></abbrgrp>. The use of symbols should alleviate some of the problems created by the use of functional names, but in practice seems to produce even more ambiguities. In addition to extended synonymy (with many symbols describing the same gene), a given symbol can also be used to describe different genes (homonymy). Moreover, many other meanings can match the abbreviation used for the gene name (acronyms). Text-mining systems are severely limited by these factors, as ambiguities decrease the precision in the retrieval of correct articles, and synonyms limit the number of total retrieved articles.</p>
			<p>These limitations potentially impair the effective application of text mining and natural language processing (NLP) techniques in genomics. For instance, the comparison of microarray data from different sources requires the exact mapping of the names used by different authors. This task can be greatly complicated by ambiguous names such as '<it>PAP</it>', which can refer to five different human genes, and will therefore be impossible to classify in the absence of additional information. In this type of situation, valuable experimental information could be lost because of nomenclature problems that could be solved by the use of standard names.</p>
			<p>Standard nomenclatures, strictly following naming guidelines, are the most obvious solution to the problem. Indeed, considerable community effort has gone into the creation of these standards for gene symbols in organisms such as yeast, mouse, fly, and, of course, human. An illustrative example is the valuable effort of HUGO nomenclature for human genes <abbrgrp><abbr bid="B5">5</abbr><abbr bid="B6">6</abbr></abbrgrp>. A single official symbol is proposed for every gene, and the aliases (alternative symbols, synonyms) for each gene are also listed. The obvious concern is the extent to which scientists follow these nomenclature rules. Other instances of standard nomenclatures, such as enzymatic codes (EC numbers), have been loosely followed.</p>
			<p>We carried out a study to assess the relative success of HUGO guidelines by measuring the progress in the usage of official gene symbols in recent years. We analyzed PubMed abstracts for the period 1994-2004, collecting information regarding the mention of human gene symbols and the frequency with which official symbols were mentioned in comparison with their aliases. It is painfully obvious that the community has not widely adopted the HUGO guidelines. It is equally obvious that there is no clear tendency that this situating is improving, as the proportion of official symbols that are used predominantly has only increased slightly, from 35% in 1994 to 44% in 2004 (Figure <figr fid="F1">1</figr>). Accordingly, a small decrease in the cases where the official name was not mentioned at all is observed (from 23% in 1994 to 14% in 2004). Despite this minor progress, it is still true that aliases are used more often than official symbols, and as many as 14% of genes are never mentioned using the recommended official symbols.</p>
			<fig id="F1">
				<title>
					<p>Figure 1</p>
				</title>
				<caption>
					<p>Usage of HUGO nomenclature in the past ten years</p>
				</caption>
				<text>
					<p>Usage of HUGO nomenclature in the past ten years. We analyzed PubMed abstracts for the period 1994-2004, collecting information about the human genes mentioned on the abstracts, and noting how such mention was made (official symbol or other aliases). Names were detected using Text Detective (BioAlma SL), a gene name recognition software that is able to recognize human gene names in texts with high recall and precision, distinguishing real instances of the gene from other uses and meanings of the same name [13]. Text Detective combines gene name recognition with standardization of citations, using HUGO nomenclature in the case of human genes. Additional results (the yeast results discussed in the text) were obtained using the Information Interlinked Over Proteins (iHOP) system [14] in order to discard possible biases due to the name-recognition software used. The percentage of genes that are cited predominantly by their official name is used as a measure of the support for official names. Blue bars show the percentage of genes for which the official name is favored (the official name is mentioned more often than aliases). Yellow bars show the inverse, the percentage of genes for which aliases are favored. Green bars show the percentage of cases in which the official name is never used, and all mentions correspond to aliases. Also, the average number of names per gene is shown, computed as the total number of names used divided by the total number of genes. The last column, labeled 'Novel', takes into account only those genes whose first mention in the literature occurred in the year 2000 or later.</p>
				</text>
				<graphic file="gb-2006-7-5-402-1"/>
			</fig>
			<p>A positive observation is that this small increment is in part due to new genes that are named preferentially according to the official standards. The genes mentioned for the first time after the year 2000 have a higher proportion of official symbols and a smaller number of synonyms (Figure <figr fid="F1">1</figr>); however, it can still be argued that it is only a question of time for these genes to acquire new synonyms. Furthermore, highly referenced genes are cited notably more often by unofficial gene names. For example, in 2004, only 38% of genes cited in more than 50 articles were named predominantly by following HUGO, whereas scarcely cited genes more often followed the standards (54% in 2004).</p>
			<p>The tendency to improve the situation by replacing aliases in favor of HUGO official symbols is, unfortunately, weak. The changes in name usage, either from official to aliases or from aliases to official, are not very frequent, and the nomenclature of most genes remains rather stable with time. These findings seem to confirm the intuition that researchers remain attached to their favorite names.</p>
			<p>This trend is not species-dependent. For example, in yeast, where there is also a proposed standard nomenclature <abbrgrp><abbr bid="B7">7</abbr></abbrgrp>, there is not a tendency to replace aliases with official names (the usage of official names has remained approximately the same in recent years as in the past), even if in this community official names are used more often (85% of the genes are preferentially cited using official names).</p>
			<p>Many of the occasional transitions are in fact produced after the publication of a prominent paper describing an important discovery regarding a gene, which usually produces a chain of subsequent studies that tend to use the new name. For instance, in the mid-1990s the gene for intestinal trefoil factor 3 was cited predominantly under the alias <it>ITF</it>. But since 1998, the official name <it>TFF3 </it>has been preferred, apparently influenced by a paper describing the regulation that the gene exerts on the expression of <it>catenin </it>and <it>cadherin</it>, with important consequences for epithelial cell adhesion, migration, and survival <abbrgrp><abbr bid="B8">8</abbr></abbrgrp>, which gave rise to the use of the symbol <it>TFF3 </it>for that gene. Therefore, it would appear that important scientific papers influence nomenclature usage even more than does the adoption of standards (Figure <figr fid="F2">2a</figr>).</p>
			<fig id="F2">
				<title>
					<p>Figure 2</p>
				</title>
				<caption>
					<p>Plot of the evolution of the usage of different names</p>
				</caption>
				<text>
					<p>Plot of the evolution of the usage of different names. The plots show, for each year, the percentage usage of each of the names. <b>(a)</b> Intestinal trefoil factor 3 (official name, <it>TFF3</it>); <b>(b)</b> poliovirus receptor (official name, <it>PVR</it>); <b>(c)</b> lymphotactin (official name, <it>XCL1</it>).</p>
				</text>
				<graphic file="gb-2006-7-5-402-2"/>
			</fig>
			<p>A similar case is illustrated in Figure <figr fid="F2">2b</figr> for the gene encoding the poliovirus receptor. In the mid-1990s, the only symbol used was <it>PVR </it>(which is today the official name for the gene). The alternative name CD155 for the protein appeared for the first time in 1997, but gained greater acceptance after the publication in the late nineties of several articles describing structural aspects of the CD155 protein <abbrgrp><abbr bid="B9">9</abbr></abbrgrp> that are critical to the interaction with the virus (CD nomenclature for cell-surface proteins follows a long established standard nomenclature). These articles named the gene as <it>CD155</it>, and this has been the preferred name since then. In this case, HUGO nomenclature apparently did not take this fact into account, since the establishment of <it>PVR </it>as the official gene name took place in 2003.</p>
			<p>Finally, Figure <figr fid="F2">2c</figr> shows an interesting case of the persistence of several different names for one gene, that for the chemokine lymphotactin. The cloning of this gene was reported almost simultaneously by three independent groups in Japan, Germany and the USA in 1995 <abbrgrp><abbr bid="B10">10</abbr><abbr bid="B11">11</abbr><abbr bid="B12">12</abbr></abbrgrp>. The three groups named the gene differently (<it>SCM1</it>, <it>ATAC </it>and <it>LTN</it>, respectively). These names have all been used since then, as well as <it>LPTN </it>and, lately, the official name <it>XCL1</it>. It is interesting to notice that the three groups reporting the discovery kept using their own names for the gene, at least until very recently, a trend that can be observed also in the previous examples.</p>
			<p>The problem of linking names in texts with the molecules they refer to can only be solved by a concerted community effort to explicitly mention the official names and/or the corresponding database accession numbers (such as these of UniProt or Refseq for proteins, and GenBank for genes). The use of accession numbers has the advantage of providing a unique and unambiguous reference that is also a direct link to the real biological object. But it does have some drawbacks. Citing accession numbers instead of gene or protein names would seriously affect the clarity and readability of the text. From this point of view, names and accession numbers must coexist. This could be done, for instance, by citing only names in the main text, and including accession numbers for the protein or gene names used in the text in a separate section. Also, our experience is that mapping between different databases is not exempt from problems. For instance, a single nucleotide sequence often has several different entries, corresponding to splice variants, polymorphisms or regions of the genome. Also, for these references to be really useful, they would have to cover all the mentions of genes including anaphoric (the use of a linguistic unit, such as the pronoun 'it' to refer to a previous mention of the name) and other forms of implicit mentions, and to take into account the difference between individual genes and proteins and general protein names referring to, for instance, protein familes (that is, 'tubulin beta1 protein' can be assigned to a well defined molecule, but 'tubulin' cannot, since it can refer to several different molecules). It would be important to develop adequate tools to facilitate the introduction of names and identifiers at the time of writing papers, and to enable the posterior recovery by both humans and software tools.</p>
			<p>The task of tagging genes and proteins in papers with the corresponding official names and/or database entries will require the collaboration of authors, journals and grant agencies, and could be facilitated by the development of adequate text-mining methods.</p>
		</sec>
	</bdy>
	<bm>
		<ack>
			<sec>
				<st>
					<p>Acknowledgements</p>
				</st>
				<p>J.T. developed the gene name recognition system Text Detective as part of his work at BioAlma SL (Tres Cantos, Madrid, Spain). This work was partly supported by research grants ENFIN LSGH-CT-2005-518254 (VI Framework Programme, European Comission), ESPA&#209;OL BIO2004-00875 (Spanish Ministry of Education and Science), and Fundaci&#243;n BBVA.</p>
			</sec>
		</ack>
		<refgrp>
			<bibl id="B1">
				<title>
					<p>What's in a name?</p>
				</title>
				<aug>
					<au>
						<snm>Petsko</snm>
						<fnm>GA</fnm>
					</au>
				</aug>
				<source>Genome Biol</source>
				<pubdate>2002</pubdate>
				<volume>3</volume>
				<fpage>comment1005.1</fpage>
				<lpage>1005.2</lpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="pmpid" link="fulltext">11983048</pubid>
						<pubid idtype="doi">10.1186/gb-2002-3-4-comment1005</pubid>
						<pubid idtype="pmcid">139339</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
			<bibl id="B2">
				<title>
					<p>Tough mining: the challenges of searching the scientific literature.</p>
				</title>
				<aug>
					<au>
						<snm>Dickman</snm>
						<fnm>S</fnm>
					</au>
				</aug>
				<source>PLoS Biol</source>
				<pubdate>2003</pubdate>
				<volume>1</volume>
				<fpage>e48</fpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="pmcid">261887</pubid>
						<pubid idtype="pmpid" link="fulltext">14624250</pubid>
						<pubid idtype="doi">10.1371/journal.pbio.0000048</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
			<bibl id="B3">
				<title>
					<p>BioCreAtIvE task 1A: gene mention finding evaluation.</p>
				</title>
				<aug>
					<au>
						<snm>Yeh</snm>
						<fnm>A</fnm>
					</au>
					<au>
						<snm>Morgan</snm>
						<fnm>A</fnm>
					</au>
					<au>
						<snm>Colosimo</snm>
						<fnm>M</fnm>
					</au>
					<au>
						<snm>Hirschman</snm>
						<fnm>L</fnm>
					</au>
				</aug>
				<source>BMC Bioinformatics</source>
				<pubdate>2005</pubdate>
				<volume>6</volume>
				<issue>Suppl 1</issue>
				<fpage>S2</fpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="doi">10.1186/1471-2105-6-S1-S2</pubid>
						<pubid idtype="pmpid" link="fulltext">15960832</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
			<bibl id="B4">
				<title>
					<p>Gene name ambiguity of eukaryotic nomenclatures.</p>
				</title>
				<aug>
					<au>
						<snm>Chen</snm>
						<fnm>L</fnm>
					</au>
					<au>
						<snm>Liu</snm>
						<fnm>H</fnm>
					</au>
					<au>
						<snm>Friedman</snm>
						<fnm>C</fnm>
					</au>
				</aug>
				<source>Bioinformatics</source>
				<pubdate>2005</pubdate>
				<volume>21</volume>
				<fpage>248</fpage>
				<lpage>256</lpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="doi">10.1093/bioinformatics/bth496</pubid>
						<pubid idtype="pmpid" link="fulltext">15333458</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
			<bibl id="B5">
				<title>
					<p>Genew: the human nomenclature database.</p>
				</title>
				<aug>
					<au>
						<snm>Wain</snm>
						<fnm>HM</fnm>
					</au>
					<au>
						<snm>Lush</snm>
						<fnm>M</fnm>
					</au>
					<au>
						<snm>Ducluzeau</snm>
						<fnm>F</fnm>
					</au>
					<au>
						<snm>Povey</snm>
						<fnm>S</fnm>
					</au>
				</aug>
				<source>Nucleic Acids Res</source>
				<pubdate>2002</pubdate>
				<volume>30</volume>
				<fpage>169</fpage>
				<lpage>171</lpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="pmcid">99058</pubid>
						<pubid idtype="pmpid" link="fulltext">11752283</pubid>
						<pubid idtype="doi">10.1093/nar/30.1.169</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
			<bibl id="B6">
				<title>
					<p>HUGO Gene Nomenclature Committee</p>
				</title>
				<url>http://www.gene.ucl.ac.uk/nomenclature</url>
			</bibl>
			<bibl id="B7">
				<title>
					<p><it>Saccharomyces </it>Genome Database (SGD)</p>
				</title>
				<url>http://www.yeastgenome.org</url>
			</bibl>
			<bibl id="B8">
				<title>
					<p>Intestinal trefoil factor controls the expression of the adenomatous polyposis coli-catenin and the E-cadherin-catenin complexes in human colon carcinoma cells.</p>
				</title>
				<aug>
					<au>
						<snm>Efstathiou</snm>
						<fnm>JA</fnm>
					</au>
					<au>
						<snm>Noda</snm>
						<fnm>M</fnm>
					</au>
					<au>
						<snm>Rowan</snm>
						<fnm>A</fnm>
					</au>
					<au>
						<snm>Dixon</snm>
						<fnm>C</fnm>
					</au>
					<au>
						<snm>Chinery</snm>
						<fnm>R</fnm>
					</au>
					<au>
						<snm>Jawhari</snm>
						<fnm>A</fnm>
					</au>
					<au>
						<snm>Hattori</snm>
						<fnm>T</fnm>
					</au>
					<au>
						<snm>Wright</snm>
						<fnm>NA</fnm>
					</au>
					<au>
						<snm>Bodmer</snm>
						<fnm>WF</fnm>
					</au>
					<au>
						<snm>Pignatelli</snm>
						<fnm>M</fnm>
					</au>
				</aug>
				<source>Proc Natl Acad Sci USA</source>
				<pubdate>1998</pubdate>
				<volume>95</volume>
				<fpage>3122</fpage>
				<lpage>3127</lpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="pmcid">19705</pubid>
						<pubid idtype="pmpid" link="fulltext">9501226</pubid>
						<pubid idtype="doi">10.1073/pnas.95.6.3122</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
			<bibl id="B9">
				<title>
					<p>Dual stem loops within the poliovirus internal ribosomal entry site control neurovirulence.</p>
				</title>
				<aug>
					<au>
						<snm>Gromeier</snm>
						<fnm>M</fnm>
					</au>
					<au>
						<snm>Bossert</snm>
						<fnm>B</fnm>
					</au>
					<au>
						<snm>Arita</snm>
						<fnm>M</fnm>
					</au>
					<au>
						<snm>Nomoto</snm>
						<fnm>A</fnm>
					</au>
					<au>
						<snm>Wimmer</snm>
						<fnm>E</fnm>
					</au>
				</aug>
				<source>J Virol</source>
				<pubdate>1999</pubdate>
				<volume>73</volume>
				<fpage>958</fpage>
				<lpage>964</lpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="pmcid">103915</pubid>
						<pubid idtype="pmpid" link="fulltext">9882296</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
			<bibl id="B10">
				<title>
					<p>Molecular cloning of a novel C or gamma type chemokine, SCM-1.</p>
				</title>
				<aug>
					<au>
						<snm>Yoshida</snm>
						<fnm>T</fnm>
					</au>
					<au>
						<snm>Imai</snm>
						<fnm>T</fnm>
					</au>
					<au>
						<snm>Kakizaki</snm>
						<fnm>M</fnm>
					</au>
					<au>
						<snm>Nishimura</snm>
						<fnm>M</fnm>
					</au>
					<au>
						<snm>Yoshie</snm>
						<fnm>O</fnm>
					</au>
				</aug>
				<source>FEBS Lett</source>
				<pubdate>1995</pubdate>
				<volume>360</volume>
				<fpage>155</fpage>
				<lpage>159</lpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="doi">10.1016/0014-5793(95)00093-O</pubid>
						<pubid idtype="pmpid" link="fulltext">7875320</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
			<bibl id="B11">
				<title>
					<p>Cloning of ATAC, an activation-induced, chemokine-related molecule exclusively expressed in CD8+ T lymphocytes.</p>
				</title>
				<aug>
					<au>
						<snm>Muller</snm>
						<fnm>S</fnm>
					</au>
					<au>
						<snm>Dorner</snm>
						<fnm>B</fnm>
					</au>
					<au>
						<snm>Korthauer</snm>
						<fnm>U</fnm>
					</au>
					<au>
						<snm>Mages</snm>
						<fnm>HW</fnm>
					</au>
					<au>
						<snm>D'Apuzzo</snm>
						<fnm>M</fnm>
					</au>
					<au>
						<snm>Senger</snm>
						<fnm>G</fnm>
					</au>
					<au>
						<snm>Kroczek</snm>
						<fnm>RA</fnm>
					</au>
				</aug>
				<source>Eur J Immunol</source>
				<pubdate>1995</pubdate>
				<volume>25</volume>
				<fpage>1744</fpage>
				<lpage>1748</lpage>
				<xrefbib>
					<pubid idtype="pmpid">7615002</pubid>
				</xrefbib>
			</bibl>
			<bibl id="B12">
				<title>
					<p>Molecular cloning and functional characterization of human lymphotactin.</p>
				</title>
				<aug>
					<au>
						<snm>Kennedy</snm>
						<fnm>J</fnm>
					</au>
					<au>
						<snm>Kelner</snm>
						<fnm>GS</fnm>
					</au>
					<au>
						<snm>Kleyensteuber</snm>
						<fnm>S</fnm>
					</au>
					<au>
						<snm>Schall</snm>
						<fnm>TJ</fnm>
					</au>
					<au>
						<snm>Weiss</snm>
						<fnm>MC</fnm>
					</au>
					<au>
						<snm>Yssel</snm>
						<fnm>H</fnm>
					</au>
					<au>
						<snm>Schneider</snm>
						<fnm>PV</fnm>
					</au>
					<au>
						<snm>Cocks</snm>
						<fnm>BG</fnm>
					</au>
					<au>
						<snm>Bacon</snm>
						<fnm>KB</fnm>
					</au>
					<au>
						<snm>Zlotnik</snm>
						<fnm>A</fnm>
					</au>
				</aug>
				<source>J Immunol</source>
				<pubdate>1995</pubdate>
				<volume>155</volume>
				<fpage>203</fpage>
				<lpage>209</lpage>
				<xrefbib>
					<pubid idtype="pmpid" link="fulltext">7602097</pubid>
				</xrefbib>
			</bibl>
			<bibl id="B13">
				<title>
					<p>Text Detective: a rule-based system for gene annotation in biomedical texts.</p>
				</title>
				<aug>
					<au>
						<snm>Tamames</snm>
						<fnm>J</fnm>
					</au>
				</aug>
				<source>BMC Bioinformatics</source>
				<pubdate>2005</pubdate>
				<volume>6</volume>
				<issue>Suppl 1</issue>
				<fpage>S10</fpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="doi">10.1186/1471-2105-6-S1-S10</pubid>
						<pubid idtype="pmpid" link="fulltext">15960822</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
			<bibl id="B14">
				<title>
					<p>A gene network for navigating the literature.</p>
				</title>
				<aug>
					<au>
						<snm>Hoffmann</snm>
						<fnm>R</fnm>
					</au>
					<au>
						<snm>Valencia</snm>
						<fnm>A</fnm>
					</au>
				</aug>
				<source>Nat Genet</source>
				<pubdate>2004</pubdate>
				<volume>36</volume>
				<fpage>664</fpage>
				<xrefbib>
					<pubidlist>
						<pubid idtype="doi">10.1038/ng0704-664</pubid>
						<pubid idtype="pmpid" link="fulltext">15226743</pubid>
					</pubidlist>
				</xrefbib>
			</bibl>
		</refgrp>
	</bm>
</art>
