<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Evaluating and Analyzing Inconsistent RDF Data in a Semantic Dataset: EMAGE Dataset</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Nwagwu Honour Chika</string-name>
          <email>Honour.C.Nwagwu@student.shu.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Cultural Communication and Computing Research Institute (C3RI) Faculty of Arts, Computing, Engineering and Sciences Sheffield Hallam University</institution>
          ,
          <country country="UK">United Kingdom</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper explains how to evaluate and analyse inconsistent Resource Description Framework (RDF) data by using EMAGE semantic (RDF) dataset as its use case. The author exploits the sub graph matching powers and mathematical functions of SPARQL query in evaluating inconsistent RDF data in a semantic dataset. He also proposes a mathematical method for calculating the amount of inconsistency in RDF data through a graph search approach. Finally, He analyzed the evaluated inconsistent RDF data.</p>
      </abstract>
      <kwd-group>
        <kwd>Triples</kwd>
        <kwd>RDF data</kwd>
        <kwd>Inconsistent data</kwd>
        <kwd>Ontology</kwd>
        <kwd>SPARQL queries</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        EMAGE is a database of in situ gene expression data in the mouse embryo and an
accompanying suite of tools to search and analyze the data
(http://www.emouseatlas.org/emage/). EMAGE publishes in situ gene expression data
for the developmental mouse. Its data is collected through a scrutinized process which
involves assessing and tabulating of Biologist‟s experimental reports. These data
include reports on gene expressions in mouse experiments which are reported elsewhere
[
        <xref ref-type="bibr" rid="ref11">11</xref>
        ], the gene expression database (GXD), and laboratory reports among others. The
Biologist‟s experimental report determines the strength of the expressed gene in a
tissue of a mouse at a particular Theiler Stage. The Theiler stages correspond to a 28
days period associated with the developing mouse denoted by TS01 to TS28. More
information about EMAGE datasets and mouse experiments can be found at the
Edinburgh Mouse Atlas Project (EMAP) website [
        <xref ref-type="bibr" rid="ref10 ref12">10, 12</xref>
        ].
      </p>
      <p>
        EMAGE‟s dataset can serve as a platform for Biologists to find solutions to the
causes of abnormalities in organisms. Biologists can suggest answers to the cause of
abnormalities in organisms through comparing the data indicating the strength of
expressed gene in a healthy organism with that of unhealthy organism [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
Nevertheless, data from some of the experiments which provide Biologists with this needed
information can sometimes be inconsistent and these inconsistencies could be as a
result of experimental error or simply a slight variation in experimental conditions [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
Also, the accuracy of a dataset with inconsistent information can be increased through
deleting the inconsistent data but at the cost of an increase in the incompleteness of
the dataset. This cost can be avoided or minimized by properly evaluating and
analyzing the degree of the inconsistency in the dataset. The author has explained how the
inconsistency of RDF data can be identified, evaluated and analyzed. He has achieved
this by explaining what RDF data model is in section 2.0, Identifying inconsistent
RDF data in EMAGE dataset in section 3.0, Evaluating and analyzing inconsistent
RDF data in section 4.0 and finally, the author presents his approach on how
inconsistent RDF data can be evaluated and analyzed in section 5.0.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>RDF data model</title>
      <p>Information in semantic dataset is represented by RDF data in the form of triples and
stored in a triple store. A triple consists of subject, predicate and an object. An
illustration of a RDF triple is as shown in figure 1 below.
&lt;http://www.cubist_project.eu/HWU#tissue_EMAP_42&gt;
&lt;http://www.w3.org/2001/01/rdf-schema#label&gt; “embryo” .</p>
      <p>Each triple in RDF dataset represents a statement of a relationship between the
entities denoted by the nodes that it links. RDF data can contain one or more triples.
Each triple is composed of a subject, predict and an object. In RDF data, each subject
of a triple is represented by a Universal Resource Identifier (URI) or blank node, each
predicate is represented by a URI and each object node is represented by a URI, a
blank node or a literal. For example in figure 1, the subject of the triple is a URI
“http://www.cubist_project.eu/hwu#tissue_EMAP_42”, the predicate is a URI
“http://www.w3.org/2000/rdf-schema#label”, and the object node is a literal
“embryo”. The author adopted turtle serialization format (http://www.w3.org/TR/turtle/) in
this example. RDF data has other serialization formats for representing its data such
as N-Triple, N3, RDF/XML and RDFa.</p>
    </sec>
    <sec id="sec-3">
      <title>3 Identifying inconsistent RDF data in EMAGE dataset: SPARQL Query</title>
      <p>Language
Inconsistency exists in RDF data when the data does not conform to the rules
governing their design. This is evident when there is a contradiction in the RDF data such
that the RDF data contains both A and ⌐A.</p>
      <p>
        Inconsistency in EMAGE dataset is identified through identifying data which do
not conform to EMAGE‟s textual annotation rules. These rules include the general
“detected somewhere in” and “not detected everywhere in” rules which are used to
propagate gene expression levels up and down the hierarchical structure of a
particular EMAP anatomy. In addition, the expression level of a gene in a particular structure
of a given Theiler stage in EMAGE dataset is reasoned through propagation approach.
Through propagation approach, the associated level of gene expression in tissues that
exhibit “is_part_of” relationship with other tissue(s) within a particular structure are
propagated up or down the given structure in line with the chosen level of gene
expression of that structure. As a consequence, gene expression levels could be
inconsistent. This can be as a result of positive propagation (expressions propagated up the
anatomy) that contradicts with an experimental result or negative propagation
(expressions propagated down the anatomy) that contradicts with an experimental result.
Also, gene expression can be completely contradictory (two experiments on the same
tissue in which a gene is stated as detected in one experiment and not detected in the
second experiment) or partly contradictory (two experiments on the same tissue in
which the genes detected have different expression levels). Also, Inconsistency in
EMAGE datasets has been categorized and defined [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] as either binary inconsistency:
gene that is both expressed and not expressed in a given tissue of a Theiler stage and
analogue inconsistency: involving varied strength levels of a particular gene in a
given tissue of a Theiler stage.
      </p>
      <p>In other to identify inconsistent RDF data, a subset of EMAGE RDF model
dataset was stored in OWLIM-SE triple store (http://www.ontotext.com/owlim). The
investigated dataset has 1,216,277 triples. The author applied appropriate SPARQL
queries as to retrieve inconsistent data from the stored RDF dataset. He was able to
detect binary inconsistency in the investigated dataset in some tissues which have
“is_part_of” relationship with other tissues of the same hierarchical annotation
structure. In these tissues, a gene is specified as “detected” and also specified as “not
detected” in their related tissue. An example of EMAGE hierarchical annotation
structure is shown in the figure 2 below. The SPARQL query in figure 3 identifies RDF
data with binary inconsistency from Theiler stage 15 of the investigated HWU RDF
model dataset. It can also be applied to any other Theiler stage by changing the
Theiler stage number in the statement under label #3 of the query. Table 1 displays the
result set. The author used the hash key (#) together with a unique number in the
SPARQL query to identify comments that explain the SPARQL statement(s).</p>
      <p>To illustrate the different types of inconsistent data in the investigated dataset, the
author used instances from Theiler stage 15. Figure 2 shows a subset of EMAP
anatomy of Theiler stage 15.
#1 Declare URI namespace
prefix hwu: &lt;http://www.cubist_project.eu/HWU#&gt;
prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt;
prefix rdf: http://www.w3.org/1999/02/22-rdf-syntax-ns#
#2 Select variables whose bindings are returned as solutions of the query
SELECT DISTINCT ?gene_label ?t_label ?t_Experiment_label
?gene_strength ?t2_label ?t2_Experiment_label ?gene_strength2
where { {
#3 Select a set of triple pattern that depicts the investigated RDF data: Set ‘A’
?x rdf:type hwu:Textual_Annotation ; hwu:belongs_to_experiment
?y ; hwu:in_tissue ?z ; hwu:has_involved_gene ?g ;
hwu:has_strength ?gene_strength .
?z hwu:has_theiler_stage hwu:theiler_stage_15 ; rdfs:label
?t_label .
?y rdfs:label ?t_Experiment_label .
?g rdfs:label ?gene_label
}
OPTIONAL #4 SPARQL key word which enables optional match
{
#5 Select optional variables contradicting set ‘A’ in another set: set ‘B’
?b rdf:type hwu:Textual_Annotation ; hwu:belongs_to_experiment
?y2 ; hwu:in_tissue ?ztissue2 ; hwu:has_involved_gene ?g ;
hwu:has_strength ?gene_strength2 .
?ztissue2 rdfs:label ?t2_label .
?y2 rdfs:label ?t2_Experiment_label .
#6 Stipulate the relationship between set ‘A’ and set ‘B’
?z hwu:is_part_of ?ztissue2 .
#7 Stipulate the necessary condition that can ascertain any
#7 possible contradictory values between set ‘A’ and set ‘B’
Filter(?gene_strength = hwu:level_detected &amp;&amp; ?gene_strength2
= hwu:level_not_detected ) } }
#8 Aggregate values of variables to be returned
group by ?gene_label ?t_label ?t_Experiment_label
?gene_strength ?t2_label ?t2_Experiment_label ?gene_strength2
#9 Restrict expected results to allow only the output of contradictory values
having ((round((count(?t2_label))/(count(?t_label))*100)) &gt; 0)
#10 Establish the order for the result set
order by ?gene_label
The result set in table 1 above, shows identified binary inconsistent RDF data in
Theiler stage 15. As an example, some tissues (future midbrain and future
rhombencephalon of experiments EMAGE:3530 and EMAGE:3879 respectively) with
involved gene “Pax2” whose expression level are specified as “level_detected” were
identified. Future midbrain and Future rhombencephalon have the same involved
gene “Pax2” and a “is_part_of” relationship with the tissue “Future brain” whose
expression level is specified as “level_not_detected” in EMAGE:984. These
expression levels of Pax2 as specified in these experiments contradict each other and do not
abide with the semantics of the word “is_part_of” as utilized by EMAP. In addition,
analogue inconsistency was detected in the investigated dataset in some tissues which
have “is_part_of” relationship with other tissues. The identified analogue inconsistent
data involve a gene with varied strength levels such as “strong” and “moderate” in
tissues that have “is_part_of” relationship with other tissues. Analogue inconsistency
in RDF data from Theiler stages 15 of the investigated dataset was identified by
substituting the filter condition under label #7 of figure 3 with the below filter condition:
Filter(?gene_strength = hwu:level_strong &amp;&amp; ?gene_strength2 =
hwu:level_weak || ?gene_strength = hwu:level_moderate &amp;&amp;
?gene_strength2 = hwu:level_weak || ?gene_strength =
hwu:level_strong &amp;&amp; ?gene_strength2 = hwu:level_moderate)</p>
      <p>The result set in table 2, shows the identified analogue inconsistent RDF data in
Theiler stage 15. As an example from the table, some tissues (Branchial arch and
limb of experiment EMAGE:5349) with involved gene “Fkbp3” whose expression
levels are specified as “level_strong” have been identified from the investigated
dataset. Branchial arch and Limb have “is_part_of” relationship with the tissue Embryo.
Yet, Fkbp3 has a level of expression “level_weak” in Embryo in the same experiment.
These expression levels of “Fkbp3” as specified in the experiment contradict each
other and do not abide with the semantics of the word “is_part_of” as utilized by
EMAP. Examples from other EMAGE inconsistency types include the inconsistency
from positive propagation: Gene “Pax2” was “detected” in Future midbrain in
EMAGE:3879 and “not detected” in Future brain in EMAGE:984 (Table 1). Future
midbrain is part of future brain and it is located at a lower part to future brain in the
anatomy structure of Theiler stage 15 (figure 2). Future brain should unavoidably
have the same gene expression as future midbrain if gene expression is to be
propagated up the anatomy. The strength level of future brain is therefore contradicted by
not fully propagating Future midbrain’s gene expression level up the anatomy and
this result to „an inconsistency of positive propagation‟. On the other hand, Future
midbrain should unavoidably have the same gene expression level as future brain if
gene expression is to be propagated down the anatomy. The strength level of future
midbrain was contradicted by not fully propagating the gene expression level in
future brain down the anatomy and this result to „an inconsistency of negative
propagation‟. Figure 2 shows the tree illustrating the hierarchical structure of future midbrain
and future brain in Theiler stage 15.</p>
      <p>4</p>
    </sec>
    <sec id="sec-4">
      <title>Evaluating and analyzing inconsistent RDF data</title>
      <p>
        There are two main methods of dealing with inconsistent data in a dataset: to diagnose
and repair it, and reasoning with the inconsistency [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Also, various approaches such
as [
        <xref ref-type="bibr" rid="ref7 ref8">7, 8</xref>
        ] have been proposed on reasoning with the inconsistent data. The act of
addressing inconsistent data through identifying the inconsistency with the aim of
repairing it through deleting the inconsistent data will inevitably increase the
incompleteness of the dataset. More so, the use of various reasoning approaches on
inconsistent dataset would produce varied result sets for a given approach on the dataset.
These lapses can be addressed through measuring and detailing of the inconsistencies
in the retrieved information from an inconsistent dataset.
      </p>
      <p>
        Obviously, measuring inconsistency has been proven useful in analyzing diverse
range of information types such as news reports [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. However, there are a few
approaches [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ] for measuring the inconsistencies of semantic datasets. There are other
publications which verify and validate the RDF data held within a database [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ] but
these works do not measure and analyze the amount of inconsistency in inconsistent
information retrieved from the database. Consequently, the author assesses the
amount of inconsistency in inconsistent information from a graph based approach. He
achieves this through adopting the sub graph matching powers of SPARQL queries.
5
      </p>
    </sec>
    <sec id="sec-5">
      <title>Approach</title>
      <p>The amount of inconsistency in an investigated RDF data can be measured by
evaluating the amount of contradiction in the RDF data against the likelihood of the
contradiction to occur. This amount is assessed herein by calculating their ratio as a
fraction of 100. The result educates us on how large/small the embedded contradiction in
the RDF data is. As stated above, the amount of inconsistency in EMAGE‟s data from
a graph based approach is herein assessed through adopting the mathematical and sub
graph matching powers of SPARQL queries. This approach can be applied to all RDF
dataset formats. It necessitates proper SPARQL query skills and adequate knowledge
of the dataset by the dataset analyst. The amount of contradictions in the data under
investigation against its total possibility to occur in the dataset is calculated as
follows:</p>
      <p>Xm =A RDF graph pattern in a RDF dataset
Xk = Contradictory sub graph of Xm
The interest is in calculating the amount of Xk in Xm such that
= Total number of contradictions in Xk
= Total number of occurrence of Xm in the dataset</p>
      <p>Amount of Inconsistency in Xm =
 Xk
 Xm</p>
      <p>In this investigation, the question “what amount of binary or analogue
contradiction is present in the expression levels of the genes in each tissue experiment of
Theiler stage 15” is answered. The amount of Binary or analogue inconsistency in RDF
data from any of the Theiler stages of the investigated dataset is identified by adding
the following SPARQL statement before label #2 of figure 3.</p>
      <sec id="sec-5-1">
        <title>Select ?gene_label ?t_Experiment_label round((count(?gene_strength2))/(count(?gene_strength))) * 100) as ?amount_of_inconsistency) {</title>
        <p>And also substituting the aggregation statement under the label #8 of the query with
the below statement:</p>
      </sec>
      <sec id="sec-5-2">
        <title>Group by ?gene_label ?t_Experiment_label</title>
        <p>The result set of the administered query on Theiler stage 15 is as displayed in table
3 and 4 below.
Table 3 above, gives a more clarifying result set of each inconsistent experiment in
Theiler stage 15 of the dataset than table 1. Rather than listing inconsistent
experiments singly (like in table 1), the amount of its occurrence in the RDF data with the
stipulated pattern is measured. These measures inform us of the amount of
inconsistent assays in each tissue experiment of a particular Theiler stage in the dataset. As an
example in EMAGE:3530, it can reliably be stated that half (50%) of the assays are
binary inconsistent. While in EMAGE:3879, less than half (33%) of the assays results
are binary inconsistent. Consequently, decisions by Biologists to carry out further test
or to remove existing experimental results from the dataset can be made.</p>
        <p>A tissue experiment can have several assays. The author‟s approach identifies the
amount of these inconsistent assay(s) in their corresponding tissue experiment. For
example, in Theiler stage 15 of the investigated dataset, there are 6 assays on
EMAGE:3879, and 2 of them are binary inconsistent thus the amount of inconsistency
in the experiment is calculated by dividing 2 with 6 and multiplied the result by 100.
The importance of identifying the amount of inconsistency in a tissue experiment is to
identify how valid the assay results of a particular experiment are.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>Conclusion</title>
      <p>Evaluating and analyzing inconsistent RDF data of a RDF model dataset is a field yet
to be explored. Interestingly, it has been shown in this paper that the measure and
analysis of inconsistent RDF data gives an insight to the soundness of the information
under investigation. Nevertheless, the author hopes to improve on this research by
automating these processes of identifying, evaluating and analyzing inconsistent RDF
data.</p>
      <p>The author acknowledges the partners of CUBIST project especially Heriot-Watt
University and Sheffield Hallam University for their support and provision of his
research datasets. He also acknowledges his two PhD supervisors “Simon Andrews”
and “Simon Polovina" for their invaluable contributions and review of this work.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Grant</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Hunter</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2006</year>
          ).
          <article-title>Measuring inconsistency in knowledgebases</article-title>
          .
          <source>Journal of Intelligent Information Systems</source>
          ,
          <volume>27</volume>
          (
          <issue>2</issue>
          ),
          <fpage>159</fpage>
          -
          <lpage>184</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Grant</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Hunter</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2008</year>
          ).
          <article-title>Analysing inconsistent first-order knowledgebases</article-title>
          .
          <source>Artificial Intelligence</source>
          ,
          <volume>172</volume>
          (
          <issue>8</issue>
          ),
          <fpage>1064</fpage>
          -
          <lpage>1093</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Huang</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>van Harmelen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <article-title>and ten</article-title>
          <string-name>
            <surname>Teije</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2006</year>
          ).
          <article-title>Reasoning with inconsistent ontologies: Framework, prototype, and experiment</article-title>
          .
          <source>Semantic Web Technologies: Trends and Research in Ontology-Based Systems</source>
          ,
          <volume>71</volume>
          -
          <fpage>93</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Hunter</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2002</year>
          ,
          <article-title>July)</article-title>
          .
          <article-title>Measuring inconsistency in knowledge via quasi-classical models</article-title>
          .
          <source>In PROCEEDINGS OF THE NATIONAL CONFERENCE ON ARTIFICIAL INTELLIGENCE</source>
          (pp.
          <fpage>68</fpage>
          -
          <lpage>73</lpage>
          ). Menlo Park, CA; Cambridge, MA; London; AAAI Press; MIT Press;
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Jerven</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sebastien</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <article-title>and the UniProt Consortium</article-title>
          .
          <article-title>Catching inconsistencies with the semantic web: a biocuration case study</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Jupp</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parkinson</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Malone</surname>
          </string-name>
          ,
          <source>J. Semantic Web Atlas: Putting Gene Expression Data Into Biological Context.</source>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Lembo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lenzerini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rosati</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ruzzi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Savo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          (
          <year>2010</year>
          ).
          <article-title>Inconsistencytolerant semantics for description logics</article-title>
          .
          <source>Web Reasoning and Rule Systems</source>
          ,
          <volume>103</volume>
          -
          <fpage>117</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>McLeod</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Burger</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2007</year>
          ).
          <article-title>Using argumentation to tackle inconsistency and incompleteness in online distributed life science resources</article-title>
          .
          <source>In Proceedings of IADIS International Conference Applied Computing</source>
          (pp.
          <fpage>489</fpage>
          -
          <lpage>492</lpage>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>McLeod</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Burger</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2011</year>
          ).
          <article-title>WP7 requirement document of CUBIST Consortium 2010-2013</article-title>
          . Available at http://www.cubistproject.eu/fileadmin/CUBIST/user_upload/Deliverable/CUBIST_D7.
          <article-title>1.1_HWU_v1.0</article-title>
          .pdf
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Richardson</surname>
            <given-names>L</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Venkataraman</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stevenson</surname>
            <given-names>P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yang</surname>
            <given-names>Y</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burton</surname>
            <given-names>N</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rao</surname>
            <given-names>J</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fisher</surname>
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Baldock</surname>
            <given-names>RA</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Davidson</surname>
            <given-names>DR</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Christiansen</surname>
            <given-names>JH</given-names>
          </string-name>
          .
          <article-title>EMAGE mouse embryo spatial gene expression database: 2010</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Suda</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hossain</surname>
            ,
            <given-names>Z. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kobayashi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hatano</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yoshida</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Matsuo</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Aizawa</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2001</year>
          ).
          <article-title>Emx2 directs the development of diencephalon in cooperation with Otx2</article-title>
          .
          <source>Development</source>
          ,
          <volume>128</volume>
          (
          <issue>13</issue>
          ),
          <fpage>2433</fpage>
          -
          <lpage>2450</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Theiler</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          (
          <year>1989</year>
          ).
          <article-title>The house mouse: atlas of embryonic development</article-title>
          (p.
          <fpage>168</fpage>
          ). New York: Springer-Verlag.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>