Links to Exploration step
Le document en format XML
<record><TEI><teiHeader><fileDesc><titleStmt><title xml:lang="en">ISA-TAB-Nano: A Specification for Sharing Nanomaterial Research Data in Spreadsheet-based Format</title>
<author><name sortKey="Thomas, Dennis G" sort="Thomas, Dennis G" uniqKey="Thomas D" first="Dennis G" last="Thomas">Dennis G. Thomas</name>
<affiliation><nlm:aff id="I1">Knowledge Discovery and Informatics, Pacific Northwest National Laboratory, Richland, WA 99352, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Gaheen, Sharon" sort="Gaheen, Sharon" uniqKey="Gaheen S" first="Sharon" last="Gaheen">Sharon Gaheen</name>
<affiliation><nlm:aff id="I2">SAIC-Frederick, Inc, Frederick National Laboratory for Cancer Research, Information Systems Program, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Harper, Stacey L" sort="Harper, Stacey L" uniqKey="Harper S" first="Stacey L" last="Harper">Stacey L. Harper</name>
<affiliation><nlm:aff id="I3">Department of Environmental and Molecular Toxicology, School of Chemical, Biological and Environmental Engineering, Oregon State University, Corvallis, OR 97331, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Fritts, Martin" sort="Fritts, Martin" uniqKey="Fritts M" first="Martin" last="Fritts">Martin Fritts</name>
<affiliation><nlm:aff id="I2">SAIC-Frederick, Inc, Frederick National Laboratory for Cancer Research, Information Systems Program, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Klaessig, Fred" sort="Klaessig, Fred" uniqKey="Klaessig F" first="Fred" last="Klaessig">Fred Klaessig</name>
<affiliation><nlm:aff id="I4">Pennsylvania Bio Nano Systems, LLC, Doylestown, PA, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Hahn Dantona, Elizabeth" sort="Hahn Dantona, Elizabeth" uniqKey="Hahn Dantona E" first="Elizabeth" last="Hahn-Dantona">Elizabeth Hahn-Dantona</name>
<affiliation><nlm:aff id="I5">Lockheed Martin, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Paik, David" sort="Paik, David" uniqKey="Paik D" first="David" last="Paik">David Paik</name>
<affiliation><nlm:aff id="I6">Department of Radiology, Stanford University, Stanford, CA 94305, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Pan, Sue" sort="Pan, Sue" uniqKey="Pan S" first="Sue" last="Pan">Sue Pan</name>
<affiliation><nlm:aff id="I2">SAIC-Frederick, Inc, Frederick National Laboratory for Cancer Research, Information Systems Program, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Stafford, Grace A" sort="Stafford, Grace A" uniqKey="Stafford G" first="Grace A" last="Stafford">Grace A. Stafford</name>
<affiliation><nlm:aff id="I7">The Jackson Laboratory, Bar Harbor, Maine 04609, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Freund, Elaine T" sort="Freund, Elaine T" uniqKey="Freund E" first="Elaine T" last="Freund">Elaine T. Freund</name>
<affiliation><nlm:aff id="I8">3rd Millennium, Inc, North Smithfield, RI 02896, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Klemm, Juli D" sort="Klemm, Juli D" uniqKey="Klemm J" first="Juli D" last="Klemm">Juli D. Klemm</name>
<affiliation><nlm:aff id="I9">Center for Biomedical Informatics and Information Technology, National Cancer Institute, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Baker, Nathan A" sort="Baker, Nathan A" uniqKey="Baker N" first="Nathan A" last="Baker">Nathan A. Baker</name>
<affiliation><nlm:aff id="I10">Knowledge Discovery and Informatics, Pacific Northwest National Laboratory, PO Box 999, MSID K7-28, Richland, WA 99352, USA</nlm:aff>
</affiliation>
</author>
</titleStmt>
<publicationStmt><idno type="wicri:source">PMC</idno>
<idno type="pmid">23311978</idno>
<idno type="pmc">3598649</idno>
<idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC3598649</idno>
<idno type="RBID">PMC:3598649</idno>
<idno type="doi">10.1186/1472-6750-13-2</idno>
<date when="2013">2013</date>
<idno type="wicri:Area/Pmc/Corpus">000261</idno>
</publicationStmt>
<sourceDesc><biblStruct><analytic><title xml:lang="en" level="a" type="main">ISA-TAB-Nano: A Specification for Sharing Nanomaterial Research Data in Spreadsheet-based Format</title>
<author><name sortKey="Thomas, Dennis G" sort="Thomas, Dennis G" uniqKey="Thomas D" first="Dennis G" last="Thomas">Dennis G. Thomas</name>
<affiliation><nlm:aff id="I1">Knowledge Discovery and Informatics, Pacific Northwest National Laboratory, Richland, WA 99352, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Gaheen, Sharon" sort="Gaheen, Sharon" uniqKey="Gaheen S" first="Sharon" last="Gaheen">Sharon Gaheen</name>
<affiliation><nlm:aff id="I2">SAIC-Frederick, Inc, Frederick National Laboratory for Cancer Research, Information Systems Program, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Harper, Stacey L" sort="Harper, Stacey L" uniqKey="Harper S" first="Stacey L" last="Harper">Stacey L. Harper</name>
<affiliation><nlm:aff id="I3">Department of Environmental and Molecular Toxicology, School of Chemical, Biological and Environmental Engineering, Oregon State University, Corvallis, OR 97331, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Fritts, Martin" sort="Fritts, Martin" uniqKey="Fritts M" first="Martin" last="Fritts">Martin Fritts</name>
<affiliation><nlm:aff id="I2">SAIC-Frederick, Inc, Frederick National Laboratory for Cancer Research, Information Systems Program, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Klaessig, Fred" sort="Klaessig, Fred" uniqKey="Klaessig F" first="Fred" last="Klaessig">Fred Klaessig</name>
<affiliation><nlm:aff id="I4">Pennsylvania Bio Nano Systems, LLC, Doylestown, PA, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Hahn Dantona, Elizabeth" sort="Hahn Dantona, Elizabeth" uniqKey="Hahn Dantona E" first="Elizabeth" last="Hahn-Dantona">Elizabeth Hahn-Dantona</name>
<affiliation><nlm:aff id="I5">Lockheed Martin, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Paik, David" sort="Paik, David" uniqKey="Paik D" first="David" last="Paik">David Paik</name>
<affiliation><nlm:aff id="I6">Department of Radiology, Stanford University, Stanford, CA 94305, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Pan, Sue" sort="Pan, Sue" uniqKey="Pan S" first="Sue" last="Pan">Sue Pan</name>
<affiliation><nlm:aff id="I2">SAIC-Frederick, Inc, Frederick National Laboratory for Cancer Research, Information Systems Program, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Stafford, Grace A" sort="Stafford, Grace A" uniqKey="Stafford G" first="Grace A" last="Stafford">Grace A. Stafford</name>
<affiliation><nlm:aff id="I7">The Jackson Laboratory, Bar Harbor, Maine 04609, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Freund, Elaine T" sort="Freund, Elaine T" uniqKey="Freund E" first="Elaine T" last="Freund">Elaine T. Freund</name>
<affiliation><nlm:aff id="I8">3rd Millennium, Inc, North Smithfield, RI 02896, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Klemm, Juli D" sort="Klemm, Juli D" uniqKey="Klemm J" first="Juli D" last="Klemm">Juli D. Klemm</name>
<affiliation><nlm:aff id="I9">Center for Biomedical Informatics and Information Technology, National Cancer Institute, Rockville, MD 20852, USA</nlm:aff>
</affiliation>
</author>
<author><name sortKey="Baker, Nathan A" sort="Baker, Nathan A" uniqKey="Baker N" first="Nathan A" last="Baker">Nathan A. Baker</name>
<affiliation><nlm:aff id="I10">Knowledge Discovery and Informatics, Pacific Northwest National Laboratory, PO Box 999, MSID K7-28, Richland, WA 99352, USA</nlm:aff>
</affiliation>
</author>
</analytic>
<series><title level="j">BMC Biotechnology</title>
<idno type="eISSN">1472-6750</idno>
<imprint><date when="2013">2013</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc><textClass></textClass>
</profileDesc>
</teiHeader>
<front><div type="abstract" xml:lang="en"><sec><title>Background and motivation</title>
<p>The high-throughput genomics communities have been successfully using standardized spreadsheet-based formats to capture and share data within labs and among public repositories. The nanomedicine community has yet to adopt similar standards to share the diverse and multi-dimensional types of data (including metadata) pertaining to the description and characterization of nanomaterials. Owing to the lack of standardization in representing and sharing nanomaterial data, most of the data currently shared via publications and data resources are incomplete, poorly-integrated, and not suitable for meaningful interpretation and re-use of the data. Specifically, in its current state, data cannot be effectively utilized for the development of predictive models that will inform the rational design of nanomaterials.</p>
</sec>
<sec><title>Results</title>
<p>We have developed a specification called ISA-TAB-Nano, which comprises four spreadsheet-based file formats for representing and integrating various types of nanomaterial data. Three file formats (Investigation, Study, and Assay files) have been adapted from the established ISA-TAB specification; while the Material file format was developed <italic>de novo</italic>
to more readily describe the complexity of nanomaterials and associated small molecules. In this paper, we have discussed the main features of each file format and how to use them for sharing nanomaterial descriptions and assay metadata.</p>
</sec>
<sec><title>Conclusion</title>
<p>The ISA-TAB-Nano file formats provide a general and flexible framework to record and integrate nanomaterial descriptions, assay data (metadata and endpoint measurements) and protocol information. Like ISA-TAB, ISA-TAB-Nano supports the use of ontology terms to promote standardized descriptions and to facilitate search and integration of the data. The ISA-TAB-Nano specification has been submitted as an ASTM work item to obtain community feedback and to provide a nanotechnology data-sharing standard for public development and adoption.</p>
</sec>
</div>
</front>
<back><div1 type="bibliography"><listBibl><biblStruct><analytic><author><name sortKey="Roco, Mc" uniqKey="Roco M">MC Roco</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Currall, Sc" uniqKey="Currall S">SC Currall</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="De La Iglesia, D" uniqKey="De La Iglesia D">D de la Iglesia</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Thomas, Dg" uniqKey="Thomas D">DG Thomas</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Collins, F" uniqKey="Collins F">F Collins</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Collins, Fs" uniqKey="Collins F">FS Collins</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Poschet, J" uniqKey="Poschet J">J Poschet</name>
</author>
<author><name sortKey="Shalley, E" uniqKey="Shalley E">E Shalley</name>
</author>
<author><name sortKey="Speakman, J" uniqKey="Speakman J">J Speakman</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Hesse, Bw" uniqKey="Hesse B">BW Hesse</name>
</author>
<author><name sortKey="Croyle, Rt" uniqKey="Croyle R">RT Croyle</name>
</author>
<author><name sortKey="Buetow, Kh" uniqKey="Buetow K">KH Buetow</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Payne, Pro" uniqKey="Payne P">PRO Payne</name>
</author>
<author><name sortKey="Embi, Pj" uniqKey="Embi P">PJ Embi</name>
</author>
<author><name sortKey="Niland, J" uniqKey="Niland J">J Niland</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Boyd, Lb" uniqKey="Boyd L">LB Boyd</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Hucka, M" uniqKey="Hucka M">M Hucka</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Demir, E" uniqKey="Demir E">E Demir</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Spellman, Pt" uniqKey="Spellman P">PT Spellman</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Rayner, Tf" uniqKey="Rayner T">TF Rayner</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Sansone, S A" uniqKey="Sansone S">S-A Sansone</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Rocca Serra, P" uniqKey="Rocca Serra P">P Rocca-Serra</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Sansone, S A" uniqKey="Sansone S">S-A Sansone</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Brazma, A" uniqKey="Brazma A">A Brazma</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Parkinson, H" uniqKey="Parkinson H">H Parkinson</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Hubble, J" uniqKey="Hubble J">J Hubble</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Reich, M" uniqKey="Reich M">M Reich</name>
</author>
<author><name sortKey="Reich, M" uniqKey="Reich M">M Reich</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Gentleman, Rc" uniqKey="Gentleman R">RC Gentleman</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Roebben, G" uniqKey="Roebben G">G Roebben</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Shick, L" uniqKey="Shick L">L Shick</name>
</author>
</analytic>
</biblStruct>
<biblStruct><analytic><author><name sortKey="Thomas, Dg" uniqKey="Thomas D">DG Thomas</name>
</author>
<author><name sortKey="Pappu, Rv" uniqKey="Pappu R">RV Pappu</name>
</author>
<author><name sortKey="Baker, Na" uniqKey="Baker N">NA Baker</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Thomas, Dg" uniqKey="Thomas D">DG Thomas</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="De Matos, P" uniqKey="De Matos P">P de Matos</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct><analytic><author><name sortKey="Sioutos, N" uniqKey="Sioutos N">N Sioutos</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
</listBibl>
</div1>
</back>
</TEI>
<pmc article-type="other" xml:lang="en"><pmc-dir>properties open_access</pmc-dir>
<front><journal-meta><journal-id journal-id-type="nlm-ta">BMC Biotechnol</journal-id>
<journal-id journal-id-type="iso-abbrev">BMC Biotechnol</journal-id>
<journal-title-group><journal-title>BMC Biotechnology</journal-title>
</journal-title-group>
<issn pub-type="epub">1472-6750</issn>
<publisher><publisher-name>BioMed Central</publisher-name>
</publisher>
</journal-meta>
<article-meta><article-id pub-id-type="pmid">23311978</article-id>
<article-id pub-id-type="pmc">3598649</article-id>
<article-id pub-id-type="publisher-id">1472-6750-13-2</article-id>
<article-id pub-id-type="doi">10.1186/1472-6750-13-2</article-id>
<article-categories><subj-group subj-group-type="heading"><subject>Correspondence</subject>
</subj-group>
</article-categories>
<title-group><article-title>ISA-TAB-Nano: A Specification for Sharing Nanomaterial Research Data in Spreadsheet-based Format</article-title>
</title-group>
<contrib-group><contrib contrib-type="author" id="A1"><name><surname>Thomas</surname>
<given-names>Dennis G</given-names>
</name>
<xref ref-type="aff" rid="I1">1</xref>
<email>dennis.thomas@pnnl.gov</email>
</contrib>
<contrib contrib-type="author" id="A2"><name><surname>Gaheen</surname>
<given-names>Sharon</given-names>
</name>
<xref ref-type="aff" rid="I2">2</xref>
<email>gaheens@mail.nih.gov</email>
</contrib>
<contrib contrib-type="author" id="A3"><name><surname>Harper</surname>
<given-names>Stacey L</given-names>
</name>
<xref ref-type="aff" rid="I3">3</xref>
<email>stacey.harper@oregonstate.edu</email>
</contrib>
<contrib contrib-type="author" id="A4"><name><surname>Fritts</surname>
<given-names>Martin</given-names>
</name>
<xref ref-type="aff" rid="I2">2</xref>
<email>martin.fritts@nist.gov</email>
</contrib>
<contrib contrib-type="author" id="A5"><name><surname>Klaessig</surname>
<given-names>Fred</given-names>
</name>
<xref ref-type="aff" rid="I4">4</xref>
<email>fred.klaessig@verizon.net</email>
</contrib>
<contrib contrib-type="author" id="A6"><name><surname>Hahn-Dantona</surname>
<given-names>Elizabeth</given-names>
</name>
<xref ref-type="aff" rid="I5">5</xref>
<email>hahndane@mail.nih.gov</email>
</contrib>
<contrib contrib-type="author" id="A7"><name><surname>Paik</surname>
<given-names>David</given-names>
</name>
<xref ref-type="aff" rid="I6">6</xref>
<email>david.paik@stanford.edu</email>
</contrib>
<contrib contrib-type="author" id="A8"><name><surname>Pan</surname>
<given-names>Sue</given-names>
</name>
<xref ref-type="aff" rid="I2">2</xref>
<email>pansu@mail.nih.gov</email>
</contrib>
<contrib contrib-type="author" id="A9"><name><surname>Stafford</surname>
<given-names>Grace A</given-names>
</name>
<xref ref-type="aff" rid="I7">7</xref>
<email>grace.stafford@jax.org</email>
</contrib>
<contrib contrib-type="author" id="A10"><name><surname>Freund</surname>
<given-names>Elaine T</given-names>
</name>
<xref ref-type="aff" rid="I8">8</xref>
<email>elainefreund@yahoo.com</email>
</contrib>
<contrib contrib-type="author" id="A11"><name><surname>Klemm</surname>
<given-names>Juli D</given-names>
</name>
<xref ref-type="aff" rid="I9">9</xref>
<email>klemmj@mail.nih.gov</email>
</contrib>
<contrib contrib-type="author" corresp="yes" id="A12"><name><surname>Baker</surname>
<given-names>Nathan A</given-names>
</name>
<xref ref-type="aff" rid="I10">10</xref>
<email>nathan.baker@pnnl.gov</email>
</contrib>
</contrib-group>
<aff id="I1"><label>1</label>
Knowledge Discovery and Informatics, Pacific Northwest National Laboratory, Richland, WA 99352, USA</aff>
<aff id="I2"><label>2</label>
SAIC-Frederick, Inc, Frederick National Laboratory for Cancer Research, Information Systems Program, Rockville, MD 20852, USA</aff>
<aff id="I3"><label>3</label>
Department of Environmental and Molecular Toxicology, School of Chemical, Biological and Environmental Engineering, Oregon State University, Corvallis, OR 97331, USA</aff>
<aff id="I4"><label>4</label>
Pennsylvania Bio Nano Systems, LLC, Doylestown, PA, USA</aff>
<aff id="I5"><label>5</label>
Lockheed Martin, Rockville, MD 20852, USA</aff>
<aff id="I6"><label>6</label>
Department of Radiology, Stanford University, Stanford, CA 94305, USA</aff>
<aff id="I7"><label>7</label>
The Jackson Laboratory, Bar Harbor, Maine 04609, USA</aff>
<aff id="I8"><label>8</label>
3rd Millennium, Inc, North Smithfield, RI 02896, USA</aff>
<aff id="I9"><label>9</label>
Center for Biomedical Informatics and Information Technology, National Cancer Institute, Rockville, MD 20852, USA</aff>
<aff id="I10"><label>10</label>
Knowledge Discovery and Informatics, Pacific Northwest National Laboratory, PO Box 999, MSID K7-28, Richland, WA 99352, USA</aff>
<pub-date pub-type="collection"><year>2013</year>
</pub-date>
<pub-date pub-type="epub"><day>14</day>
<month>1</month>
<year>2013</year>
</pub-date>
<volume>13</volume>
<fpage>2</fpage>
<lpage>2</lpage>
<history><date date-type="received"><day>12</day>
<month>4</month>
<year>2012</year>
</date>
<date date-type="accepted"><day>11</day>
<month>12</month>
<year>2012</year>
</date>
</history>
<permissions><copyright-statement>Copyright ©2013 Thomas et al; licensee BioMed Central Ltd.</copyright-statement>
<copyright-year>2013</copyright-year>
<copyright-holder>Thomas et al; licensee BioMed Central Ltd.</copyright-holder>
<license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by/2.0"><license-p>This is an Open Access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/2.0">http://creativecommons.org/licenses/by/2.0</ext-link>
), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<self-uri xlink:href="http://www.biomedcentral.com/1472-6750/13/2"></self-uri>
<abstract><sec><title>Background and motivation</title>
<p>The high-throughput genomics communities have been successfully using standardized spreadsheet-based formats to capture and share data within labs and among public repositories. The nanomedicine community has yet to adopt similar standards to share the diverse and multi-dimensional types of data (including metadata) pertaining to the description and characterization of nanomaterials. Owing to the lack of standardization in representing and sharing nanomaterial data, most of the data currently shared via publications and data resources are incomplete, poorly-integrated, and not suitable for meaningful interpretation and re-use of the data. Specifically, in its current state, data cannot be effectively utilized for the development of predictive models that will inform the rational design of nanomaterials.</p>
</sec>
<sec><title>Results</title>
<p>We have developed a specification called ISA-TAB-Nano, which comprises four spreadsheet-based file formats for representing and integrating various types of nanomaterial data. Three file formats (Investigation, Study, and Assay files) have been adapted from the established ISA-TAB specification; while the Material file format was developed <italic>de novo</italic>
to more readily describe the complexity of nanomaterials and associated small molecules. In this paper, we have discussed the main features of each file format and how to use them for sharing nanomaterial descriptions and assay metadata.</p>
</sec>
<sec><title>Conclusion</title>
<p>The ISA-TAB-Nano file formats provide a general and flexible framework to record and integrate nanomaterial descriptions, assay data (metadata and endpoint measurements) and protocol information. Like ISA-TAB, ISA-TAB-Nano supports the use of ontology terms to promote standardized descriptions and to facilitate search and integration of the data. The ISA-TAB-Nano specification has been submitted as an ASTM work item to obtain community feedback and to provide a nanotechnology data-sharing standard for public development and adoption.</p>
</sec>
</abstract>
</article-meta>
</front>
<body><sec><title>Introduction</title>
<p>As we enter the National Nanotechnology Initiative’s second decade [<xref ref-type="bibr" rid="B1">1</xref>
], the early concerns regarding rapid product development without extensive regulatory review have shifted to today’s modest commercialization rate and pursuit of plausible risk assessments. Responsible development of nanotechnology will be influenced strongly by the public’s perception of both promise and risk coupled with the expectation that there are responsible parties addressing any remaining uncertainty [<xref ref-type="bibr" rid="B2">2</xref>
,<xref ref-type="bibr" rid="B3">3</xref>
]. Meeting this expectation requires effective multidisciplinary communication that often involves the exchange of complex datasets. The responsible development of nanotechnology products will be empirically-driven, grounded on effective informatics [<xref ref-type="bibr" rid="B4">4</xref>
] for a variety of purposes; e.g., discussing ecotoxicity data with a regulator or modeling environmental fate for the purpose of setting appropriate disposal instructions or regulating the design of nanoparticles for an effective biological application.</p>
<p>A cross-cutting need in the nanotechnology community is the development of standards to support both meaningful data submission to public repositories and information exchange among investigators [<xref ref-type="bibr" rid="B5">5</xref>
]. In order to move toward the rational design of nanomaterials for biomedical and other applications, it is critical to recognize and exploit the nanomaterial physicochemical properties that drive biological behavior. Data mining and computer simulation are essential for deriving this information; however, the datasets needed to support such modeling and computational studies are sparse and stored across a variety of nanotechnology repositories and resources. The lack of standardized data formats and the non-uniformity of information reported have proven to be significant barriers to effective and meaningful data sharing and re-use. We have addressed this problem by developing a spreadsheet-based data exchange format specification, called ISA-TAB-Nano, which provides a general framework for representing and integrating diverse types of data related to the description and characterization of nanomaterials. As noted by Dr. Francis Collins, open access to technologies, tools, and databases has become increasingly critical for accelerating biological discovery [<xref ref-type="bibr" rid="B6">6</xref>
,<xref ref-type="bibr" rid="B7">7</xref>
]. Open access databases necessitate open standards for representing the information to be exchanged. A number of nanomaterials resources are now becoming available leading to an opportune moment to introduce an open standard for nanomedicine. In this paper, we discuss the main features of ISA-TAB-Nano file formats and how they can be used to represent and share nanomaterial data.</p>
<sec><title>Data exchange formats and their uses</title>
<p>The ability to share data meaningfully among investigators from separate biomedical disciplines is a challenge [<xref ref-type="bibr" rid="B8">8</xref>
-<xref ref-type="bibr" rid="B11">11</xref>
]. In order to understand and use experimental data generated by another investigator, one must have sufficiently detailed information about how the data were generated, using mutually understood terminology. These requirements can be facilitated through a shared data exchange format that captures information between two laboratories or between investigators and public repositories. Many XML-based and spreadsheet-based data exchange formats have been successfully developed and adopted across the biomedical community; examples include the SBML – Systems Biology Markup Language [<xref ref-type="bibr" rid="B12">12</xref>
]; BioPAX – Biological Pathway Exchange [<xref ref-type="bibr" rid="B13">13</xref>
]; MAGE-ML – Microarray and Gene Expression Markup Language [<xref ref-type="bibr" rid="B14">14</xref>
]; MAGE-TAB – Microarray Gene Expression Tabular [<xref ref-type="bibr" rid="B15">15</xref>
]; and ISA-TAB – Investigation/Study/Assay Tabular [<xref ref-type="bibr" rid="B16">16</xref>
-<xref ref-type="bibr" rid="B18">18</xref>
].</p>
<p>Compared to XML-based formats, spreadsheet-based formats offer the advantage that they can be created, viewed, and edited by the investigator using software (e.g., Excel) that is broadly available and familiar to most researchers. The most widely adopted spreadsheet-based formats of biological data are MAGE-TAB [<xref ref-type="bibr" rid="B15">15</xref>
] and ISA-TAB [<xref ref-type="bibr" rid="B16">16</xref>
-<xref ref-type="bibr" rid="B18">18</xref>
]. MAGE-TAB supports the capture and exchange of microarray data in accordance with the minimal information standards adopted in this field [<xref ref-type="bibr" rid="B19">19</xref>
]. It was developed in response to the need for a format that could be created and used by laboratories lacking the dedicated bioinformatics personnel necessary to support its predecessor XML-based MAGE-ML format. The ease of use of MAGE-TAB has facilitated its broad adoption across the microarray community and it is supported by several public repositories (ArrayExpress [<xref ref-type="bibr" rid="B20">20</xref>
], caArray [<xref ref-type="bibr" rid="B21">21</xref>
], the Stanford Microarray Database [<xref ref-type="bibr" rid="B22">22</xref>
]) and analysis tools (e.g., GenePattern [<xref ref-type="bibr" rid="B23">23</xref>
], Bioconductor [<xref ref-type="bibr" rid="B24">24</xref>
]). In addition, data from The Cancer Genome Atlas Project (TCGA) are made available in MAGE-TAB format. Based on the wide acceptance of MAGE-TAB, a generalization of this format (ISA-TAB) was developed to support the broader community need for a common format to support the exchange of data about ‘omics studies employing a combination of methodologies (e.g., genomics, transcriptomics, proteomics). Multiple public and private repositories are now ISA-TAB compliant [<xref ref-type="bibr" rid="B25">25</xref>
] and an open-source tool suite has been developed to support the use of this format [<xref ref-type="bibr" rid="B16">16</xref>
-<xref ref-type="bibr" rid="B18">18</xref>
].</p>
</sec>
<sec><title>The need for a data exchange format to share nanomaterial data</title>
<p>Information describing the chemical composition and three-dimensional (3D) structure of nanomaterials is often represented in an unstructured fashion, with no standardized way to associate this information with the assay data from characterization studies. Nanomaterials are diverse: chemical composition, size, geometry, morphology and surface chemistry all play important roles in determining the biological properties of resulting nanomaterials. Complex nanomaterials are often multi-component systems formulated with small molecules for specific biomedical applications such as drug delivery, imaging, and detection of diseases. Such complex formulations make the representation of exact chemical composition, physical structure, and properties very challenging and very necessary.</p>
<p>Nanomaterial analysis requires knowledge of the characterization experiment details so that the results can be accurately and interpreted. Nanomaterial interactions with biological systems are complex and, accordingly, associated data are often generated at multiple levels of detail. The properties of nanomaterials are analyzed based on the data available from different characterization studies, such as <italic>in vitro</italic>
and <italic>in vivo</italic>
analysis of biological activities and abiotic studies of physicochemical properties. Each characterization itself involves a wide range of variables using different types of assays, which can also vary depending on the endpoint measured, technology used, and the protocol applied. Furthermore, even minor variations in the chemical composition, assay protocols and conditions, and time point of analysis (the elapsed time since the nanomaterial was synthesized), can give rise to different characterization results. Currently, most of the measurements on nanomaterial properties depend on non-standardized protocols and diverse instrumentation technology types. Experimental results are dependent on protocol details that are not consistently captured or reported [<xref ref-type="bibr" rid="B26">26</xref>
]. For example, measurements of certain parameters, such as size, are dependent on the instrumentation and the sample preparation method; this information needs to be captured in the form of metadata to fully interpret such measurements.</p>
</sec>
<sec><title>ISA-TAB-Nano specification</title>
<p>To address the challenges associated with the sharing and re-use of nanomaterial data, we have developed the ISA-TAB-Nano specification, a standard format for representing and sharing data pertaining to the description and characterization of nanomaterials. ISA-TAB-Nano is intended to facilitate the submission and exchange of assay metadata and nanomaterial descriptions, along with other information (raw/derived data, image data, protocol information), among individual researchers and to/from nanotechnology online resources. We expect that ISA-TAB-Nano will provide organizations with a standard approach to representing nanomaterial data that will enable researchers to share nanomaterial information effectively and to make cross-material comparisons.</p>
</sec>
</sec>
<sec sec-type="methods"><title>Methods</title>
<p>In 2008, the Nanotechnology Working Group (Nano WG) was established as part of National Cancer Institute (NCI) cancer Biomedical Informatics Grid (caBIG<sup>®</sup>
) program, to support the informatics needs of nanomedicine researchers. Today, the group has over 20 active participants who represent a broad range of expertise and come from academic, industrial, government agency and other institutions. Beginning in March 2010, a sub-group of the Nano WG began developing a specification to facilitate the exchange of nanomaterial data amongst research labs and with public repositories of nanoparticle information. An important goal of this effort from the outset was to use and extend concepts from the caBIG<sup>®</sup>
Life Sciences Domain Analysis Model [<xref ref-type="bibr" rid="B27">27</xref>
] while using the NanoParticle Ontology [<xref ref-type="bibr" rid="B28">28</xref>
] and other ontologies as terminology sources. Recognizing that nanoparticle assays have many of the same challenges as microarray assays, the Nano WG looked to the microarray community for lessons learned. The ISA-TAB standard [<xref ref-type="bibr" rid="B16">16</xref>
,<xref ref-type="bibr" rid="B18">18</xref>
] forms the basis for our ISA-TAB-Nano format because of its flexibility in supporting several different types of assays of interest including physicochemical<italic>, in vitro</italic>
, and <italic>in vivo</italic>
assays.</p>
<p>The ISA-TAB-Nano file formats were evaluated using several nanomaterial datasets from the cancer Nanotechnology Laboratory Portal (caNanoLab) [<xref ref-type="bibr" rid="B29">29</xref>
] and individual researchers with applications ranging from biomedicine to nanotoxicology. This diversity allowed for format refinement and enabled support for a broad range of interests. Test case studies were conducted and feedback was provided to the ISA-TAB-Nano development team. Example datasets are available from the ISA-TAB-Nano website at <ext-link ext-link-type="uri" xlink:href="https://wiki.nci.nih.gov/x/HgiG">https://wiki.nci.nih.gov/x/HgiG</ext-link>
.</p>
<sec><title>Basis of ISA-TAB-Nano</title>
<sec><title>ISA-TAB</title>
<p>The ISA-TAB-Nano specification is based on the ISA-TAB specification [<xref ref-type="bibr" rid="B16">16</xref>
-<xref ref-type="bibr" rid="B18">18</xref>
,<xref ref-type="bibr" rid="B25">25</xref>
]. ISA-TAB defines three file formats for sharing the metadata associated with ‘omics (e.g., proteomics, genomics, metabolomics, and transcriptomics) – based experiments. The three files are called Investigation file, Study file, and Assay file. Non-standard (user-defined) file formats such as image files, spreadsheet files containing raw/derived data, and protocol documents, can also be referenced in appropriate fields within the Investigation, Study, and Assay files. By providing a standard format for representing the metadata related to each ‘omics experiment, the ISA-TAB file formats facilitate the integration and sharing of ‘omics data in a meaningful and standardized way.</p>
<p>The ISA-TAB Study file is used to record information about the source and characteristics of a subject (sample) under study as well as the different treatment protocols that are applied to prepare the samples for the analysis (assay). The subject under study could be an organism, a sample taken out of the organism, or any other sample. The Assay files are used to record the assay metadata along with references to the names (or URIs) of the raw/derived data and image files. In the ISA-TAB framework, the type of assay is determined by the endpoint of measurement and by the technology (technique) used to measure that endpoint. Therefore, a single study (of a given sample) can comprise several types of assays. The Investigation file serves to relate the different types of assays to their corresponding studies. In particular, the Investigation file is used to record reference information about each Study file and Assay file; point of contact; publications; the parameters, instruments, software, and reagents of a protocol; the factors of the study (a factor is defined as any independent variable that is varied in an experiment to investigate its effect on the subject under study) and the terminology sources referred to in the Investigation, Study and Assay files.</p>
</sec>
</sec>
<sec><title>Biospecimens versus material samples</title>
<p>An important extension to ISA-TAB required to support nanomaterials came from the need to distinguish samples derived from biological sources (e.g., from cell lines, tissues, body fluids, etc.) and samples derived from non-biological sources (e.g., nanoparticle formulations, small molecule drug, etc.). Hence, for the ISA-TAB-Nano specification, we consider a sample derived from biological sources as a <italic>biological specimen</italic>
or <italic>biospecimen material type</italic>
, while referencing samples derived from non-biological sources as <italic>material samples</italic>
.</p>
<p>The ISA-TAB Study file can be used to describe the source and characteristics of biological specimens, however, it is not suitable for describing nanomaterials. In this work, we have designed a “Material” file format for describing nanomaterials. In general, this file format is applicable for describing any material sample, nanoscale or otherwise, as discussed later. Hence, in ISA-TAB-Nano, the concept of a sample (as used in ISA-TAB specification) is extended to distinguish between biological specimens and material samples by incorporating information about the latter into the Material file.</p>
</sec>
<sec><title>Scope of a ISA-TAB-Nano Material file</title>
<p>The Material file is designed to capture information related to the description of nanomaterials. Typically, the description of a nanomaterial is complex and includes different types of information (name, type, characteristics) related to the whole nanomaterial and its individual chemical components. A typical example is that of a nanoparticle formulation [<xref ref-type="bibr" rid="B5">5</xref>
,<xref ref-type="bibr" rid="B28">28</xref>
], which can be generally described as a multi-component system containing chemical components that may be distinguished as nanoparticles, chemical constituents of the nanoparticle, functionalizing agents, and components of the medium in which the nanoparticles may be suspended. These chemical components can be described and identified based on their molecular structure, biochemical role, and function [<xref ref-type="bibr" rid="B28">28</xref>
]. The types of information needed to describe nanoparticles and their formulations include specification of the linkages existing between the different components of the formulation (e.g., encapsulation, entrapment, amide linkages, etc.); the physical state of the formulation (e.g., emulsion, solid, hydrogel, etc.); the properties (physical, chemical, and functional) of each chemical component; the intended functions and applications of the nanoparticle; the nanoparticle design principles (or rationale); and the type of stimulus that may be required for activating a specific function of the nanoparticle (e.g., magnetic field, ultrasound, pH change, etc.) [<xref ref-type="bibr" rid="B28">28</xref>
]. All of these types of information were taken into account when developing the specification for the ISA-TAB-Nano Material file format.</p>
</sec>
</sec>
<sec><title>Results and discussion</title>
<p>The ISA-TAB-Nano specification makes use of the ISA-TAB Investigation, Study, and Assay files to record and share the assay metadata. In addition to sharing the assay metadata, we also want to share the endpoint measurements and description (chemical composition, characteristics) of both nanomaterials and small molecules (e.g., drugs, imaging agents). To accommodate this additional information, we have made extensions to ISA-TAB. In particular, the ISA-TAB Study file is suited for recording the source and characteristics of biological specimens and for specifying any treatments performed on them. However, the Study file is not designed to represent information about the chemical composition and characteristics of <italic>material samples</italic>
(nanomaterials, drugs, imaging agents, and other small molecules). To represent this information, we have introduced a fourth ISA-TAB-Nano file called the Material file. We use the Material file to describe <italic>material samples</italic>
while using the ISA-TAB Study file to describe <italic>biospecimens</italic>
. We have modified the definitions of some of the field names in the ISA-TAB Investigation, Study, and Assay files and added new fields names to expand the scope of information that needs to be shared using the ISA-TAB-Nano specification. Detailed information of the field names and definitions of each file format can be found in Supporting Information. For more detailed information about the structure and contents of the ISA-TAB files, the reader may refer to the ISA-TAB specification [<xref ref-type="bibr" rid="B25">25</xref>
]. The rules for naming the four file formats defined in the ISA-TAB-Nano specification are i_xxxx.txt for the Investigation file, s_xxxx.txt for the Study file, a_xxxx.txt for the Assay file, and m_xxxx.txt for the Material file, where ‘xxxx’ denotes a unique string.</p>
<p>The following sections describe the different components of the ISA-TAB-Nano files. Supporting Information provides additional materials to supplement the manuscript discussion, including a summary of extensions to the ISA-TAB format, the standard specification, and examples.</p>
<sec><title>Types of information shared using ISA-TAB-Nano files</title>
<p>The types of information shared using ISA-TAB-Nano pertain to the material samples, biospecimens, assays, and protocols. As listed in Table <xref ref-type="table" rid="T1">1</xref>
, we use the ISA-TAB-Nano Material file to capture information about material samples and references to the external material data files (e.g., image files, structural data files); the Investigation file to enter reference information about each investigation, study, assay, protocol: the Study file to capture information about biospecimen source and characteristics, names and attributes of protocols used in the preparation of samples analyzed in an assay; and, the Assay file to capture information about measured values of endpoint variables and references to external files (raw/derived data files, image files) related to each analyzed biospecimen or material sample. In the following sections, we explain how to record and share the different types of information in each ISA-TAB-Nano file.</p>
<table-wrap position="float" id="T1"><label>Table 1</label>
<caption><p>Types of information entered in the four ISA-TAB-Nano files</p>
</caption>
<table frame="hsides" rules="groups" border="1"><colgroup><col align="left"></col>
<col align="left"></col>
<col align="left"></col>
</colgroup>
<thead valign="top"><tr><th align="left"><bold>No.</bold>
</th>
<th align="left"><bold>ISA-TAB-Nano file</bold>
</th>
<th align="left"><bold>Types of information entered in each ISA-TAB-Nano file</bold>
</th>
</tr>
</thead>
<tbody valign="top"><tr><td align="left" valign="bottom">1.<hr></hr>
</td>
<td align="left" valign="bottom">Investigation file<hr></hr>
</td>
<td align="left" valign="bottom">Reference information about each investigation, study, assay, protocol, Study file, and Assay file.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">2.<hr></hr>
</td>
<td align="left" valign="bottom">Study file<hr></hr>
</td>
<td align="left" valign="bottom">Names and attributes of protocols used for preparing samples for analysis; source and characteristics of biospecimens.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">3.<hr></hr>
</td>
<td align="left" valign="bottom">Assay file<hr></hr>
</td>
<td align="left" valign="bottom">Values of measured endpoint variables and references to external data files for each analyzed sample.<hr></hr>
</td>
</tr>
<tr><td align="left">4.</td>
<td align="left">Material file</td>
<td align="left">Descriptions of the material sample and its structural parts and chemical components; linkage descriptions between chemical components; reference information about external material data files.</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec><title>Sharing material sample description</title>
<p>In the ISA-TAB-Nano framework, all material samples are viewed as formulations having one or more chemical components (e.g., nanoparticles, small molecules, solvent medium, etc.). The ISA-TAB-Nano material file has been designed for recording descriptions of various types of formulations, ranging from a simple chemical compound to a complex multi-component nanoparticle formulation.</p>
<p>The layout of the ISA-TAB-Nano Material file is same as that of the Study and Assay files, wherein the field names are arranged as columns and material sample information is entered as rows. Columns in the ISA-TAB-Nano Material file provide information on the material and its components, the relationship between materials and components, and any associated data files, as mentioned in Table <xref ref-type="table" rid="T1">1</xref>
.</p>
</sec>
<sec><title>Using the ISA-TAB-Nano Material file to describe a material sample and its components</title>
<p>The Material file is used to describe a material sample and its structural and chemical components. There are different ways to identify the components, depending on how the sample is viewed at its various levels of molecular and structural granularities. Figure <xref ref-type="fig" rid="F1">1</xref>
shows a process flowchart that can be used as a basis for identifying different components of the material sample. Once a component is identified, its description can be entered as a row in the Material file.</p>
<fig id="F1" position="float"><label>Figure 1</label>
<caption><p><bold>Flowchart depicting the ways to identify different components of a material sample, and to guide the creation of rows for each component in the ISA-TAB-Nano Material file.</bold>
(<bold>A</bold>
) The overall ISA-TAB-Nano file creation process which includes (<bold>B</bold>
) the creation of molecular component entries.</p>
</caption>
<graphic xlink:href="1472-6750-13-2-1"></graphic>
</fig>
<p>In Figure <xref ref-type="fig" rid="F2">2</xref>
, we show an example of the ISA-TAB-Nano Material file that contains information about a hypothetical dendrimer sample (LAB-1) and its components. The first row (row 2) of the Material file is used to identify the material sample name (identifier, chemical name), type, synthesis type, design rationale, intended application, and nominal characteristics. Subsequent rows of the Material file are used to identify the different structural parts and chemical components of the sample including their name, type, nominal characteristics, and intended application. While row 2 represents the dendrimer sample LAB-1, rows 3, 4, and 5 represent the components (core molecule, branch, and terminal group) of the dendrimer sample. From the given information, one can understand that the dendrimer sample (LAB-1) is a 4.5 generation dendrimer that has a molecular weight of 27 kilodaltons (kDa). Ontology terms can be identified by the name of the source ontology (defined by <italic>Term Source REF</italic>
labels) and their identification numbers (defined by <italic>Term Accession Number</italic>
labels) used within the ontology. Thus, we use row 2 to describe the material sample as a whole, and subsequent rows to describe each material sample component. If a material sample that is described in a Material file is also a component of another material sample, then the components of the former sample need not be specified in the Material file of the latter sample. To illustrate this scenario, we consider another hypothetical sample called LAB-2 that contains both LAB-1 and an image contrast agent called Magnevist<sup>®</sup>
(LAB-3). Figure <xref ref-type="fig" rid="F3">3</xref>
shows the LAB-2 Material file, where row 2 represents the whole LAB-2 material sample and rows 3 and 4 represent its components (LAB-1 and LAB-3). Note that we did not have to enter information about each component of LAB-1 since that information is already present in the LAB-1 Material file (see Figure <xref ref-type="fig" rid="F2">2</xref>
). The LAB-2 Material file describes the material sample LAB-2 which consists of nanoparticles composed of carboxyl-terminated PAMAM dendrimer complexed with Magnevist<sup>®</sup>
, a small molecule gadolinium-based image contrast agent. The dendrimer is conjugated to the Magnevist<sup>®</sup>
and is intended to be used as a delivery vehicle for image contrast agents like Magnevist<sup>®</sup>
in MRI applications.</p>
<fig id="F2" position="float"><label>Figure 2</label>
<caption><p>Example of an ISA-TAB-Nano Material file with information about a dendrimer nanoparticle sample, identified as LAB-1.</p>
</caption>
<graphic xlink:href="1472-6750-13-2-2"></graphic>
</fig>
<fig id="F3" position="float"><label>Figure 3</label>
<caption><p>Example of an ISA-TAB-Nano Material file with information about a dendrimer-magnevist nanoparticle complex sample, identified as LAB-2.</p>
</caption>
<graphic xlink:href="1472-6750-13-2-3"></graphic>
</fig>
</sec>
<sec><title>Using the ISA-TAB-Nano Material file to describe linkages in a material sample</title>
<p>The ISA-TAB-Nano Material file is used to describe the whole material sample and its components with respect to their name, type, characteristics, synthesis, design rationale, and intended application. In addition, the Material file can be used to identify the chemical components and represent how they are linked or connected to each other with respect to a nanoparticle. Any two chemical components in a typical multi-component nanoparticle formulation can be linked to each other by one of the three types of linkages: encapsulation, entrapment, or covalent linkage [<xref ref-type="bibr" rid="B28">28</xref>
]. We can describe linkages between the different chemical components of a nanoparticle sample as shown in Figure <xref ref-type="fig" rid="F4">4</xref>
. In the figure, one can identify that there is a covalent linkage that exists between the dendrimer and the Magnevist<sup>®</sup>
of LAB-2 sample. The term “covalent linkage” is used here as a generic term. Normally, if the specific type of covalent linkage is known (e.g., amide linkage, disulfide linkage, etc.), then one should use the appropriate term identifying that linkage. The NPO [<xref ref-type="bibr" rid="B28">28</xref>
] provides several terms (their names and definitions) for describing different types of linkages that can be typically found in a nanoparticle sample. Additionally, we have recently developed a simple nomenclature system for describing the specific chemical linkages in nanoparticle formulations [<xref ref-type="bibr" rid="B30">30</xref>
]. It is important to ensure that the names of the two chemical components specified in the <italic>Material Constituent</italic>
field (Figure <xref ref-type="fig" rid="F4">4</xref>
) match their respective names given in the <italic>Material Name</italic>
field.</p>
<fig id="F4" position="float"><label>Figure 4</label>
<caption><p>An example showing the representation of linkages among components of a nanoparticle sample in the ISA-TAB-Nano Material file.</p>
</caption>
<graphic xlink:href="1472-6750-13-2-4"></graphic>
</fig>
</sec>
<sec><title>Using the ISA-TAB-Nano Material file to record information about external files that provide additional information about the material sample</title>
<p>The Material file is also used to record the name or URI of external files that contain additional information about the material sample. Examples include image files displaying the chemical structures of molecules, or documents (e.g., spreadsheet, Word, PDF, etc.) that contain detailed descriptions of the sample. The example given in Figure <xref ref-type="fig" rid="F4">4</xref>
references one file called “magnevist.jpg” that contains an image of the molecular structure of Magnevist<sup>®</sup>
.</p>
<p>In practice, one ISA-TAB-Nano Material file should be created for each material sample in a study. When using the format “m_xxxx.txt” to name the Material files, the string “xxxx” should exactly match the string used in the <italic>Material Source Name</italic>
field of the sample’s Material file. For example, we would name the Material file of samples LAB-1 and LAB-2 as m_LAB-1.txt and m_LAB-2.txt, respectively.</p>
</sec>
<sec><title>Sharing assay information</title>
<p>Different types of assays are performed to measure the physicochemical, <italic>in vitro</italic>
, and <italic>in vivo</italic>
properties of material samples. We can identify the type of each assay based on the measured endpoint, measurand, and technique used. For example, if an assay is related to a size characterization study, the endpoint could be “size” and the technique could be “dynamic light scattering (DLS)”, or “scanning electron microscopy (SEM)”, or other relevant technique. The corresponding assay types are “size by DLS assay”, “size by SEM”, etc. Assays of the same type may be performed using different protocols, by different people, at different dates, and under different experimental conditions. To interpret the characterization results of a material sample meaningfully, we need to have information about the assay type; biospecimen information (if it is a bioassay); protocol descriptions; dates of synthesis and analysis of the material sample; the measured endpoint variables; as well as the protocol variables of the experiment. Based on the ISA-TAB specification, variables that are kept constant in an assay experiment are termed “parameters”, while variables that are changed for studying their effects on the measured endpoint values are termed “study factors”.</p>
</sec>
<sec><title>Representing physiochemical characterization data of material samples using ISA-TAB-Nano files</title>
<p>In a physicochemical characterization study, one measures the properties of a material sample and studies how these properties are affected by the study factors. Typically, one prepares several dilutions of same material sample and may even suspend each sample in different test media to achieve solution conditions suitable for performing a specific assay. Therefore, each analyzed sample may have its own identifier while its (source) material sample to be characterized has a different identifier (the <italic>Material Source Name</italic>
).</p>
<p>Figure <xref ref-type="fig" rid="F5">5</xref>
and Figure <xref ref-type="fig" rid="F6">6</xref>
show an example of how to use the Study and Assay files, respectively, to represent the assay data (metadata, summary data) of each sample analyzed in a size characterization assay using DLS technique. In this example, the goal of the study was to determine the effect of varying temperature and solvent medium on the size of nanoparticles in the two material samples - LAB-1 and LAB-2.</p>
<fig id="F5" position="float"><label>Figure 5</label>
<caption><p>An example showing the layout of the ISA-TAB-Nano Study file.</p>
</caption>
<graphic xlink:href="1472-6750-13-2-5"></graphic>
</fig>
<fig id="F6" position="float"><label>Figure 6</label>
<caption><p>An example showing the layout of the ISA-TAB-Nano Assay file.</p>
</caption>
<graphic xlink:href="1472-6750-13-2-6"></graphic>
</fig>
<sec><title>Study file</title>
<p>In the ISA-TAB Study file, a column <italic>Source Name</italic>
is used to define the source of a biospecimen. ISA-TAB-Nano extends the ISA-TAB Study file by adding a column called <italic>Material Source Name REF</italic>
to refer the source name of the material sample, given in the <italic>Material Source Name</italic>
column of the sample’s Material file. Thus, as shown in Figure <xref ref-type="fig" rid="F5">5</xref>
, the first column of the Study file (<italic>Material Source Name REF</italic>
) represents the identifier of the material sample that is to be characterized. The second column contains the name of the protocol applied to prepare each individual biospecimen or material sample for the analysis. After the protocol column, we create columns to capture the attributes of the protocol including the name of the person who performed the protocol, the date when the protocol was applied, and the values of each parameter in the protocol. After these, we add two more columns to record the sample name (identifier) and its material type.</p>
</sec>
<sec><title>Assay file</title>
<p>The first column of the Assay file is used to enter the biospecimen or material sample names under the header name <italic>Sample Name</italic>
(see Figure <xref ref-type="fig" rid="F6">6</xref>
) – note that these names should match the names entered in the <italic>Sample Name</italic>
column of the Study file. The names of the assay and protocol are entered in the next two columns. As in the Study file, we also create columns to capture the attributes of each protocol, including investigator, date, and parameter values. We also create columns for entering the values of each factor value and measurement value variables, followed by columns to record the URIs or names of associated data files, as shown in Figure <xref ref-type="fig" rid="F6">6</xref>
.</p>
<p>The values for the parameters, factors, and measurements can be qualified by a unit of measurement and a statistical type (if applicable) using column headers <italic>Unit</italic>
and <italic>Statistic</italic>
, respectively, in both the Study as well as in the Assay files (see Figure <xref ref-type="fig" rid="F5">5</xref>
and Figure <xref ref-type="fig" rid="F6">6</xref>
). Note that the <italic>Measurement Value []</italic>
and <italic>Statistic</italic>
columns are newly added by the ISA-TAB-Nano specification. If terms from an ontology are used as valid values in any of the columns of the Study and Assay files, it is necessary to enter the term’s identifier and source ontology name in adjacent columns named as <italic>Term Accession Number</italic>
and <italic>Term Source REF</italic>
, respectively (not shown in the Figure <xref ref-type="fig" rid="F5">5</xref>
and Figure <xref ref-type="fig" rid="F6">6</xref>
). One may choose to enter the factor values either in the Study file and/or in the Assay file, as appropriate to the actual experimental procedure(s). Furthermore, to enter any additional type of information in the Study or Assay file, one may create a column with header name, <italic>Comment []</italic>
, as specified by ISA-TAB.</p>
</sec>
<sec><title>Investigation file</title>
<p>The Investigation file is a reference for the different assays and protocols that have been conducted in a single study. The Investigation file is divided into several sections (listed in Table <xref ref-type="table" rid="T2">2</xref>
), including Study, Study Assays, Study Factors, and Study Protocols. As summarized in Table <xref ref-type="table" rid="T2">2</xref>
, the Study section is used to record information about each study and its Study file (see Figure <xref ref-type="fig" rid="F7">7</xref>
A). The Study Assays section is used to record information about each assay and its assay file, particularly, the assay and technology types, measurement variable names, and the assay file names (see example in Figure <xref ref-type="fig" rid="F7">7</xref>
B). The Study Factors section is used to record the names of factor variables and the factor type, as shown in Figure <xref ref-type="fig" rid="F7">7</xref>
C. The Study Protocols section is used to record information about each protocol, including the name, type, description, URI file references and version of each protocol; as well as names of parameter variables and components (instruments, reagents, and software) of each protocol (an example is given in Figure <xref ref-type="fig" rid="F8">8</xref>
). It should be noted the above information must be recorded in the Investigation file for reference to them in the individual Assay and Study files.</p>
<table-wrap position="float" id="T2"><label>Table 2</label>
<caption><p>Types of information entered in the eleven sections of the ISA-TAB-Nano Investigation file</p>
</caption>
<table frame="hsides" rules="groups" border="1"><colgroup><col align="left"></col>
<col align="left"></col>
<col align="left"></col>
</colgroup>
<thead valign="top"><tr><th align="left"><bold>No.</bold>
</th>
<th align="left"><bold>Sections of Investigation file</bold>
</th>
<th align="left"><bold>Types of information entered in each section</bold>
</th>
</tr>
</thead>
<tbody valign="top"><tr><td align="left" valign="bottom">1.<hr></hr>
</td>
<td align="left" valign="bottom">Ontology Source Reference<hr></hr>
</td>
<td align="left" valign="bottom">Information about the ontologies referenced in the ISA-TAB-Nano files.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">2.<hr></hr>
</td>
<td align="left" valign="bottom">Investigation<hr></hr>
</td>
<td align="left" valign="bottom">Investigation title and description.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">3.<hr></hr>
</td>
<td align="left" valign="bottom">Investigation Contacts<hr></hr>
</td>
<td align="left" valign="bottom">Point(s) of contact for the whole investigation.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">4.<hr></hr>
</td>
<td align="left" valign="bottom">Investigation Publications<hr></hr>
</td>
<td align="left" valign="bottom">References to publications of an investigation.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">5.<hr></hr>
</td>
<td align="left" valign="bottom">Study<hr></hr>
</td>
<td align="left" valign="bottom">Information about each study and its associated Study file.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">6.<hr></hr>
</td>
<td align="left" valign="bottom">Study Design Descriptors<hr></hr>
</td>
<td align="left" valign="bottom">Type of study design.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">7.<hr></hr>
</td>
<td align="left" valign="bottom">Study Contacts<hr></hr>
</td>
<td align="left" valign="bottom">Point(s) of contact for a study.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">8.<hr></hr>
</td>
<td align="left" valign="bottom">Study Publications<hr></hr>
</td>
<td align="left" valign="bottom">References to publications of a study.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">9.<hr></hr>
</td>
<td align="left" valign="bottom">Study Assays<hr></hr>
</td>
<td align="left" valign="bottom">Information about each assay and its associated Assay file.<hr></hr>
</td>
</tr>
<tr><td align="left" valign="bottom">10.<hr></hr>
</td>
<td align="left" valign="bottom">Study Factors<hr></hr>
</td>
<td align="left" valign="bottom">Names of factor variables and types.<hr></hr>
</td>
</tr>
<tr><td align="left">11.</td>
<td align="left">Study Protocols</td>
<td align="left">Information about each protocol.</td>
</tr>
</tbody>
</table>
</table-wrap>
<fig id="F7" position="float"><label>Figure 7</label>
<caption><p>Examples showing how information is represented in the following sections of the Investigation file: (A) Study, (B) Study Assays, and (C) Study Factors.</p>
</caption>
<graphic xlink:href="1472-6750-13-2-7"></graphic>
</fig>
<fig id="F8" position="float"><label>Figure 8</label>
<caption><p>An example showing how information is represented in the Study Protocols section of the Investigation file.</p>
</caption>
<graphic xlink:href="1472-6750-13-2-8"></graphic>
</fig>
<p>Note that the ontologies or controlled vocabularies referenced in any of the ISA-TAB-Nano files must be declared in the Ontology Reference section of the Investigation file (noted in Table <xref ref-type="table" rid="T2">2</xref>
). The Investigation file can also contain information about publications and point of contact associated with an investigation or a specific study within the investigation (also noted in Table <xref ref-type="table" rid="T2">2</xref>
). For more details on the Investigation file, we refer the reader to the ISA-TAB specification [<xref ref-type="bibr" rid="B25">25</xref>
] and ASTM ISA-TAB-Nano specification [<xref ref-type="bibr" rid="B31">31</xref>
].</p>
</sec>
</sec>
<sec><title>Representing material sample <italic>in vitro</italic>
and <italic>in vivo</italic>
characterization data of material samples using ISA-TAB-Nano files</title>
<p>For <italic>in vitro</italic>
and <italic>in vivo</italic>
characterization studies, one is interested in measuring the effects of a material sample on a biological system, such as a cell line or animal model. In these studies, the material sample plays the role of a factor, and the sample analyzed is a biospecimen. The way we enter the <italic>in vitro</italic>
/<italic>in vivo</italic>
characterization data is similar to how we entered the physicochemical characterization data in the Investigation, Study, and Assay files. The only additional information to be entered is the description of the source and characteristics of the biospecimen in the Study file, as illustrated in Figure <xref ref-type="fig" rid="F9">9</xref>
. Note that we use the column <italic>Characteristic []</italic>
to enter the type of the biological source, as specified by ISA-TAB. The material type of the sample is entered as biospecimen in the <italic>Material Type</italic>
column, and the material representing the nanoparticle or other non-biological material is entered in the <italic>Factor Value</italic>
column. Particularly, the non-biological material entered in the <italic>Factor Value</italic>
column should be the same as that entered in the <italic>Material Source Name</italic>
column of the sample’s Material file.</p>
<fig id="F9" position="float"><label>Figure 9</label>
<caption><p><bold>A representative Study file for a hypothetical </bold>
<bold><italic>in vitro </italic>
</bold>
<bold>cytotoxicity characterization study, showing the description of a biological specimen and attributes of the sample preparation protocols.</bold>
Note that the entered information is not from an actual study and is only used for illustration purposes.</p>
</caption>
<graphic xlink:href="1472-6750-13-2-9"></graphic>
</fig>
</sec>
<sec><title>Integrated view of ISA-TAB-Nano files and external referenced documents</title>
<p>ISA-TAB-Nano files support the aggregation of all information pertaining to the description and characterization of material samples. In Figure <xref ref-type="fig" rid="F10">10</xref>
, we show how the ISA-TAB-Nano files and the external files, such as protocol documents, raw data files, derived data files, image files, and material sample description files, can be assembled within the ISA-TAB-Nano framework. The names of all Study and Assay files are recorded in the Investigation file in columns corresponding to the fields <italic>Study File Name</italic>
(Study section) and <italic>Study Assay File Name</italic>
(Study Assays section), respectively. As a result, the Investigation, Study and Assay files are linked. The data in the Study and Assay files for each sample are integrated through the <italic>Sample Name</italic>
fields found in both of the files. This is illustrated in Figure <xref ref-type="fig" rid="F5">5</xref>
and Figure <xref ref-type="fig" rid="F6">6</xref>
, where the sample names in Column A of the assay file (a_LABsizeDLS.xls) are the same as those found in Column P of the study file (s_LABsizeDLS.xls). Thus, the information of each biospecimen or material sample in the Study and Assay files can be linked to each other. If the sample that is analyzed is a material sample, then it is necessary to ensure that the value of <italic>Material Source Name REF</italic>
entered in the Study file matches the string entered in the <italic>Material Source Name</italic>
of its Material file (Figure <xref ref-type="fig" rid="F10">10</xref>
). Similarly, the same string must be used in the <italic>Factor Value</italic>
column of the study file or assay file for material samples that are used as factors in an <italic>in vitro</italic>
or an <italic>in vivo</italic>
study. As shown in Figure <xref ref-type="fig" rid="F10">10</xref>
, the ISA-TAB-Nano files can also be associated with any external files, as long as the URI or the names of these files are referenced in the appropriate fields in the ISA-TAB-Nano files. Specifically, the ISA-TAB-Nano files are associated with protocol documents by referencing the URIs or names of these documents in the <italic>Study Protocol URI</italic>
field of the Investigation file. The external files related to the description of a material sample are associated via the <italic>Material Data File</italic>
field of the material file. Finally, the Assay file associates the raw data, derived data and image files via the column fields, <italic>Raw Data File</italic>
, <italic>Derived Data File</italic>
, and <italic>Image File</italic>
, respectively.</p>
<fig id="F10" position="float"><label>Figure 10</label>
<caption><p>Links (black arrows) between ISA-TAB-Nano files and references (blue arrows) to documents (protocol documents, raw/derived data files, image files, and material description files).</p>
</caption>
<graphic xlink:href="1472-6750-13-2-10"></graphic>
</fig>
</sec>
<sec><title>Validation of ISA-TAB-Nano files</title>
<p>A key feature of ISA-TAB-Nano (and the parent ISA-TAB format) is that it can be readily created and edited with any spreadsheet software, without the need for specialized bioinformatics support. However, this also creates challenges because such software does not enforce validation rules for ISA-TAB-Nano files. One possible solution to this problem is to adapt the suite of open source tools provided by the ISA-TAB community [<xref ref-type="bibr" rid="B16">16</xref>
-<xref ref-type="bibr" rid="B18">18</xref>
], such as: (1) ISACreator, which provides a graphical user interface for entering in data into ISA-TAB files; (2) ISAValidator, which assesses the validity of ISA-TAB files; (3) ISAConverter, which converts an ISA-TAB file to one of several other formats if so desired, (4) ISAConfigurator, which creates the XML files that define specialized versions of ISA-TAB, and (5) bioinvindex, which is a database for storing ISA-TAB files. These tools are part of our future plans to be tested for editing and validating ISA-TAB-Nano files.</p>
<p>XML-based validation is also of interest and would involve developing an ISA-TAB-Nano XML schema based on the ISA-TAB-Nano specification such that any ISA-TAB-Nano XML file converted from the ISA-TAB-Nano files can be formally validated against the XML schema. Having an XML-based validation service would also enable software systems to import and export validated ISA-TAB-Nano files to and from distributed nanotechnology resources.</p>
</sec>
</sec>
<sec sec-type="conclusions"><title>Conclusions</title>
<p>In this paper, we have provided an overview of ISA-TAB-Nano, a spreadsheet-based exchange format for information pertaining to the description and characterization of nanomaterials. The ISA-TAB-Nano specification extends the ISA-TAB specification that was designed for sharing all types of ‘omics data. Specifically, ISA-TAB-Nano leverages the three primary ISA-TAB file formats - Investigation file, the Study file, and the Assay file - to represent the metadata related to the characterization of nanomaterials. To capture the measurement data, ISA-TAB-Nano specifies new fields in the Investigation file and in the Assay file. In addition, ISA-TAB-Nano includes a new file format, the Material file, to capture the description of nanomaterials and chemical substances (drugs, imaging agents, etc.) that are characterized in an assay. The ISA-TAB-Nano specification was recently submitted as an ASTM work item to obtain community feedback and to promote ISA-TAB-Nano as a voluntary consensus standard for the nanotechnology community. Additionally, we hope that the ISA-TAB-Nano standard will be adopted by journals and other organizations to ensure a uniform representation of information that is too often “lost” in a prose Methods section and cannot be easily extracted for re-use.</p>
<p>Many of the ISA-TAB extensions developed for ISA-TAB-Nano could also be used for studies of other types of complex materials or formulations. In particular, the “Material” file addition is likely to be useful outside of the nanotechnology realm for a broader range of samples with complex composition or structural characteristics.</p>
<p>Key to promoting the successful adoption of ISA-TAB-Nano will be the availability of resources to facilitate the creation and validation of these files. Our adherence to the parent ISA-TAB specification will allow the ready adaptation of the ISA Tools [<xref ref-type="bibr" rid="B16">16</xref>
-<xref ref-type="bibr" rid="B18">18</xref>
] to support the extended framework, an anticipated next step for this project. The ability easily select ontology terms when populating the files is critical to the ultimate goal of integrating these data across disparate resources. The ISA-TAB and ISA-TAB-Nano specifications support the use of any ontology or controlled vocabulary; in this domain, preferred ontologies include NanoParticle Ontology (NPO) [<xref ref-type="bibr" rid="B28">28</xref>
], Chemical Entities of Biological Interest (ChEBI) [<xref ref-type="bibr" rid="B32">32</xref>
], Gene Ontology (GO) [<xref ref-type="bibr" rid="B33">33</xref>
], NCI thesaurus (NCIt) [<xref ref-type="bibr" rid="B34">34</xref>
], and Unit Ontology (UO) [<xref ref-type="bibr" rid="B35">35</xref>
]. The Nano WG continues to expand the NanoParticle Ontology (NPO) to support the needs of ISA-TAB-Nano, and is considering various methods and tools for facilitating the use of ontology terms in ISA-TAB-Nano files. (Additional files <xref ref-type="supplementary-material" rid="S1">1</xref>
, <xref ref-type="supplementary-material" rid="S2">2</xref>
and <xref ref-type="supplementary-material" rid="S3">3</xref>
).</p>
</sec>
<sec><title>Competing interests</title>
<p>The authors have no competing interests to declare.</p>
</sec>
<sec><title>Authors’ contributions</title>
<p>All authors contributed to the design and testing of the ISA-TAB-Nano standard. DGT, SG, SLH, JDK, and NAB were primarily responsible for the preparation of the manuscript with contributions and revisions from the other authors. All authors read and approved the final manuscript.</p>
</sec>
<sec sec-type="supplementary-material"><title>Supplementary Material</title>
<supplementary-material content-type="local-data" id="S1"><caption><title>Additional file 1</title>
<p>This Supporting Information provides a summary of ISA-TAB-Nano extensions to the ISA-TAB format, glossaries for the terms used in the ISA-TAB-Nano specification, and an overview of the worked examples and templates provided in the other supporting files.</p>
</caption>
<media xlink:href="1472-6750-13-2-S1.doc" mimetype="application" mime-subtype="msword"><caption><p>Click here for file</p>
</caption>
</media>
</supplementary-material>
<supplementary-material content-type="local-data" id="S2"><caption><title>Additional file 2</title>
<p>This file contains the examples described in Supporting File 1.</p>
</caption>
<media xlink:href="1472-6750-13-2-S2.zip" mimetype="application" mime-subtype="x-zip-compressed"><caption><p>Click here for file</p>
</caption>
</media>
</supplementary-material>
<supplementary-material content-type="local-data" id="S3"><caption><title>Additional file 3</title>
<p>This file contains ISA-TAB-Nano templates for common assays.</p>
</caption>
<media xlink:href="1472-6750-13-2-S3.zip" mimetype="application" mime-subtype="x-zip-compressed"><caption><p>Click here for file</p>
</caption>
</media>
</supplementary-material>
</sec>
</body>
<back><sec><title>Acknowledgments</title>
<p>We would like to thank Susanna-Assunta Sansone and Philippe Rocca-Serra, for taking time to provide their expertise on ISA-TAB during the various stages of ISA-TAB-Nano development. We would also like to thank the anonymous reviewers for their helpful comments and suggestions. N.A.B. and D.G.T. acknowledge support from the NIH NCI caBIG<sup>®</sup>
Working Group, Pacific Northwest National Laboratory HHS sector LDRD funds, as well as NIH grants U54 HG004028 (National Center for Biomedical Ontology), U01 NS073457, and R01 GM069702. S.L.H. would like to acknowledge support from NIEHS Environmental Health Sciences Center P30 ES03850, National Institute of Environmental Health Sciences ES016896-01, and the Air Force Research Laboratory FA8650-05-1-5041 under an agreement with the Oregon Nanoscience and Microtechnologies Institute/Safer Nanomaterials and Nanomanufacturing Initiative. D.P. acknowledges support for funding from Stanford CCNE-TR/CCNE-T (NIH U54 CA119367) and National Center for Biomedical Ontology (NIH U54 CA151459). The views, opinions, and content in this article are those of the authors and do not necessarily represent the views, opinions, or policies of their respective employers or organizations. Mention of company names or products does not constitute endorsement.</p>
</sec>
<ref-list><ref id="B1"><mixed-citation publication-type="journal"><name><surname>Roco</surname>
<given-names>MC</given-names>
</name>
<article-title>Nanotechnology: convergence with modern biology and medicine</article-title>
<source>Curr Opin Biotechnol</source>
<year>2003</year>
<volume>14</volume>
<issue>3</issue>
<fpage>337</fpage>
<lpage>346</lpage>
<pub-id pub-id-type="doi">10.1016/S0958-1669(03)00068-5</pub-id>
<pub-id pub-id-type="pmid">12849790</pub-id>
</mixed-citation>
</ref>
<ref id="B2"><mixed-citation publication-type="book"><collab>PCAST, The President's Council of Advisors on Science and Technology</collab>
<source>The National Nanotechnology Initiative 2010 third assessment along with recommendations of the National Nanotechnology Advisory Panel</source>
<year>2010</year>
<publisher-name>Washington D.C</publisher-name>
</mixed-citation>
</ref>
<ref id="B3"><mixed-citation publication-type="journal"><name><surname>Currall</surname>
<given-names>SC</given-names>
</name>
<etal></etal>
<article-title>What drives public acceptance of nanotechnology?</article-title>
<source>Nat Nanotechnol</source>
<year>2006</year>
<volume>1</volume>
<issue>3</issue>
<fpage>153</fpage>
<lpage>155</lpage>
<pub-id pub-id-type="doi">10.1038/nnano.2006.155</pub-id>
<pub-id pub-id-type="pmid">18654170</pub-id>
</mixed-citation>
</ref>
<ref id="B4"><mixed-citation publication-type="other"><name><surname>de la Iglesia</surname>
<given-names>D</given-names>
</name>
<etal></etal>
<article-title>Nanoinformatics</article-title>
<source>Roadmap</source>
<year>2020</year>
</mixed-citation>
</ref>
<ref id="B5"><mixed-citation publication-type="other"><name><surname>Thomas</surname>
<given-names>DG</given-names>
</name>
<etal></etal>
<article-title>Informatics and standards for nanomedicine technology</article-title>
<source>Wiley Interdiscip Rev Nanomed Nanobiotechnol</source>
<year>2011</year>
</mixed-citation>
</ref>
<ref id="B6"><mixed-citation publication-type="journal"><name><surname>Collins</surname>
<given-names>F</given-names>
</name>
<article-title>Has the revolution arrived?</article-title>
<source>Nature</source>
<year>2010</year>
<volume>464</volume>
<fpage>675</fpage>
<lpage>676</lpage>
</mixed-citation>
</ref>
<ref id="B7"><mixed-citation publication-type="journal"><name><surname>Collins</surname>
<given-names>FS</given-names>
</name>
<article-title>Research agenda. Opportunities for research and NIH</article-title>
<source>Science</source>
<year>2010</year>
<volume>327</volume>
<fpage>36</fpage>
<lpage>37</lpage>
<pub-id pub-id-type="doi">10.1126/science.1185055</pub-id>
<pub-id pub-id-type="pmid">20044560</pub-id>
</mixed-citation>
</ref>
<ref id="B8"><mixed-citation publication-type="other"><name><surname>Poschet</surname>
<given-names>J</given-names>
</name>
<name><surname>Shalley</surname>
<given-names>E</given-names>
</name>
<name><surname>Speakman</surname>
<given-names>J</given-names>
</name>
<article-title>Cancer Biomedical Informatics Grid</article-title>
</mixed-citation>
</ref>
<ref id="B9"><mixed-citation publication-type="journal"><name><surname>Hesse</surname>
<given-names>BW</given-names>
</name>
<name><surname>Croyle</surname>
<given-names>RT</given-names>
</name>
<name><surname>Buetow</surname>
<given-names>KH</given-names>
</name>
<article-title>Cyberinfrastructure and the biomedical sciences</article-title>
<source>Am J Prev Med</source>
<year>2011</year>
<volume>40</volume>
<issue>5 Suppl 2</issue>
<fpage>S97</fpage>
<lpage>102</lpage>
<pub-id pub-id-type="pmid">21521604</pub-id>
</mixed-citation>
</ref>
<ref id="B10"><mixed-citation publication-type="journal"><name><surname>Payne</surname>
<given-names>PRO</given-names>
</name>
<name><surname>Embi</surname>
<given-names>PJ</given-names>
</name>
<name><surname>Niland</surname>
<given-names>J</given-names>
</name>
<article-title>Foundational biomedical informatics research in the clinical and translational science era: a call to action</article-title>
<source>J Am Med Informatics Assoc</source>
<year>2010</year>
<volume>17</volume>
<issue>6</issue>
<fpage>615</fpage>
<lpage>616</lpage>
<pub-id pub-id-type="doi">10.1136/jamia.2010.005165</pub-id>
</mixed-citation>
</ref>
<ref id="B11"><mixed-citation publication-type="journal"><name><surname>Boyd</surname>
<given-names>LB</given-names>
</name>
<etal></etal>
<article-title>The caBIG (R) Life Science Business Architecture Model</article-title>
<source>Bioinformatics</source>
<year>2011</year>
<volume>27</volume>
<issue>10</issue>
<fpage>1429</fpage>
<lpage>1435</lpage>
<pub-id pub-id-type="doi">10.1093/bioinformatics/btr141</pub-id>
<pub-id pub-id-type="pmid">21450709</pub-id>
</mixed-citation>
</ref>
<ref id="B12"><mixed-citation publication-type="journal"><name><surname>Hucka</surname>
<given-names>M</given-names>
</name>
<etal></etal>
<article-title>The systems biology markup language (SBML): a medium for representation and exchange of biochemical network models</article-title>
<source>Bioinformatics</source>
<year>2003</year>
<volume>19</volume>
<issue>4</issue>
<fpage>524</fpage>
<lpage>31</lpage>
<pub-id pub-id-type="doi">10.1093/bioinformatics/btg015</pub-id>
<pub-id pub-id-type="pmid">12611808</pub-id>
</mixed-citation>
</ref>
<ref id="B13"><mixed-citation publication-type="journal"><name><surname>Demir</surname>
<given-names>E</given-names>
</name>
<etal></etal>
<article-title>The BioPAX community standard for pathway data sharing</article-title>
<source>Nat Biotechnol</source>
<year>2010</year>
<volume>28</volume>
<issue>9</issue>
<fpage>935</fpage>
<lpage>42</lpage>
<pub-id pub-id-type="doi">10.1038/nbt.1666</pub-id>
<pub-id pub-id-type="pmid">20829833</pub-id>
</mixed-citation>
</ref>
<ref id="B14"><mixed-citation publication-type="journal"><name><surname>Spellman</surname>
<given-names>PT</given-names>
</name>
<etal></etal>
<article-title>Design and implementation of microarray gene expression markup language (MAGE-ML)</article-title>
<source>Genome Biol</source>
<year>2002</year>
<volume>3</volume>
<issue>9</issue>
<fpage>RESEARCH0046</fpage>
<pub-id pub-id-type="pmid">12225585</pub-id>
</mixed-citation>
</ref>
<ref id="B15"><mixed-citation publication-type="journal"><name><surname>Rayner</surname>
<given-names>TF</given-names>
</name>
<etal></etal>
<article-title>A simple spreadsheet-based</article-title>
<source>MIAME-supportive format for microarray data: MAGE-TAB. BMC Bioinformatics</source>
<year>2006</year>
<volume>7</volume>
<fpage>489</fpage>
</mixed-citation>
</ref>
<ref id="B16"><mixed-citation publication-type="journal"><name><surname>Sansone</surname>
<given-names>S-A</given-names>
</name>
<etal></etal>
<article-title>The First RSBI (ISA-TAB) Workshop: “Can a Simple Format Work for Complex Studies?”</article-title>
<source>OMICS: J Integrative Biol</source>
<year>2008</year>
<volume>12</volume>
<issue>2</issue>
<fpage>143</fpage>
<lpage>149</lpage>
<pub-id pub-id-type="doi">10.1089/omi.2008.0019</pub-id>
</mixed-citation>
</ref>
<ref id="B17"><mixed-citation publication-type="journal"><name><surname>Rocca-Serra</surname>
<given-names>P</given-names>
</name>
<etal></etal>
<article-title>ISA software suite: supporting standards-compliant experimental annotation and enabling curation at the community level</article-title>
<source>Bioinformatics</source>
<year>2010</year>
<volume>26</volume>
<issue>18</issue>
<fpage>2354</fpage>
<lpage>6</lpage>
<pub-id pub-id-type="doi">10.1093/bioinformatics/btq415</pub-id>
<pub-id pub-id-type="pmid">20679334</pub-id>
</mixed-citation>
</ref>
<ref id="B18"><mixed-citation publication-type="journal"><name><surname>Sansone</surname>
<given-names>S-A</given-names>
</name>
<etal></etal>
<article-title>Toward interoperable bioscience data</article-title>
<source>Nat Genet</source>
<year>2012</year>
<volume>44</volume>
<issue>2</issue>
<fpage>121</fpage>
<lpage>126</lpage>
<pub-id pub-id-type="doi">10.1038/ng.1054</pub-id>
<pub-id pub-id-type="pmid">22281772</pub-id>
</mixed-citation>
</ref>
<ref id="B19"><mixed-citation publication-type="journal"><name><surname>Brazma</surname>
<given-names>A</given-names>
</name>
<etal></etal>
<article-title>Minimum information about a microarray experiment (MIAME)-toward standards for microarray data</article-title>
<source>Nat Genet</source>
<year>2001</year>
<volume>29</volume>
<issue>4</issue>
<fpage>365</fpage>
<lpage>71</lpage>
<pub-id pub-id-type="doi">10.1038/ng1201-365</pub-id>
<pub-id pub-id-type="pmid">11726920</pub-id>
</mixed-citation>
</ref>
<ref id="B20"><mixed-citation publication-type="journal"><name><surname>Parkinson</surname>
<given-names>H</given-names>
</name>
<etal></etal>
<article-title>ArrayExpress--a public database of microarray experiments and gene expression profiles</article-title>
<source>Nucleic Acids Res</source>
<year>2007</year>
<volume>35</volume>
<fpage>747</fpage>
<lpage>50</lpage>
<pub-id pub-id-type="doi">10.1093/nar/gkl995</pub-id>
</mixed-citation>
</ref>
<ref id="B21"><mixed-citation publication-type="other"><collab>caArray</collab>
<year>2011</year>
<comment>[cited 2011 November 8]; Available from:<ext-link ext-link-type="uri" xlink:href="https://array.nci.nih.gov/caarray/">https://array.nci.nih.gov/caarray/</ext-link>
</comment>
</mixed-citation>
</ref>
<ref id="B22"><mixed-citation publication-type="journal"><name><surname>Hubble</surname>
<given-names>J</given-names>
</name>
<etal></etal>
<article-title>Implementation of GenePattern within the Stanford Microarray Database</article-title>
<source>Nucleic Acids Res</source>
<year>2009</year>
<volume>37</volume>
<fpage>898</fpage>
<lpage>901</lpage>
<pub-id pub-id-type="doi">10.1093/nar/gkn786</pub-id>
</mixed-citation>
</ref>
<ref id="B23"><mixed-citation publication-type="journal"><name><surname>Reich</surname>
<given-names>M</given-names>
</name>
<name><surname>Reich</surname>
<given-names>M</given-names>
</name>
<etal></etal>
<article-title>GenePattern 2.0</article-title>
<source>Nat Genet</source>
<year>2006</year>
<volume>38</volume>
<issue>5</issue>
<fpage>1</fpage>
<lpage>500</lpage>
<pub-id pub-id-type="pmid">16380718</pub-id>
</mixed-citation>
</ref>
<ref id="B24"><mixed-citation publication-type="journal"><name><surname>Gentleman</surname>
<given-names>RC</given-names>
</name>
<etal></etal>
<article-title>Bioconductor: open software development for computational biology and bioinformatics</article-title>
<source>Genome Biol</source>
<year>2004</year>
<volume>5</volume>
<issue>10</issue>
<fpage>R80</fpage>
<pub-id pub-id-type="doi">10.1186/gb-2004-5-10-r80</pub-id>
<pub-id pub-id-type="pmid">15461798</pub-id>
</mixed-citation>
</ref>
<ref id="B25"><mixed-citation publication-type="book"><collab>ISA-TAB website</collab>
<year>2011</year>
<publisher-name>ISA-TAB website</publisher-name>
<comment>[cited 2011 November 8]; Available from: <ext-link ext-link-type="uri" xlink:href="http://isatab.sourceforge.net/case_studies.html">http://isatab.sourceforge.net/case_studies.html</ext-link>
</comment>
</mixed-citation>
</ref>
<ref id="B26"><mixed-citation publication-type="journal"><name><surname>Roebben</surname>
<given-names>G</given-names>
</name>
<etal></etal>
<article-title>Interlaboratory comparison of size and surface charge measurements on nanoparticles prior to biological impact assessment</article-title>
<source>J Nanoparticle Res</source>
<year>2011</year>
<volume>13</volume>
<issue>7</issue>
<fpage>2675</fpage>
<lpage>2687</lpage>
<pub-id pub-id-type="doi">10.1007/s11051-011-0423-y</pub-id>
</mixed-citation>
</ref>
<ref id="B27"><mixed-citation publication-type="other"><name><surname>Shick</surname>
<given-names>L</given-names>
</name>
<source>Life Sciences Domain Analysis Model (LS DAM)</source>
<year>2011</year>
<comment>Available from: <ext-link ext-link-type="uri" xlink:href="https://wiki.nci.nih.gov/x/cxRlAQ">https://wiki.nci.nih.gov/x/cxRlAQ</ext-link>
</comment>
</mixed-citation>
</ref>
<ref id="B28"><mixed-citation publication-type="journal"><name><surname>Thomas</surname>
<given-names>DG</given-names>
</name>
<name><surname>Pappu</surname>
<given-names>RV</given-names>
</name>
<name><surname>Baker</surname>
<given-names>NA</given-names>
</name>
<article-title>NanoParticle Ontology for cancer nanotechnology research</article-title>
<source>J Biomedical Informatics</source>
<year>2011</year>
<volume>44</volume>
<issue>1</issue>
<fpage>59</fpage>
<lpage>74</lpage>
<pub-id pub-id-type="doi">10.1016/j.jbi.2010.03.001</pub-id>
</mixed-citation>
</ref>
<ref id="B29"><mixed-citation publication-type="book"><collab>cancer Nanotechnology Laboratory Portal (caNanoLab)</collab>
<source>cancer Nanotechnology Laboratory Portal (caNanoLab)</source>
<year>2011</year>
<publisher-name>[cited 2011 November 8]; Available from</publisher-name>
<comment><ext-link ext-link-type="uri" xlink:href="https://cananolab.nci.nih.gov/caNanoLab/">https://cananolab.nci.nih.gov/caNanoLab/</ext-link>
</comment>
</mixed-citation>
</ref>
<ref id="B30"><mixed-citation publication-type="other"><name><surname>Thomas</surname>
<given-names>DG</given-names>
</name>
<etal></etal>
<article-title>Annotating the structure and components of a nanoparticle formulation using computable string expressions</article-title>
<source>in IEEE International Conference on Bioinformatics and Biomedicine</source>
<year>2012</year>
<comment>Philadelphia, PA</comment>
</mixed-citation>
</ref>
<ref id="B31"><mixed-citation publication-type="book"><collab>ASTM WK28974</collab>
<source>New Specification for A Standard File Format For the Submission and Exchange of Data on Nanomaterials and Characterizations 2011</source>
<year>2011</year>
<publisher-name>New Specification for A Standard File Format For the Submission and Exchange of Data on Nanomaterials and Characterizations 2011, New Specification for A Standard File Format For the Submission and Exchange of Data on Nanomaterials and Characterizations 2011</publisher-name>
<comment>[cited 2011 October 20]; Available from: <ext-link ext-link-type="uri" xlink:href="http://www.astm.org/DATABASE.CART/WORKITEMS/WK28974.htm">http://www.astm.org/DATABASE.CART/WORKITEMS/WK28974.htm</ext-link>
</comment>
</mixed-citation>
</ref>
<ref id="B32"><mixed-citation publication-type="journal"><name><surname>de Matos</surname>
<given-names>P</given-names>
</name>
<etal></etal>
<article-title>Chemical Entities of Biological Interest: an update</article-title>
<source>Nucleic Acids Res</source>
<year>2010</year>
<volume>38</volume>
<issue>suppl 1</issue>
<fpage>D249</fpage>
<lpage>D254</lpage>
<pub-id pub-id-type="pmid">19854951</pub-id>
</mixed-citation>
</ref>
<ref id="B33"><mixed-citation publication-type="journal"><collab>T.G.O.C</collab>
<article-title>Creating the Gene Ontology Resource. Design and Implementation</article-title>
<source>Genome Res</source>
<year>2001</year>
<volume>11</volume>
<issue>8</issue>
<fpage>1425</fpage>
<lpage>1433</lpage>
<pub-id pub-id-type="doi">10.1101/gr.180801</pub-id>
<pub-id pub-id-type="pmid">11483584</pub-id>
</mixed-citation>
</ref>
<ref id="B34"><mixed-citation publication-type="journal"><name><surname>Sioutos</surname>
<given-names>N</given-names>
</name>
<etal></etal>
<article-title>NCI Thesaurus: A semantic model integrating cancer-related clinical and molecular information</article-title>
<source>J Biomedical Informatics</source>
<year>2007</year>
<volume>40</volume>
<issue>1</issue>
<fpage>30</fpage>
<lpage>43</lpage>
<pub-id pub-id-type="doi">10.1016/j.jbi.2006.02.013</pub-id>
</mixed-citation>
</ref>
<ref id="B35"><mixed-citation publication-type="other"><collab>Unit Ontology</collab>
<comment>[cited 2012; Available from: <ext-link ext-link-type="uri" xlink:href="http://www.obofoundry.org/cgi-bin/detail.cgi?id=unit">http://www.obofoundry.org/cgi-bin/detail.cgi?id=unit</ext-link>
</comment>
</mixed-citation>
</ref>
</ref-list>
</back>
</pmc>
</record>
Pour manipuler ce document sous Unix (Dilib)
EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/CyberinfraV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 0002618 | SxmlIndent | more
Ou
HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 0002618 | SxmlIndent | more
Pour mettre un lien sur cette page dans le réseau Wicri
{{Explor lien |wiki= Ticri/CIDE |area= CyberinfraV1 |flux= Pmc |étape= Corpus |type= RBID |clé= |texte= }}
![]() | This area was generated with Dilib version V0.6.25. | ![]() |