<?xml version="1.0" encoding="UTF-8"?>
<record
    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"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01707nam a22002057a 4500</leader>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">37887</subfield>
    <subfield code="d">37887</subfield>
  </datafield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">9781032174747</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng-</subfield>
  </datafield>
  <datafield tag="082" ind1=" " ind2=" ">
    <subfield code="a">341.48</subfield>
    <subfield code="b">CON-</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a"> Constructing the Responsibility to Protect :</subfield>
    <subfield code="b"> contestation and consolidation / </subfield>
    <subfield code="c">edited by Charles T. Hunt and Phil Orchard.</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">London : </subfield>
    <subfield code="b">Routledge, </subfield>
    <subfield code="c">2020.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">208p. </subfield>
    <subfield code="b">illustrations (black and white).</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Includes bibliographical references and index.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">The book focuses on how the R2P doctrine has been both consolidated and contested along three dimensions, regarding its meaning, status and application. The first focuses on how the R2P should be understood in a theoretical sense, exploring it through the lens of the International Relations constructivist approach and through different toolkits available to conventional and critical constructivists. The second focuses on how the R2P interacts with other normative frameworks, and how this interaction can lead to a range of effects from mutual reinforcement and co-evolution through to unanticipated feedback that can undermine consensus and flexibility. The third focuses on how key state actors &#x2013; including the United States, China and Russia &#x2013; understand, use and contest the R2P. Together, the book&#x2019;s chapters demonstrate that broad aspects of the R2P are consolidated in the sense that they are accepted by states even while other, specific aspects, remain subject to contestation in practice and in policy.</subfield>
  </datafield>
  <datafield tag="546" ind1=" " ind2=" ">
    <subfield code="a">English.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Responsibility to protect (International law) </subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Human rights.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Hunt, Charles T.</subfield>
    <subfield code="e">editor.</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a"> Orchard, Phil</subfield>
    <subfield code="e">editor.</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">BK</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">NASSDOC</subfield>
    <subfield code="b">NASSDOC</subfield>
    <subfield code="d">2023-03-16</subfield>
    <subfield code="e">Overseas</subfield>
    <subfield code="g">0.00</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">341.48 CON-</subfield>
    <subfield code="p">53334</subfield>
    <subfield code="r">2023-06-01 00:00:00</subfield>
    <subfield code="v">0.00</subfield>
    <subfield code="w">2023-06-01</subfield>
    <subfield code="y">BK</subfield>
  </datafield>
</record>
