<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://hist1952-17.omeka.fas.harvard.edu/items/browse?output=omeka-xml&amp;page=5&amp;sort_field=Dublin+Core%2CCreator" accessDate="2026-05-07T03:40:03-04:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>5</pageNumber>
      <perPage>10</perPage>
      <totalResults>88</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="35" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
      <elementContainer>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="144">
              <text>map layer</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="142">
                <text>Layer 1: Spheres</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143">
                <text>Perhaps the most intrinsic element of a map are the shapes which guide and inform the reader’s perspective. The art of transforming a three dimensional land mass into a two dimensional piece of paper is reliant on orienting the reader’s line of sight. Vischer’s Novissima totius terrarum orbis tabula relies on four spheroids with two depicting the East-West hemispheres that lie between a proposed meridian. The second set depict azimuthal projections of the North and South Poles where the Earth’s axis meets its surface–this means that the poles are mapped according to flat planes rather than the conic projections of the East-West Hemispheres. I chose not to include these projection lines, however, because of the symbolic nature of empty spheroids. Whereas layers of the map such as the continents, and land-water hemispheres inevitably depict the cartographer’s bias, spheroids are a simplistic and rather equalizing element of the map. They rid the map of the scale distortion that comes from projection lines as well as the colonial distortion that comes from continent/country inclusion.&#13;
I believe the spheroids to be the map in its most raw form.&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147">
                <text>Reade Rossman</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="37" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
      <elementContainer>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="151">
              <text>map layer</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="148">
                <text>Layer 2: North &amp; South Poles</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="149">
                <text>The North and South Poles, while taking up less space on the map, prove just as integral to the arguments of the map as the East-West Hemisphere split. They are depicted via azimuthal projections in which the distance from a center point is recorded while distorting size. More specifically, Vischer applies gnomonic map projection in which circles are depicted as straight lines. The fact that both the poles are relatively uninhabited allows Vischer to apply this method without worrying too much about the effect of such distortion. Novissima totius terrarum orbis tabula follows ptolemaic map projection in that it depicts two “frigid zones” however the map is absent of any conception of a southern land mass like Antarctica. The North Pole includes depictions of modern day Northern European countries and Russia. The depiction of the poles bolster the North-South bias of the map, portraying the North as the height of exploration and expansion and the south as vast and empty. As Professor Nicole De Armendi in Map as Political Agent, projections such as that included in Vischer’s map, “Antarctica is frequently eliminated and the equator is located much lower than midway on the grid, enhancing the North’s dominant position.” While the equator constitutes another layer of the map, the portrayal of the poles serves to fortify a notion of European domination.&#13;
