<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     naa a22        4500</leader>
  <controlfield tag="001">510779042</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180411083240.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">180411e20130601xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/s11948-012-9357-8</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/s11948-012-9357-8</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Malsch</subfield>
   <subfield code="D">Ineke</subfield>
   <subfield code="u">Malsch TechnoValuation, Vondellaan 90, 3521 GH, Utrecht, The Netherlands</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="4">
   <subfield code="a">The Just War Theory and the Ethical Governance of Research</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Ineke Malsch]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">This article analyses current trends in and future expectations of nanotechnology and other key enabling technologies for security as well as dual use nanotechnology from the perspective of the ethical Just War Theory (JWT), interpreted as an instrument to increase the threshold for using armed force for solving conflicts. The aim is to investigate the relevance of the JWT to the ethical governance of research. The analysis gives rise to the following results. From the perspective of the JWT, military research should be evaluated with different criteria than research for civil or civil security applications. From a technological perspective, the boundaries between technologies for civil and military applications are fuzzy. Therefore the JWT offers theoretical grounds for making clear distinctions between research for military, civil security and other applications that are not obvious from a purely technological perspective. Different actors bear responsibility for development of the technology than for resorting to armed force for solving conflicts or for use of weapons and military technologies in combat. Different criteria should be used for moral judgment of decisions made by each type of actor in each context. In addition to evaluation of potential consequences of future use of the weapons or military technologies under development, the JWT also prescribes ethical evaluation of the inherent intent and other foreseeable consequences of the development itself of new military technologies.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Springer Science+Business Media B.V., 2012</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Just War Theory</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Research ethics</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Nanotechnology</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Emerging technology</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Governance</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Science and Engineering Ethics</subfield>
   <subfield code="d">Springer Netherlands</subfield>
   <subfield code="g">19/2(2013-06-01), 461-486</subfield>
   <subfield code="x">1353-3452</subfield>
   <subfield code="q">19:2&lt;461</subfield>
   <subfield code="1">2013</subfield>
   <subfield code="2">19</subfield>
   <subfield code="o">11948</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/s11948-012-9357-8</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/s11948-012-9357-8</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">100</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Malsch</subfield>
   <subfield code="D">Ineke</subfield>
   <subfield code="u">Malsch TechnoValuation, Vondellaan 90, 3521 GH, Utrecht, The Netherlands</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Science and Engineering Ethics</subfield>
   <subfield code="d">Springer Netherlands</subfield>
   <subfield code="g">19/2(2013-06-01), 461-486</subfield>
   <subfield code="x">1353-3452</subfield>
   <subfield code="q">19:2&lt;461</subfield>
   <subfield code="1">2013</subfield>
   <subfield code="2">19</subfield>
   <subfield code="o">11948</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
