<?xml version="1.0" standalone="yes"?>
<Paper uid="P80-1001">
  <Title>ON THE SPATIAL USES OF PREPOSITIONS</Title>
  <Section position="3" start_page="0" end_page="0" type="intro">
    <SectionTitle>
1.2. FUNCTION
</SectionTitle>
    <Paragraph position="0"> One says in ran disk and on the tray though these objects uy be essentially Identical in shape. One will not ordinarily say tan cat Is in :At t~e, but un~r tan t~e, even with the cage-like table below.</Paragraph>
    <Paragraph position="1"> /oAn is et X Often means that John Is using I as one normally uses it (JoAn is at his desk). If normal use implies being on or m X, then at Is not used (John is in or on the bed, but not at). And to the right of the chadr Is defined by reference to a typical user of the chair.</Paragraph>
    <Paragraph position="2"> 1.3. TYPICAl, PHYSICAl, OR GEOMETRICAL CONTEXT When using in with areas, it Is not sufficient that the reference object be two-dimensional; that object must be part of a surface divided into cells. One does not draw a line in a blackboard; but in tat nlargin is acceptable, because the margin is a subdivision of a page. In the same fashion, ' geographical areas (England, tat county, etc.) are sections of a divided surface. Some objects are exclusively conceptualized as parts of a &amp;quot;cell structure&amp;quot; and cannot then follow at (*at his room, *at England). Other objects can be conceptualized both as elements of a cell structure (in the village), or as one of a set of separate places (at tat ~illage). Or consider ~ard: when 1~ is a part of the grounds of a house, one is restricted to In. But of somebody working In a Junkyard, one could say he is at the )C/rd, reflecting a view of the yard as one of a set of separate locations.</Paragraph>
    <Paragraph position="3"> If a door is in its typical context, i.e. part of a wall, then interpretation of m tk~ right of Me d~r must be based on the door's own axes. Otherwise (In a hardware store for example) an observer's line of sight my override the door's cross-axis.</Paragraph>
  </Section>
class="xml-element"></Paper>