&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150">
                <text>Reade Rossman</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="38" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152">
                <text>Layer 3: Continent Outlines</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="153">
                <text>Perhaps the most obvious medium for the portrayal of European domination is the inclusion or exclusion of continents on Vischer’s map. Europe appears at the northernmost point as the most complex in outline due to the cartographer’s Dutch background. Africa appears particularly large in scale, even surpassing the size of Asia, perhaps due to its conceptualization in European global imaginary as a as site for exploitation of natural resources and the enslavement of people via the transatlantic slave trade. South America is similarly large in scale, perhaps due to the Dutch involvement in Brazil, Chile, and the Guyanas beginning in the early 1600’s. Present day Australia not only appears as the southernmost land in the right spheroid but also appears mostly unexplored. The Dutch colonization of New Holland (present day Australia) involved mapping the western and northern coast of the land in the mid-1600’s, but at the time of Vischer’s map the eastern and southern coasts were, to his knowledge, nonexistent. North America appears relatively small in size, with California existing as its own land mass. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154">
                <text>Reade Rossman</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="48" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="177">
                <text>Layer 4: Zodiac Glyphs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178">
                <text>The final layer of the map I included was the interpretations of the zodiac glyphs that surround the spheres. The twelve signs of the zodiac are divided among the four corners of the map. The upper left features Aries (the ram), Taurus (the bull), and Gemini (the twins) while the upper right includes Leo (the lion), Virgo (the maiden), and Cancer (the crab). The lower left includes Sagittarius (the archer), Libra (the scales), and Scorpio (the scorpion) while the lower right depicts Aquarius (water bearer), Capricorn (the goat), and Pisces (fish). They are intended to represent the sky which surrounds the Earth, and serve to adorn the map along with biblical imagery. The glyphs not only serve to fill what would otherwise be a literal empty void, but expand the map’s purpose to include decoration as well as pragmatism. Art could certainly incentivize people to buy the map–helping to disseminate its contents and in turn, share its arguments with a greater audience.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="179">
                <text>Reade Rossman</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="21" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="97">
                <text>Layer 1: Perspective</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="98">
                <text>Layer one deals with perspective, and what truly constitutes a map within a map. Indeed the perspective drawing beneath the map proper is a map in and of itself, and offers the reader, quite literally, a different angle of 1737 Berlin which was purposefully chosen by the cartographer and serves to ground the reader’s perspective of the map in its totality, and in relation to its other elements. The illustration and its corresponding index together comprise more than one quarter of the map’s total area which communicates its importance in the most practical sense. The caption in German reads roughly (this translation proved difficult even for a native German speaker), “Plan of the city of Berlin as seen by people from the North West.” This information, along with the centrally drawn windmill, and the location of the indexed Weidendamer Bridge (with the help of google maps) positively locates the reader in the bottom right hand corner of the map (shown at windmill). Apart from mentally situating the reader in two places at once (illustrated ground level, and a cartesian point on the traditional map), the process of discerning this location alerts the reader to the map’s inverted compass and offers a detailed view of the built environment of center city Berlin. In this sense the illustration situates the reader in both three and two dimensional space. It invites exploration of the rest of the map’s elements through this specific spatial vantage point, which serves to define these other elements relative to this specifically chosen location. As a result this perspective and its corresponding location are a lens through which the rest of the map can be viewed.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99">
                <text>Ryan Taras</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="22" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="100">
                <text>Layer 2: Plane and Scale</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="101">
                <text>After being spatially situated via the perspective of the vantage point featured in layer one, layer two builds on this sense of location and place by introducing scale, and classification of points of interest in both space and text through use of alphanumerically coded districts. Upper case letters in the map space correspond to eight districts labelled in layer two’s index. Printed numbers in the map space likewise correspond to points of interest within these districts which are also enumerated in the layer two index. In the bottom left hand corner of the map, a scale in the archaic Ruthen (not standard, but roughly 15 feet) provides scale, while in the upper right hand corner, latitude and longitude readings situate Berlin more globally. Building on layer one, layer two accomplishes a number of things for the map’s reader. For one, It notably situates the reader globally via latitude and longitude, allowing for spatial comparison and integration with other maps. Use of the scale now enables quantifiable point to point spatial comparison. Additionally, categorization of points through district classification attaches recognizable linguistic meaning to spatial divisions, and imparts a sense of both spatial and linguistic order to what may otherwise seem an overwhelming distribution of points. More crucially, however, many of the features listed in layer two’s index are also featured in layer one’s index. This provides the reader with an easily referenceable link between what is shown pictorially in layer one, and spatially in layer two. Shown as an example are Dorotheen Stadt Kirche (number 27 in layer one and D3 in layer two) and Jerusalems Kirche (22 in layer one E3 in layer two). These churches are shown in layer one’s perspective picture, but now with the help of layer two, both can be situated in the xy plane, quite literally adding a dimension to the comprehension of these places. Their separating distance, and their respective distances from our windmill perspective can now be quantified definitively, endowing the reader with a sense of space entirely different than is offered in layer one. Furthermore, layer two’s index tells the reader that one church is situated in Dorotheen Stadt, and the other in Friderich’s Stadt which could prove useful information for on the ground navigation. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="102">
                <text>Ryan Taras</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="23" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="103">
                <text>Layer 3: Center</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="104">
                <text>The purpose of layers three and four is to build on the functionality established in layers one and two by introducing elements of physical geography, while also showing how the map presents geographical elements in a way which helps to further a narrative of an emphasized center city. Layer three builds on layers one and two by imparting geographical sense to the perspective, measuring tools, and elements of the built urban environment introduced in the first two layers. With two indices, large amounts of text, densely drawn buildings, and a perspective illustration it is easy to get lost in a plethora of “unnatural” or non-geographical information. The lines in layer three which outline three separately districted islands in the river Spree complement the spatially separated (but not explicitly bounded) capital letter markers of layer two by imposing geographical elements to classify and bound these points in representations of real space on the ground. Where before we had a cartesian plane, we now have points bounded by clearly identifiable elements of geography which could be seen on the ground (or in our perspective illustration). In this sense layer three brings the reader into the geographic reality of Berlin. Furthermore, the way the reader is engaged to interact with this defined geographic space begins to further a narrative of an emphasis on this sectionalized center city denoted by index sections A, B, and C (Berlin, Coln, and Federichs Werder). An entire “overflow index” in the map’s top right hand corner is is devoted to naming streets and other features in these three dense inner city districts. This represents a concerted effort on the part of the mapmaker to emphasize the importance of labeling these inner city features by taking up space elsewhere on the page in order to ensure that they are easily referenced. The city center is also shaded uniformly in a darker hue than spaces elsewhere on the map. This uniformity points to segmentation of these three districts within the city at large, and likewise emphasizes centrality of this geographical area. Additionally, the title box in the map’s lower left corner tells us that the city we are looking at is in fact called Berlin. This may seem a pedestrian or inconsequential observation, however, our index in layer two suggests that “Berlin” is just one of eight districts represented. This serves to strongly imply central importance of district A, and by extension of the uniform colorization of B and C, these districts as well. &#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105">
                <text>Ryan Taras</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="24" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="106">
                <text>Layer 4: Periphery</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107">
                <text>Layer four serves to expand upon layer three’s introduction of geographic sense of space, while also complementing and contributing to a developing narrative of inner city centrality. A large number of geographic features and indicators are introduced giving a sense that, relative to the center city, the periphery is defined by these natural features whereas the center is defined by its density (taking the overflow index as a comparative analog). These features include large swaths of map area populated trees colored green along with others which remain uncolored. This simultaneously adds a sense of pastoralism through use of green, along with a lack of spatial cohesion via the seemingly inconsistent use of color in contrast to the uniformly shaded city center. This sense of fragmentation is further exaggerated by the use of pink, and the fact that both of these colors are used over several different districts. This characterizes the periphery as an area which while districted (D,E,F, G, and H), has less definite boundaries than the city center, and is more fluid. To this end it is also worth mentioning that it is impossible to look at layer four and not see, simultaneously, the area that defines layer three by exclusion, adding to this distinct separation between the center and the periphery. Adding to this contrasting pastoral sense  are the graded hills which appear in the map’s lower right corner. With this one exception, this hill feature is shown exclusively outside the city’s walls. This further serves to connect districts D, E, F, G, and H with an already defined element of extra-mural space. Likewise, dashes in green colored space give a sense of lush grassland, which stands in contrast to the dense center. The only two arrows indicating river flow are also located at the ends of the map, giving a sense that the importance of natural phenomenon are more peripheral. Open featureless space which takes up large swaths of district F also serve to strongly deemphasize the importance of peripheral space. Potentially most striking, however, is the idea that the relative size of districts D, E, and F to G and H may have informed the map maker’s decision to flip the maps orientation upside down. Flipping the map in this way (accounting for space taken up by the perspective illustration) allows the city center to remain close to the geometric center of the paper. Traditional orientation would have left the city center awkwardly close to the top of the map. As a reasonable explanation for the inverted orientation, this decision would work strongly with other evidence of the maps inclination toward a city center spatial emphasis. The benefit of this geometric centrality comes, in a way, at the expense of much of what seems “natural.”&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="108">
                <text>Ryan Taras</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="103" public="1" featured="0">
    <fileContainer>
      <file fileId="105">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/hist1952-17/original/dfcbb9381b6dfc6b931148a8c8b174f9.png</src>
        <authentication>dbbfe5ce9ef66dce9d5dca05706f3db4</authentication>
      </file>
      <file fileId="106">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/hist1952-17/original/e7e2c04593073e6a30d9b0ba9b3e738c.jpg</src>
        <authentication>298724b39b4c774331074cb9c078035b</authentication>
      </file>
      <file fileId="107">
        <src>https://s3.amazonaws.com/atg-prod-oaas-files/hist1952-17/original/00c3301f49ece6c78486d1a50ff1c675.jpg</src>
        <authentication>df18707d9b18ed52d17ee4e64e90de5e</authentication>
      </file>
    </fileContainer>
    <collection collectionId="4">
      <elementSetContainer>
        <elementSet elementSetId="1">
          <name>Dublin Core</name>
          <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
          <elementContainer>
            <element elementId="50">
              <name>Title</name>
              <description>A name given to the resource</description>
              <elementTextContainer>
                <elementText elementTextId="381">
                  <text>Spatial Histories</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="382">
                  <text>What do spatial histories look like? Here is a gallery of images that advance and enrich the histories laid out in &lt;a href="http://hist1952-17.omeka.fas.harvard.edu/exhibits/show/mobility" target="_self"&gt;these student projects&lt;/a&gt;.</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="378">
                <text>Manchukuo: Imperium in Imperio</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="379">
                <text>Ryan Taras</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="6" public="1" featured="0">
    <itemType itemTypeId="19">
      <name>Tracing</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="10">
                <text>Layer 1: Organizational Lines</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11">
                <text>The organization of my map, Sekai bankoku Nihon, depends on segmentation of a variety information. The segmentation is facilitated by black lines of various widths that form boxes and borders for text, drawn depictions of people from around the world, compasses and other forms of information. There is a curved oval line around the perimeter of the representation of the world and there are boxes overlayed on the map and jutting out from the edges. Interestingly, some of the Japanese text on the map is written right on the drawings of land masses or ocean but other chunks of text are bounded by boxes. This hints at a hierarchical ordering of text used on the map. Perhaps the text in boxes labels something at a larger scale, like a continent or broader region instead of a certain country to city. As someone who can not read Japanese, the segmentation of information in and out of boxes is crucial to me for identifying where the most important information (according to the map's designer) is written.  The pictorial renderings of people from different regions are also contained in boxes, meaning the mapmaker wanted that information to be implicitly related to the map but not interfering with the depiction of physical territory. In summary, this level of organization of the map influences our perceptions about what the most important pieces of information are and how the text/art is related to the part of the map that depicts the physical world. </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="198">
                <text>Tomas Spiers</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
