<?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>01751nmm a22002537a 4500</leader>
  <controlfield tag="003">ES-BaAUN</controlfield>
  <controlfield tag="005">20230224120055.0</controlfield>
  <controlfield tag="008">221102| ||||go||d|||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="022" ind1=" " ind2=" ">
    <subfield code="a">2575-5374</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">ES-BaAUN</subfield>
    <subfield code="b">eng</subfield>
    <subfield code="c">ES-BaAUN</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Malpas, Jeff</subfield>
    <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Building Memory: Ontology in Architecture</subfield>
  </datafield>
  <datafield tag="260" ind1="3" ind2=" ">
    <subfield code="b">urbanNext,</subfield>
    <subfield code="c">February 01, 2019.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="b">3690 words.</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Essay, expanding design practices, Jeff Malpas, No Density, Territory and mobility	</subfield>
  </datafield>
  <datafield tag="501" ind1=" " ind2=" ">
    <subfield code="a">Accessibility, Architecture, Architecture&#x2019;s challenge, Building, City, Collective identity, Contemporary architecture, Cultural agitator, Design, Essay, Ethics, Humanity, Identity, Memory, Power of materiality, Practice, Public engagement, Responsive Environment, Space-time relationship, Texture, Topography	
</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">The following is an abridged version of an essay that first appeared in Interstices: Journal of Architecture and Related Arts 13 (2012), pp.11-21.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">What is the ontology of architecture? One way to understand this question is to take it as asking after the basic elements of architectural practice. Another is to take the question as directed at the being of architecture, its proper limits and grounds. It is in this latter sense that I wish to put the question here. When taken in this sense, it seems there can be only one answer: more so than any other mode of human activity, architecture has its being in the human engagement with place, and more specifically, in the engagement with place as opened through building.</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Architecture</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Theory</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Concept</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">https://urbannext.net/building-memory/</subfield>
    <subfield code="z">Access to info</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">CF</subfield>
    <subfield code="n">0</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">2087</subfield>
    <subfield code="d">2087</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">ddc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">9876543210</subfield>
    <subfield code="b">9876543210</subfield>
    <subfield code="d">2023-02-24</subfield>
    <subfield code="l">0</subfield>
    <subfield code="r">2023-02-24</subfield>
    <subfield code="w">2023-02-24</subfield>
    <subfield code="y">CF</subfield>
  </datafield>
</record>
