<?xml version="1.0" encoding="UTF-8"?>
<collection 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">
 <record>
  <leader>00000caa a22000003i 4500</leader>
  <controlfield tag="001">UP-1685594773862409065</controlfield>
  <controlfield tag="003">Buklod</controlfield>
  <controlfield tag="005">20210503203822.0</controlfield>
  <controlfield tag="006">m     |  |        </controlfield>
  <controlfield tag="007">ta</controlfield>
  <controlfield tag="008">210503s2006    xx      r    |||| u|eng d</controlfield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(iLib)UPBAG-00040012080</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
   <subfield code="d">BAG</subfield>
   <subfield code="e">rda</subfield>
  </datafield>
  <datafield tag="041" ind1="0" ind2=" ">
   <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
   <subfield code="a">ARTICLE-3336</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Luquin, Elizabeth</subfield>
   <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">To be in relation</subfield>
   <subfield code="b">ancestors' or the polysemy of the Minangyan (Hanunoo) term apu</subfield>
   <subfield code="c">Elizabeth Luquin.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
   <subfield code="c">2006.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
   <subfield code="a">pages [87]-94</subfield>
   <subfield code="c">23 cm</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
   <subfield code="a">text</subfield>
   <subfield code="2">rdacontent</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
   <subfield code="a">unmediated</subfield>
   <subfield code="2">rdamedia</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
   <subfield code="a">volume</subfield>
   <subfield code="2">rdacarrier</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
   <subfield code="a">Includes bibliographical references (page 94).</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
   <subfield code="a">This article deals with the polysemy of the term 'āpu used by the Mangyan Patag of   the Philippines, Minangyan language speakers. The  anthropologists of the region usually  translate the term 'apu as 'owner', 'master', and sometimes 'spirit possessor', 'leader'. They also define it as 'ascending kin (GEN-5, GEN-6, and GEN-7)' and stress the notions of property and ownership. And yet the problematic term 'āpu signifies more than a simple  ownership relation. I will show in this article that these glosses are not entirely satisfactory. Rather  than 'master' or 'owner', translations which seem to impoverish the polysemic senses, I will argue - giving some concrete examples - that the polysemy of the term 'āpu appears to imply more fundamental meanings. It turns out that we need to take into account  that 'āpu means  'relation: ancestor', which organizes the relations between the living and the dead.</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Philippine Journal of Linguistics</subfield>
   <subfield code="g">Vol. 37, Number 1 (June 2006), p. [87]-94.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="a">Request full-text access via UPB University Library through</subfield>
   <subfield code="u">https://forms.gle/KZjBv7aRtY6jiL5E9</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
   <subfield code="z">(viewed 03 May 2021)</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
   <subfield code="a">FI</subfield>
  </datafield>
  <datafield tag="852" ind1="0" ind2=" ">
   <subfield code="a">UPBAG</subfield>
   <subfield code="b">UPBAG-MAIN</subfield>
   <subfield code="h">ARTICLE-3336</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
   <subfield code="a">Analytics</subfield>
  </datafield>
 </record>
</collection>
