<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="other" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">F1000Research</journal-id>
            <journal-title-group>
                <journal-title>F1000Research</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2046-1402</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/f1000research.13197.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Software Tool Article</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                    <subj-group>
                        <subject>Bioinformatics</subject>
                    </subj-group>
                    <subj-group>
                        <subject>Drug Discovery &amp; Design</subject>
                    </subj-group>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>Explicit interaction information from WikiPathways in RDF facilitates drug discovery in the Open PHACTS Discovery Platform</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 2 approved with reservations]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Miller</surname>
                        <given-names>Ryan A.</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-3477-7443</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Woollard</surname>
                        <given-names>Peter</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-7654-6902</uri>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Willighagen</surname>
                        <given-names>Egon L.</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-7542-0286</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Digles</surname>
                        <given-names>Daniela</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Data Curation</role>
                    <xref ref-type="aff" rid="a3">3</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Kutmon</surname>
                        <given-names>Martina</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-7699-8191</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a4">4</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Loizou</surname>
                        <given-names>Antonis</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Software</role>
                    <xref ref-type="aff" rid="a5">5</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Waagmeester</surname>
                        <given-names>Andra</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-9773-4008</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a6">6</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Senger</surname>
                        <given-names>Stefan</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <xref ref-type="aff" rid="a2">2</xref>
                    <xref ref-type="aff" rid="a7">7</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Evelo</surname>
                        <given-names>Chris T.</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Supervision</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-5301-3142</uri>
                    <xref ref-type="aff" rid="a1">1</xref>
                    <xref ref-type="aff" rid="a4">4</xref>
                    <xref ref-type="aff" rid="a7">7</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>Department of Bioinformatics (BiGCaT), Maastricht University, Maastricht, The Netherlands</aff>
                <aff id="a2">
                    <label>2</label>GlaxoSmithKline (GSK), Stevenage, UK</aff>
                <aff id="a3">
                    <label>3</label>Pharmacoinformatics Research Group, Department of Pharmaceutical Chemistry, University of Vienna, Vienna, Austria</aff>
                <aff id="a4">
                    <label>4</label>Maastricht Center for Systems Biology (MaCSBio), Maastricht University, Maastricht, The Netherlands</aff>
                <aff id="a5">
                    <label>5</label>Blue Sky IT, Amsterdam, The Netherlands</aff>
                <aff id="a6">
                    <label>6</label>Micelio, Antwerp, Belgium</aff>
                <aff id="a7">
                    <label>7</label>Open PHACTS Foundation, Science Park, Cambridge, UK</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:ryan.miller@maastrichtuniversity.nl">ryan.miller@maastrichtuniversity.nl</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>17</day>
                <month>1</month>
                <year>2018</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2018</year>
            </pub-date>
            <volume>7</volume>
            <elocation-id>75</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>13</day>
                    <month>12</month>
                    <year>2017</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2018 Miller RA et al.</copyright-statement>
                <copyright-year>2018</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/7-75/pdf"/>
            <abstract>
                <p>Open PHACTS is a pre-competitive project to answer scientific questions developed recently by the pharmaceutical industry. Having high quality biological interaction information in the Open PHACTS Discovery Platform is needed to answer multiple pathway related questions. To address this, updated WikiPathways data has been added to the platform. This data includes information about biological interactions, such as stimulation and inhibition. The platform&#x2019;s Application Programming Interface (API) was extended with appropriate calls to reference these interactions. These new methods of the Open PHACTS API are available now.</p>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>Open PHACTS</kwd>
                <kwd>drug discovery</kwd>
                <kwd>semantic</kwd>
                <kwd>bioinformatics</kwd>
                <kwd>WikiPathways</kwd>
                <kwd>pathway database</kwd>
                <kwd>API</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1">
                    <funding-source>Innovative Medicines Initiative Joint Undertaking</funding-source>
                    <award-id>115191</award-id>
                </award-group>
                <funding-statement>This work was supported by the Innovative Medicines Initiative Joint Undertaking [115191], resources of which are composed of financial contribution from the European Union&#x2019;s Seventh FrameworkProgramme (FP7/2007-2013) and EFPIA companies&#x2019; in kind contribution.</funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec sec-type="intro">
            <title>Introduction</title>
            <p>Targeting proteins to ideally restore normal biological processes is a common starting point in drug discovery
                <sup>
                    <xref ref-type="bibr" rid="ref-1">1</xref>
                </sup>. The Open PHACTS Discovery Platform (OPDP) was designed to help identify protein targets and information about their associations with each other
                <sup>
                    <xref ref-type="bibr" rid="ref-2">2</xref>&#x2013;
                    <xref ref-type="bibr" rid="ref-4">4</xref>
                </sup>. The OPDP supports target identification and validation by including target-target interactions from WikiPathways
                <sup>
                    <xref ref-type="bibr" rid="ref-5">5</xref>&#x2013;
                    <xref ref-type="bibr" rid="ref-7">7</xref>
                </sup>. Of these interaction networks, proteins sharing a downstream path allows investigation of alternative drug target combinations. Even the knowledge of which biological pathways participate in disease-related processes provides insight in the pathway topology between the targets. The importance and need of providing access to interaction information for real-world research questions was outlined in a recent Open PHACTS paper
                <sup>
                    <xref ref-type="bibr" rid="ref-8">8</xref>
                </sup>.</p>
            <p>The Open PHACTS project was born out of the desire to integrate pharmacological data from multiple pre-competitive sources to efficiently address scientific questions that cannot be answered with single data sources
                <sup>
                    <xref ref-type="bibr" rid="ref-8">8</xref>
                </sup>. It integrates data using linked data approaches
                <sup>
                    <xref ref-type="bibr" rid="ref-3">3</xref>
                </sup> from chemical and biological sources such as ChEBI, ChEMBL, UniProt, and WikiPathways
                <sup>
                    <xref ref-type="bibr" rid="ref-6">6</xref>
                </sup>. However, the OPDP did not previously include calls to access specific up- and downstream interaction effects. This information is needed for questions related to drug repositioning and repurposing. Up- or downstream targets may be interesting alternatives with similar therapeutic effect to targets, for which it is particularly hard to develop an drug agent. Thus, finding a target that has already been drugged or is more drug tractable will be advantageous. Here we describe how to identify alternative targets in the same cellular pathway using OPDP against the WikiPathways data.</p>
        </sec>
        <sec sec-type="methods">
            <title>Methods</title>
            <sec>
                <title>Implementation</title>
                <p>The WikiPathways Resource Description Framework data (WPRDF) is released as part of the monthly releases
                    <sup>
                        <xref ref-type="bibr" rid="ref-5">5</xref>
                    </sup>. It includes details about directed and undirected interactions. Directed biochemical interactions capture the source and target which are depicted as an arrow in simple pathway drawings. WikiPathways adds biological meaning to interactions with Molecular Interaction Map (MIM) interaction types, like inhibitions, enzyme catalyzed reactions, and stimulations
                    <sup>
                        <xref ref-type="bibr" rid="ref-9">9</xref>
                    </sup>, as well as Systems Biology Graphical Notation (SBGN) interactions
                    <sup>
                        <xref ref-type="bibr" rid="ref-10">10</xref>
                    </sup>. Reactome pathways in WikiPathways use SBGN interactions
                    <sup>
                        <xref ref-type="bibr" rid="ref-11">11</xref>,
                        <xref ref-type="bibr" rid="ref-12">12</xref>
                    </sup>. However, because MIM and SBGN use different drawing styles, we normalize their inhibition types into a common inhibition type, defined by the WikiPathways ontology (
                    <ext-link ext-link-type="uri" xlink:href="https://vocabularies.wikipathways.org/wp">https://vocabularies.wikipathways.org/wp</ext-link>).</p>
                <p>The WikiPathways basic drawing tools also contain generic arrows and t-bar annotations that give the user the ability to create basic diagrams without the semantic meaning of MIM or SBGN notations. The interactions connecting these nodes are captured, but the only explicit information is that it is a directed interaction from a source to a target. To handle more complicated enzyme reaction drawings, where there is not a single line that directly connects targets in a cascade of enzymatic reactions, a query was developed that recognizes these types of reactions. However, this is not implemented in the current Open PHACTS Application Programming Interface (API).</p>
                <p>Version 2.1 of the OPDP API contains three new calls for interactions and their pathways.  The first call, 
                    <italic toggle="yes">/pathway/getInteractions</italic>, returns all interactions involved in a pathway. To use this feature, the user specifies a pathway URI and OPDP returns its interactions including information about direction and the connected entities. The direction information is relayed as a starting node having a 
                    <italic toggle="yes">wp:source</italic> annotation, while the end of the interaction has the 
                    <italic toggle="yes">wp:target</italic> annotation. In its simplest form, this means that if gene product A is interacting with a gene product B, then we have 
                    <italic toggle="yes">wp:source</italic> for product A and 
                    <italic toggle="yes">wp:target</italic> for product B. However, the new methods also support interactions with multiple sources and targets.</p>
                <p>The second added call, 
                    <italic toggle="yes">/pathways/interactions/byEntity</italic>, returns the direction of the interactions involving this entity. An entity is specified by a URI and can be a metabolite, protein, gene product, or RNA. API options allow the user to select only upstream or only downstream interactions. The results also specify the interaction type (e.g. inhibition, stimulation, conversion). This ability to select the interaction direction is specifically what allows users to answer scientific questions around upstream and downstream effects, such as those defined by Open PHACTS. The third API call is 
                    <italic toggle="yes">/pathways/interactions/byEntity/count</italic> which is a helper function that returns the number of interactions for a target.</p>
            </sec>
            <sec>
                <title>Operation</title>
                <p>The OPDP API calls are backed by SPARQL searches against the loaded WikiPathways RDF. The query parameters that are required or optional are given in the documentation of Open PHACTS (
                    <ext-link ext-link-type="uri" xlink:href="https://dev.openphacts.org/docs/2.1">https://dev.openphacts.org/docs/2.1</ext-link>). As in previous versions, the API uses HTTP GET to call methods and needs a (free) application ID and key
                    <sup>
                        <xref ref-type="bibr" rid="ref-3">3</xref>
                    </sup>.</p>
            </sec>
        </sec>
        <sec>
            <title>Example queries</title>
            <p>We are demonstrating the platform with three example calls. All the API calls require use of an application ID and an application key. This key and ID can be acquired by creating a free Open PHACTS account. The first example is an application to the PI3K/AKT pathway for cell growth regulation which contain important targets for cancer treatment
                <sup>
                    <xref ref-type="bibr" rid="ref-13">13</xref>
                </sup>. The AKT protein has a central role and usefully shows the API call&#x2019;s ability to return connected elements with the first and third calls. The API call can help aid drug discovery by taking a target, in this case AKT, and easily identify other connected proteins that could potentially be used as drug targets with a common downstream effect.</p>
            <p>
                <xref ref-type="fig" rid="f1">Figure 1</xref> shows the web interface of the API call that returns the connectivity of the AKT2 target to both upstream or downstream proteins or gene products. This method allows the user to identify connections to other targets in the pathway. The results of that API call (
                <xref ref-type="fig" rid="f2">Figure 2</xref>) show the AKT2 interaction with microRNA. A helper method (
                <xref ref-type="fig" rid="f3">Figure 3</xref>): 
                <italic toggle="yes">/pathways/interactions/byEntity/count</italic> is also included. It returns the number of all interactions in which an entity is participates. This helps the user get a sense of the prevalence of the queried entity with interactions in pathways found on WikiPathways.</p>
            <fig fig-type="figure" id="f1" orientation="portrait" position="float">
                <label>Figure 1. </label>
                <caption>
                    <title>Parameters (bottom) and 
                        <italic toggle="yes">curl</italic> command (top) for the GET 
                        <italic toggle="yes">/pathways/interactions/byEntity</italic> call.</title>
                    <p>The GET portion tells the API to retrieve data with the associated call. It takes an entity URI, the Ensembl ID for AKT2, and returns a list interactions for AKT2. The obligatory parameters are shown in bold.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/14318/cd1971d8-06dc-4daa-addd-7014665d36d0_figure1.gif"/>
            </fig>
            <fig fig-type="figure" id="f2" orientation="portrait" position="float">
                <label>Figure 2. </label>
                <caption>
                    <title>Result in the JSON format of the AKT2 query from 
                        <xref ref-type="fig" rid="f1">Figure 1</xref>.</title>
                    <p>The participants of the interaction are directed from source (hsa-let7b) to target (AKT2). It also shows the type of interaction (inhibition), and the biological types of the interaction participants.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/14318/cd1971d8-06dc-4daa-addd-7014665d36d0_figure2.gif"/>
            </fig>
            <fig fig-type="figure" id="f3" orientation="portrait" position="float">
                <label>Figure 3. </label>
                <caption>
                    <title>Parameters (bottom) and 
                        <italic toggle="yes">curl</italic> command (top) for the GET 
                        <italic toggle="yes">/pathways/interactions/byEntity/count</italic> call.</title>
                    <p>It takes a URI for an entity, in this case the Ensembl ID for AKT2 and returns a count of the interactions to which this gene product is involved. Only the entity URI, app ID, and app key are required fields. Optional parameters are pathway organism, direction, or type of interaction.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/14318/cd1971d8-06dc-4daa-addd-7014665d36d0_figure3.gif"/>
            </fig>
            <p>The other call implemented, 
                <italic toggle="yes">/pathway/getInteractions</italic> (
                <xref ref-type="fig" rid="f4">Figure 4</xref>), demonstrates an API call to return all interactions in the MicroRNAs in cardiomyocyte hypertrophy pathway
                <sup>
                    <xref ref-type="bibr" rid="ref-14">14</xref>
                </sup>. This pathway has interaction details for AKT, mTOR, and PI3K, which are all important targets in cancer research
                <sup>
                    <xref ref-type="bibr" rid="ref-15">15</xref>
                </sup>. For each interaction the participants are given and whether it is a directed or undirected interaction.</p>
            <fig fig-type="figure" id="f4" orientation="portrait" position="float">
                <label>Figure 4. </label>
                <caption>
                    <title>Parameters (bottom) and 
                        <italic toggle="yes">curl</italic> command (top) for the 
                        <italic toggle="yes">/pathways/getInteractions</italic> call.</title>
                    <p>It is intended to take the pathway URI from WikiPathways and return a list of interaction involved in that particular pathway. Pathway URI, app ID, and app key are the only required values for this call.</p>
                </caption>
                <graphic orientation="portrait" position="float" xlink:href="https://f1000research-files.f1000.com/manuscripts/14318/cd1971d8-06dc-4daa-addd-7014665d36d0_figure4.gif"/>
            </fig>
        </sec>
        <sec>
            <title>Summary</title>
            <p>The addition of interactions with direction information allows OPDP to answering more of the pre-defined scientific questions
                <sup>
                    <xref ref-type="bibr" rid="ref-16">16</xref>
                </sup>. The directional information allows the user to explore how proteins and gene products are connected with one another and easily access this information. This is illustrated in the example queries using the cancer target AKT.</p>
        </sec>
        <sec>
            <title>Software availability</title>
            <p>Online service:  
                <ext-link ext-link-type="uri" xlink:href="https://dev.openphacts.org/docs/2.1">https://dev.openphacts.org/docs/2.1</ext-link>
            </p>
            <p>Latest  source  code  is  available  at: 
                <ext-link ext-link-type="uri" xlink:href="https://github.com/openphacts/OPS_LinkedDataApi">https://github.com/openphacts/OPS_LinkedDataApi</ext-link>
            </p>
            <p>Archived  source  code  of  discussed  version:  
                <ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.5281/zenodo.1068252">https://doi.org/10.5281/zenodo.1068252</ext-link>
                <sup>
                    <xref ref-type="bibr" rid="ref-17">17</xref>
                </sup>
            </p>
            <p>License: Apache License 2.0</p>
        </sec>
    </body>
    <back>
        <ack>
            <title>Acknowledgments</title>
            <p>A special thanks goes to all members of the Open PHACTS project that provided the platform that was necessary.</p>
        </ack>
        <ref-list>
            <ref id="ref-1">
                <label>1</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Schreiber</surname>
                            <given-names>SL</given-names>
                        </name>
						</person-group>:
                    <article-title>Target-oriented and diversity-oriented organic synthesis in drug discovery.</article-title>
                    <source>
						
                        <italic toggle="yes">Science.</italic>
					</source>
                    <year>2000</year>;<volume>287</volume>(<issue>5460</issue>):<fpage>1964</fpage>&#x2013;<lpage>1969</lpage>.
                    <pub-id pub-id-type="pmid">10720315</pub-id>
                    <pub-id pub-id-type="doi">10.1126/science.287.5460.1964</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-2">
                <label>2</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Azzaoui</surname>
                            <given-names>K</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Jacoby</surname>
                            <given-names>E</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Senger</surname>
                            <given-names>S</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>Scientific competency questions as the basis for semantically enriched open pharmacological space development.</article-title>
                    <source>
						
                        <italic toggle="yes">Drug Discov Today.</italic>
					</source>
                    <year>2013</year>;<volume>18</volume>(<issue>17&#x2013;18</issue>):<fpage>843</fpage>&#x2013;<lpage>852</lpage>.
                    <pub-id pub-id-type="pmid">23702085</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.drudis.2013.05.008</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-3">
                <label>3</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Williams</surname>
                            <given-names>AJ</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Harland</surname>
                            <given-names>L</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Groth</surname>
                            <given-names>P</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>Open PHACTS: semantic interoperability for drug discovery.</article-title>
                    <source>
						
                        <italic toggle="yes">Drug Discov Today.</italic>
					</source>
                    <year>2012</year>;<volume>17</volume>(<issue>21&#x2013;22</issue>):<fpage>1188</fpage>&#x2013;<lpage>1198</lpage>.
                    <pub-id pub-id-type="pmid">22683805</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.drudis.2012.05.016</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-4">
                <label>4</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Digles</surname>
                            <given-names>D</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Zdrazil</surname>
                            <given-names>B</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Neefs</surname>
                            <given-names>JM</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>Open PHACTS computational protocols for 
                        <italic toggle="yes">in silico</italic> target validation of cellular phenotypic screens: knowing the knowns.</article-title>
                    <source>
						
                        <italic toggle="yes">Medchemcomm.</italic>
					</source>
                    <year>2016</year>;<volume>7</volume>(<issue>6</issue>):<fpage>1237</fpage>&#x2013;<lpage>1244</lpage>.
                    <pub-id pub-id-type="pmid">27774140</pub-id>
                    <pub-id pub-id-type="doi">10.1039/c6md00065g</pub-id>
                    <pub-id pub-id-type="pmcid">5063042</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-5">
                <label>5</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Waagmeester</surname>
                            <given-names>A</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Kutmon</surname>
                            <given-names>M</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Riutta</surname>
                            <given-names>A</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>Using the Semantic Web for Rapid Integration of WikiPathways with Other Biological Online Data Resources.</article-title>
                    <source>
						
                        <italic toggle="yes">PLoS Comput Biol.</italic>
					</source>
                    <year>2016</year>;<volume>12</volume>(<issue>6</issue>):<fpage>e1004989</fpage>.
                    <pub-id pub-id-type="pmid">27336457</pub-id>
                    <pub-id pub-id-type="doi">10.1371/journal.pcbi.1004989</pub-id>
                    <pub-id pub-id-type="pmcid">4918977</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-6">
                <label>6</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Gray</surname>
                            <given-names>AJG</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Groth</surname>
                            <given-names>P</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Loizou</surname>
                            <given-names>A</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>Applying linked data approaches to pharmacology: Architectural decisions and implementation.</article-title>
                    <source>
						
                        <italic toggle="yes">Semant Web.</italic>
					</source>
                    <year>2014</year>;<volume>5</volume>(<issue>2</issue>):<fpage>101</fpage>&#x2013;<lpage>113</lpage>.
                    <pub-id pub-id-type="doi">10.3233/SW-2012-0088</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-7">
                <label>7</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Kelder</surname>
                            <given-names>T</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Pico</surname>
                            <given-names>AR</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Hanspers</surname>
                            <given-names>K</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>Mining biological pathways using WikiPathways web services.</article-title>
                    <source>
						
                        <italic toggle="yes">PLoS One.</italic>
					</source>
                    <year>2009</year>;<volume>4</volume>(<issue>7</issue>):<fpage>e6447</fpage>.
                    <pub-id pub-id-type="pmid">19649250</pub-id>
                    <pub-id pub-id-type="doi">10.1371/journal.pone.0006447</pub-id>
                    <pub-id pub-id-type="pmcid">2714472</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-8">
                <label>8</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Chichester</surname>
                            <given-names>C</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Digles</surname>
                            <given-names>D</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Siebes</surname>
                            <given-names>R</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>Drug discovery FAQs: workflows for answering multidomain drug discovery questions.</article-title>
                    <source>
						
                        <italic toggle="yes">Drug Discov Today.</italic>
					</source>
                    <year>2015</year>;<volume>20</volume>(<issue>4</issue>):<fpage>399</fpage>&#x2013;<lpage>405</lpage>.
                    <pub-id pub-id-type="pmid">25463038</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.drudis.2014.11.006</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-9">
                <label>9</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Luna</surname>
                            <given-names>A</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Karac</surname>
                            <given-names>EI</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Sunshine</surname>
                            <given-names>M</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>A formal mim specification and tools for the common exchange of mim diagrams: an xml-based format, an api, and a validation method.</article-title>
                    <source>
						
                        <italic toggle="yes">BMC Bioinformatics.</italic>
					</source>
                    <year>2011</year>;<volume>12</volume>(<issue>1</issue>):<fpage>167</fpage>.
                    <pub-id pub-id-type="pmid">21586134</pub-id>
                    <pub-id pub-id-type="doi">10.1186/1471-2105-12-167</pub-id>
                    <pub-id pub-id-type="pmcid">3118169</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-10">
                <label>10</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Le Nov&#x00e8;re</surname>
                            <given-names>NL</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Hucka</surname>
                            <given-names>M</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Mi</surname>
                            <given-names>H</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>The systems biology graphical notation.</article-title>
                    <source>
						
                        <italic toggle="yes">Nat Biotechnol.</italic>
					</source>
                    <year>2009</year>;<volume>27</volume>(<issue>8</issue>):<fpage>735</fpage>&#x2013;<lpage>741</lpage>.
                    <pub-id pub-id-type="pmid">19668183</pub-id>
                    <pub-id pub-id-type="doi">10.1038/nbt.1558</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-11">
                <label>11</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Kutmon</surname>
                            <given-names>M</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Riutta</surname>
                            <given-names>A</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Nunes</surname>
                            <given-names>N</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>WikiPathways: capturing the full diversity of pathway knowledge.</article-title>
                    <source>
						
                        <italic toggle="yes">Nucleic Acids Res.</italic>
					</source>
                    <year>2016</year>;<volume>44</volume>(<issue>D1</issue>):<fpage>D488</fpage>&#x2013;<lpage>D494</lpage>.
                    <pub-id pub-id-type="pmid">26481357</pub-id>
                    <pub-id pub-id-type="doi">10.1093/nar/gkv1024</pub-id>
                    <pub-id pub-id-type="pmcid">4702772</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-12">
                <label>12</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Croft</surname>
                            <given-names>D</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Mundo</surname>
                            <given-names>AF</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Haw</surname>
                            <given-names>R</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>The reactome pathway knowledgebase.</article-title>
                    <source>
						
                        <italic toggle="yes">Nucleic Acids Res.</italic>
					</source>
                    <year>2014</year>;<volume>42</volume>(<issue>Database issue</issue>):<fpage>D472</fpage>&#x2013;<lpage>D477</lpage>.
                    <pub-id pub-id-type="pmid">24243840</pub-id>
                    <pub-id pub-id-type="doi">10.1093/nar/gkt1102</pub-id>
                    <pub-id pub-id-type="pmcid">3965010</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-13">
                <label>13</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Vanhaesebroeck</surname>
                            <given-names>B</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Stephens</surname>
                            <given-names>L</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Hawkins</surname>
                            <given-names>P</given-names>
                        </name>
					</person-group>:
                    <article-title>PI3K signalling: the path to discovery and understanding.</article-title>
                    <source>
						
                        <italic toggle="yes">Nat Rev Mol Cell Biol.</italic>
					</source>
                    <year>2012</year>;<volume>13</volume>(<issue>3</issue>):<fpage>195</fpage>&#x2013;<lpage>203</lpage>.
                    <pub-id pub-id-type="pmid">22358332</pub-id>
                    <pub-id pub-id-type="doi">10.1038/nrm3290</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-14">
                <label>14</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Levels</surname>
                            <given-names>M</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Hanspers</surname>
                            <given-names>K</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Kutmon</surname>
                            <given-names>M</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>Micrornas in cardiomyocyte hypertrophy (homo sapiens)</article-title>.<year>2017</year>.
                    <ext-link ext-link-type="uri" xlink:href="http://www.wikipathways.org/instance/WP1544_r89794">Reference Source</ext-link>
                </mixed-citation>
            </ref>
            <ref id="ref-15">
                <label>15</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Li</surname>
                            <given-names>H</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Zeng</surname>
                            <given-names>J</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Shen</surname>
                            <given-names>K</given-names>
                        </name>
					</person-group>:
                    <article-title>PI3K/AKT/mTOR signaling pathway as a therapeutic target for ovarian cancer.</article-title>
                    <source>
						
                        <italic toggle="yes">Arch Gynecol Obstet.</italic>
					</source>
                    <year>2014</year>;<volume>290</volume>(<issue>6</issue>):<fpage>1067</fpage>&#x2013;<lpage>1078</lpage>.
                    <pub-id pub-id-type="pmid">25086744</pub-id>
                    <pub-id pub-id-type="doi">10.1007/s00404-014-3377-3</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-16">
                <label>16</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>Azzaoui</surname>
                            <given-names>K</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Jacoby</surname>
                            <given-names>E</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Senger</surname>
                            <given-names>S</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>Scientific competency questions as the basis for semantically enriched open pharmacological space development.</article-title>
                    <source>
						
                        <italic toggle="yes">Drug Discov Today.</italic>
					</source>
                    <year>2013</year>;<volume>18</volume>(<issue>17&#x2013;18</issue>):<fpage>843</fpage>&#x2013;<lpage>852</lpage>.
                    <pub-id pub-id-type="pmid">23702085</pub-id>
                    <pub-id pub-id-type="doi">10.1016/j.drudis.2013.05.008</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref-17">
                <label>17</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">
						
                        <name name-style="western">
                            <surname>fundatureanu-sever</surname>
                        </name>
							
                        <name name-style="western">
                            <surname>Kerber</surname>
                            <given-names>R</given-names>
                        </name>
						
                        <name name-style="western">
                            <surname>Soiland-Reyes</surname>
                            <given-names>S</given-names>
                        </name>
						
                        <etal/>
					</person-group>:
                    <article-title>openphacts/OPS_LinkedDataApi: Open PHACTS Linked Data API 2.1.0 (Version 2.1.0).</article-title>
                    <source>
						
                        <italic toggle="yes">Zenodo.</italic>
					</source>
                    <year>2016</year>.
                    <ext-link ext-link-type="uri" xlink:href="http://dx.doi.org/10.5281/zenodo.1068252">Data Source</ext-link>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report32325">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.14318.r32325</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Chen</surname>
                        <given-names>Yi-An</given-names>
                    </name>
                    <xref ref-type="aff" rid="r32325a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0003-4936-8060</uri>
                </contrib>
                <aff id="r32325a1">
                    <label>1</label>National Institutes of Biomedical Innovation, Health and Nutrition, Osaka, Japan</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>3</day>
                <month>4</month>
                <year>2018</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2018 Chen YA</copyright-statement>
                <copyright-year>2018</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport32325" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.13197.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>The authors add new features to the&#x00a0;Open PHACTS APIs which facilitate querying reactions in WikiPathways.</p>
            <p> </p>
            <p> Some comments: 
                <list list-type="order">
                    <list-item>
                        <p>In the first example, the query for AKT2 in the figure 1 uses&#x00a0;&#x00a0;
                            <ext-link ext-link-type="uri" xlink:href="http://identifiers.org/ensembl/ENSG00000105221">http://identifiers.org/ensembl/ENSG00000105221</ext-link> but the result in the figure 2 shows 
                            <ext-link ext-link-type="uri" xlink:href="http://identifiers.org/ncbigene/208">http://identifiers.org/ncbigene/208</ext-link>. I guess the API should be able to accept different commonly used identifiers, however, either the article or the web interface mention about the acceptable identifiers. In addition,&#x00a0;It would be nice if the input of the query accepts simple&#x00a0;identifiers, instead of constructing the full&#x00a0;URI.</p>
                    </list-item>
                    <list-item>
                        <p>The result&#x00a0;in figure 2 is difficult to interpret. It would be nice to expand the query to get the basic information for those interacting&#x00a0;entities.&#x00a0;For example, the gene symbol or the compound name.</p>
                    </list-item>
                    <list-item>
                        <p>The examples in figure 3 and figure 4 didn't show the query results.</p>
                    </list-item>
                    <list-item>
                        <p>Simple queries&#x00a0;in the examples may be&#x00a0;difficult to show the usefulness of the new implemented APIs. A more sophisticated application which contains either bulk query or pipeline query&#x00a0;should be helpful for the readers to understand the demand of using the APIs.</p>
                    </list-item>
                </list>
            </p>
            <p>Are the conclusions about the tool and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>Is the rationale for developing the new software tool clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the software tool technically sound?</p>
            <p>Partly</p>
            <p>Are sufficient details of the code, methods and analysis (if applicable) provided to allow replication of the software development and its use by others?</p>
            <p>Yes</p>
            <p>Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>NA</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
        <sub-article article-type="response" id="comment4058-32325">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>Miller</surname>
                            <given-names>Ryan</given-names>
                        </name>
                        <aff>Maastricht University, The Netherlands</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>11</day>
                    <month>10</month>
                    <year>2018</year>
                </pub-date>
            </front-stub>
            <body>
                <p>
                    <bold>1.&#x00a0; The Open PHACTS API includes the Identifier Mapping Service component which allows use of many identifier schemes, as long as suitable link sets are available (at http://data.openphacts.org/1.5/ims/linksets/). These sets include many of the popular gene, protein, and metabolite identifier:for genes, proteins, and RNAs Ensembl, Entrez Gene, UniProt, and others; for metabolites the ID sources can include HMDB, ChEBI, PubChem, CAS registry numbers, and ChemSpider.</bold>
                </p>
                <p>
                    <bold> </bold>
                </p>
                <p>
                    <bold> 2.&#x00a0;&#x00a0;Retrieving specific gene symbol or compound names aside from the identifier URI, resource, and identifier can be part of a workflow in workflow tools like KNIME or Pipeline Pilot. &#x00a0;We did create a simple workflow to address this. In this example, we use the /pathway/getInteractions API call to return the directed interactions for a pathway and the resulting IDs for the interaction and then returned the more human readable labels for the URIs. &#x00a0;</bold>
                </p>
                <p>
                    <bold> </bold>
                </p>
                <p>
                    <bold> 3.&#x00a0;&#x00a0;Additional example output figures were added to the supplementary materials section to reflect the addition of example query results for the remaining calls.</bold>
                </p>
                <p>
                    <bold> </bold>
                </p>
                <p>
                    <bold> 4.&#x00a0;&#x00a0;We added an Example Workflows section describing two simple workflows. More complex applications and workflows have been recently published for KNIME and Pipeline Pilot, which we added as reference 19. </bold>
                </p>
            </body>
        </sub-article>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report29933">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.14318.r29933</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Luna</surname>
                        <given-names>Augustin</given-names>
                    </name>
                    <xref ref-type="aff" rid="r29933a1">1</xref>
                    <role>Referee</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-5709-371X</uri>
                </contrib>
                <aff id="r29933a1">
                    <label>1</label>Dana-Farber Cancer Institute, Boston, MA, USA</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>24</day>
                <month>1</month>
                <year>2018</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2018 Luna A</copyright-statement>
                <copyright-year>2018</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport29933" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.13197.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve-with-reservations</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>The tool provides additional features to the Open PHACTS platform to simplify the access of interaction information from WikiPathways. Some comments:&#x00a0; 
                <list list-type="bullet">
                    <list-item>
                        <p>The authors go into some detail about the MIM/SBGN representations used by WikiPathways. To my understanding, WikiPathways makes use of the format GPML as a data storage format. Some description of the relationship of GPML and the WPRDF format would be nice for readers to understand the data processing involved.&#x00a0;</p>
                    </list-item>
                    <list-item>
                        <p>Looking at the code repository, the API interface seems to be built using Swagger. Is there the plan to provide supported client packages to access the API from various programming languages? Are users encouraged to produce their own using the swagger-codegen (
                            <ext-link ext-link-type="uri" xlink:href="https://github.com/swagger-api/swagger-codegen">https://github.com/swagger-api/swagger-codegen</ext-link>) project? Have the authors had any experience with these auto-generated packages in the context of their API?&#x00a0;</p>
                    </list-item>
                    <list-item>
                        <p>The sentence "However, the new methods also support interactions with multiple sources and targets.", are these the methods that are elsewhere described as not implemented currently?</p>
                    </list-item>
                    <list-item>
                        <p>What entity IDs are acceptable? The examples show ENSEMBL is this the only acceptable ID source? Does the documentation provide any examples for ID conversion from much more common gene symbols, for example?</p>
                    </list-item>
                    <list-item>
                        <p>I assume that when "up" or "down" interactions are not specified for return then both are returned is this correct?&#x00a0;</p>
                    </list-item>
                    <list-item>
                        <p>Are the example interactions (i.e. inhibition, stimulation, conversion) the only ones available in the API? If not, is there a listing of the interaction types with description of the interaction type.&#x00a0;</p>
                    </list-item>
                    <list-item>
                        <p>It would be more clear to just state the call function name rather than "the first and third calls" and "the api call" in the example queries section.&#x00a0;</p>
                    </list-item>
                    <list-item>
                        <p>Additional examples of the result output for all described function calls would be helpful for the described API calls.&#x00a0;</p>
                    </list-item>
                    <list-item>
                        <p>Additional examples that highlight the integrative nature of Open PHACTS would be nice. For example, to show how results of the currently described API calls can paired the other data available, such as the CHEBI data from the platform.</p>
                    </list-item>
                </list>
            </p>
            <p>Are the conclusions about the tool and its performance adequately supported by the findings presented in the article?</p>
            <p>Yes</p>
            <p>Is the rationale for developing the new software tool clearly explained?</p>
            <p>Yes</p>
            <p>Is the description of the software tool technically sound?</p>
            <p>Partly</p>
            <p>Are sufficient details of the code, methods and analysis (if applicable) provided to allow replication of the software development and its use by others?</p>
            <p>Yes</p>
            <p>Is sufficient information provided to allow interpretation of the expected output datasets and any results generated using the tool?</p>
            <p>Partly</p>
            <p>Reviewer Expertise:</p>
            <p>NA</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard, however I have significant reservations, as outlined above.</p>
        </body>
        <sub-article article-type="response" id="comment4059-29933">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>Miller</surname>
                            <given-names>Ryan</given-names>
                        </name>
                        <aff>Maastricht University, The Netherlands</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>11</day>
                    <month>10</month>
                    <year>2018</year>
                </pub-date>
            </front-stub>
            <body>
                <p>
                    <list list-type="order">
                        <list-item>
                            <p>
                                <bold>WikiPathways is represented using GPML (Graphical Pathway Markup Language), which is a modified XML format. &#x00a0;The WikiPathways RDF is divided into two divisions, the GPML and the WPRDF. The GPML side is the portion that is responsible for the drawing and graphical elements. &#x00a0;The WPRDF side is there to describe the semantic elements of the RDF.&#x00a0;&#x00a0;We have updated the Methods section and clarified this in the first &#x201c;Implementation&#x201d; paragraph.</bold>
                            </p>
                        </list-item>
                        <list-item>
                            <p>
                                <bold>The API is REST-like and dedicated clients are not required. However, a few client libraries are already available for various languages and platforms: JavaScript (ops.js), Java (ops4j), ropenphacts, and KNIME nodes. Personal experience with auto-generated packages has been negative, but based on code generation in general, not the Open PHACTS API.&#x00a0;&#x00a0;Supported libraries are referenced in the summary sections along with the workflow environments.</bold>
                            </p>
                        </list-item>
                        <list-item>
                            <p>
                                <bold>We intended to clarify that this simple example referred to single-source, single-target interactions, but that the framework also supports interactions with more than one source and/or target. Such complex interactions occur frequently. </bold>
                                <bold>The&#x00a0;last sentence of the third paragraph under Methods: Implementation has been updated to make this more clear.</bold>
                            </p>
                        </list-item>
                        <list-item>
                            <p>
                                <bold>The Open PHACTS API includes the Identifier Mapping Service component which allows use of many identifier schemes, as long as suitable link sets are available (at http://data.openphacts.org/1.5/ims/linksets/). These sets include many of the popular gene, protein, and metabolite identifier:for genes, proteins, and RNAs Ensembl, Entrez Gene, UniProt, and others; for metabolites the ID sources can include HMDB, ChEBI, PubChem, CAS registry numbers, and ChemSpider. The caption of Figure 1 has been extended&#x00a0;and a paragraph&#x00a0;added to Operation section to reflect this.</bold>
                            </p>
                        </list-item>
                        <list-item>
                            <p>
                                <bold>Yes, you are correct: if the user does not specify the directions for the interactions, all the immediate interactions are retrieved regardless of their direction. This can be found in the last paragraph of the Methods section and updated here to clarify.</bold>
                            </p>
                        </list-item>
                        <list-item>
                            <p>
                                <bold>Vocabularies.wikipathways.org also identifies catalysis and binding events as well as a more generic directedInteraction in the case where the type of the interaction is not identified. This can be found in the last paragraph of the Methods: Implementation.</bold>
                            </p>
                        </list-item>
                        <list-item>
                            <p>
                                <bold>The text in the under Example Queries section has been updated to use the names of the API calls used.</bold>
                            </p>
                        </list-item>
                        <list-item>
                            <p>
                                <bold>Additional figures that show example outputs for the remaining figures can be found in the supplemental info section.</bold>
                            </p>
                        </list-item>
                        <list-item>
                            <p>
                                <bold>Workflow tools make it possible to take advantage of the integrative nature of the OPDP to make API calls in succession. &#x00a0;With these tools, it is possible to perform a directional query of a target and identify alternative targets that can then be queried against the chemistry calls to identify active compounds for these alternative targets.&#x00a0; An Example Workflows section has been added describing two simple workflows and the code for the workflows can be found in the supplementary information.</bold>
                            </p>
                        </list-item>
                    </list>
                </p>
            </body>
        </sub-article>
    </sub-article>
</article>
