Pesquisa de referências

On the concept and definition of terrorism risk

<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd">
  <record>
    <leader>00000cab a2200000   4500</leader>
    <controlfield tag="001">MAP20160003697</controlfield>
    <controlfield tag="003">MAP</controlfield>
    <controlfield tag="005">20160205135825.0</controlfield>
    <controlfield tag="008">160205e20151201esp|||p      |0|||b|spa d</controlfield>
    <datafield tag="040" ind1=" " ind2=" ">
      <subfield code="a">MAP</subfield>
      <subfield code="b">spa</subfield>
      <subfield code="d">MAP</subfield>
    </datafield>
    <datafield tag="084" ind1=" " ind2=" ">
      <subfield code="a">328.2</subfield>
    </datafield>
    <datafield tag="100" ind1="1" ind2=" ">
      <subfield code="0">MAPA20080019686</subfield>
      <subfield code="a">Aven, Terje</subfield>
    </datafield>
    <datafield tag="245" ind1="0" ind2="0">
      <subfield code="a">On the concept and definition of terrorism risk</subfield>
      <subfield code="c">Terje Aven, Seth Guikema</subfield>
    </datafield>
    <datafield tag="520" ind1=" " ind2=" ">
      <subfield code="a">In this article, we provide some reflections on how to define and understand the concept of terrorism risk in a professional risk assessment context. As a basis for this discussion we introduce a set of criteria that we believe should apply to any conceptualization of terrorism risk. These criteria are based on both criteria used in other areas of risk analysis and our experience with terrorism risk analysis. That is, these criteria offer our perspective. We show that several of the suggested perspectives and definitions have eaknesses in relation to these criteria. A main problem identified is the idea that terrorism risk can be conceptualized as a function of probability and consequence, not as a function of the interactions between adaptive individuals and organizations. We argue that perspectives based solely on probability and consequence should be used cautiously or not at all because they fail to reflect the essential features of the concept of terrorism risk, the threats and attacks, their consequences, and the uncertainties, all in the context of adaptation by the adversaries. These three elements should in our view constitute the main pillars of the terrorism risk concept. From this concept we can develop methods for assessing the risk by identifying a set of threats, attacks,and consequence measures associated with the possible outcome scenarios together with a description of the uncertainties and interactions between the adversaries</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080556808</subfield>
      <subfield code="a">Terrorismo</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080612429</subfield>
      <subfield code="a">Riesgos extraordinarios</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080578626</subfield>
      <subfield code="a">Víctimas humanas</subfield>
    </datafield>
    <datafield tag="650" ind1=" " ind2="4">
      <subfield code="0">MAPA20080591182</subfield>
      <subfield code="a">Gerencia de riesgos</subfield>
    </datafield>
    <datafield tag="700" ind1=" " ind2=" ">
      <subfield code="0">MAPA20120021327</subfield>
      <subfield code="a">Guikema, Seth</subfield>
    </datafield>
    <datafield tag="773" ind1="0" ind2=" ">
      <subfield code="w">MAP20077000345</subfield>
      <subfield code="t">Risk analysis : an international journal</subfield>
      <subfield code="d">McLean, Virginia : Society for Risk Analysis, 1987-2015</subfield>
      <subfield code="x">0272-4332</subfield>
      <subfield code="g">01/12/2015 Volumen 35 Número 12 - diciembre 2015 , p. 2162-2171</subfield>
    </datafield>
  </record>
</collection>