<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="151" 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/151?output=omeka-xml" accessDate="2026-08-21T17:15:36+00:00">
  <fileContainer>
    <file fileId="150">
      <src>https://com395.omeka.chass.ncsu.edu/files/original/39fb44af333d60dbbb0f2312cad5d08a.jpeg</src>
      <authentication>ec525e12ab76c4ba72a31dcccf261490</authentication>
    </file>
  </fileContainer>
  <collection collectionId="7">
    <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="908">
                <text>Post-Books</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="909">
                <text>Post-Books</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="910">
                <text>What happens with books and other periodicals when they move to digital space? What kinds of affordances are there, and what are the limitations? How does materiality work?</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="911">
                <text>Students of COM/ENG 395</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="912">
                <text>Digital Images</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="1032">
              <text>Does Writing Have A Future? - Vilem Flusser 1987</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1033">
              <text>20th century speculation on future technology revolutionizing writing</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1034">
              <text>These images are of Vilem Flusser’s English edition of Does Writing Have a Future? Flusser’s book raises many different implications about this post-books transformation that Drucker’s “The Virtual Codex fromFrom Page Space to E-Space” also raises. In Drucker’s conclusion they raise that “Books of the future depend very much on how we meet the challenge to understand what a book has been.” and finishes up by stating that the digital or future of books will be reformatted. Drucker’s speculation in 2003 about reformatting seems to be occurring as digital e-readers steadily assert their individuality. Greater complexity has led to greater possibilities to functionally distinguish digital books from bound pages, which also hazards progressive acclimation. In 2020 digital books have their benefits but they've yet to be unanimously perfected despite continued innovation. &#13;
&#13;
Vilem Flusser’s book is a great contrast to Drucker’s article because Flusser more radically takes the position that writing will, and needs, to change and evolve from its current capacities which Flusser considers primitive. Flusser’s mode of conflict regarding writing and its relationship to society promotes critical discussion about the structural consequences of writing which remains relevant while digital books continue to optimize rather than entirely transform.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="1035">
              <text>Vilem Flusser</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="1036">
              <text>Mike Schmitt</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="1037">
              <text>Digital image</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
