<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="160" public="1" featured="0" 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://com395.omeka.chass.ncsu.edu/items/show/160?output=omeka-xml" accessDate="2026-08-08T12:15:14+00:00">
  <fileContainer>
    <file fileId="160">
      <src>https://com395.omeka.chass.ncsu.edu/files/original/5763c8df449b43311c4485c74b7bee4c.jpg</src>
      <authentication>f4db969cbb6cf8f67c08665f8dfe2daf</authentication>
    </file>
  </fileContainer>
  <collection collectionId="8">
    <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="1050">
                <text>Visual Literacy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1051">
                <text>Visual Literacy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1052">
                <text>Can images be "read" using a known language? This is a collection of graphics that bring up issues related to not just viewing things, but apprising what they are saying.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1053">
                <text>Students of COM/ENG 395</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="6">
    <name>Still Image</name>
    <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</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="1090">
              <text>Raleigh Parking Sign</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1091">
              <text>Visual Literacy</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1092">
              <text>This is a picture of a parking sign in Downtown Raleigh. The reason I chose to use this photo is because it contains many directions in very few words. It is not in the picture but above the sign there is another sign describing how long the parking is for during the week. The sign we are focusing on is important because its colors are chosen strategically to blend with the blue parking logos and create concurrency with the new parking app they are promoting. It is easy to identify how to use this app because most people know how to operate a parking meter and the function can be transferred easily to a mobile interface. There is also a parking meter there just in case someone doesn't have the time or knowledge of downloading the app. They are both present for people trying to park so that in the future the meter will be gone and people can just pay on their phone.&#13;
I don't believe this sign is required by the state but the way it was designed makes it look like a state regulated sign so that people will obey it and pay closer attention. Although it says nothing about the parking spots and only gives the zone number, you are able to put pieces together to understand that the number space you're parked in has to be keyed into the zone within the app or parking meter to pay for your parking. Normal traffic signs and parking signs are interesting to me because they are able to communicate with very few or no words what the law is.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="1093">
              <text>CJ Falchi</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1094">
              <text>3/1/2020</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1095">
              <text>Digital Image</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1096">
              <text>Parking sign</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
  <tagContainer>
    <tag tagId="78">
      <name>cj</name>
    </tag>
    <tag tagId="19">
      <name>Parking</name>
    </tag>
    <tag tagId="248">
      <name>sign</name>
    </tag>
    <tag tagId="246">
      <name>Visual Literacy</name>
    </tag>
  </tagContainer>
</item>
