<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>     caa a22        4500</leader>
  <controlfield tag="001">445822295</controlfield>
  <controlfield tag="003">CHVBK</controlfield>
  <controlfield tag="005">20180317145247.0</controlfield>
  <controlfield tag="007">cr unu---uuuuu</controlfield>
  <controlfield tag="008">170323e20110201xx      s     000 0 eng  </controlfield>
  <datafield tag="024" ind1="7" ind2="0">
   <subfield code="a">10.1007/s00779-010-0315-7</subfield>
   <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(NATIONALLICENCE)springer-10.1007/s00779-010-0315-7</subfield>
  </datafield>
  <datafield tag="245" ind1="0" ind2="0">
   <subfield code="a">Hyperform specification: designing and interacting with self-reconfiguring materials</subfield>
   <subfield code="h">[Elektronische Daten]</subfield>
   <subfield code="c">[Michael Weller, Mark Gross, Seth Goldstein]</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">We are on the verge of realizing a new class of material that need not be machined or molded in order to make things. Rather, the material forms and re-forms itself according to software programmed into its component elements. These self-reconfiguring materials are composed of robotic modules that coordinate with each other locally to produce global behaviors. These robotic materials can be used to realize a new class of artifact: a shape that can change over time, i.e., a four-dimensional shape or a hyperform. Hyperforms present several opportunities: objects such as furniture could exhibit dynamic behaviors, could respond to tangible and gestural input, and end-users could customize their form and behavior. To realize these opportunities, the tangible interaction community must begin to consider how we will create and interact with hyperforms. The behaviors that hyperforms can perform will be constrained by the capabilities of the self-reconfiguring materials they are made of. By considering how we will interact with hyperforms, we can inform the design of these systems. In this paper, we discuss the life cycle of a hyperform and the roles designers and end-users play in interacting with hyperforms at these various stages. We consider the interactions such a system could afford as well as how underlying hardware and software affect this interaction. And we consider the extent to which several current hardware systems, including our own prismatic cubes (Weller etal. in Intelligent Robots and Systems. IEEE, 2009), can support the hyperform interactions we envision.</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
   <subfield code="a">Springer-Verlag London Limited, 2010</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Modular robotics</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Tangible interaction</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Hyperforms</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="690" ind1=" " ind2="7">
   <subfield code="a">Programmable matter</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Weller</subfield>
   <subfield code="D">Michael</subfield>
   <subfield code="u">Computational Design Lab, Carnegie Mellon University, 15213, Pittsburgh, PA, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Gross</subfield>
   <subfield code="D">Mark</subfield>
   <subfield code="u">Computational Design Lab, Carnegie Mellon University, 15213, Pittsburgh, PA, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2=" ">
   <subfield code="a">Goldstein</subfield>
   <subfield code="D">Seth</subfield>
   <subfield code="u">Computer Science Department, Carnegie Mellon University, 15213, Pittsburgh, PA, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
   <subfield code="t">Personal and Ubiquitous Computing</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">15/2(2011-02-01), 133-149</subfield>
   <subfield code="x">1617-4909</subfield>
   <subfield code="q">15:2&lt;133</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">15</subfield>
   <subfield code="o">779</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
   <subfield code="u">https://doi.org/10.1007/s00779-010-0315-7</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="908" ind1=" " ind2=" ">
   <subfield code="D">1</subfield>
   <subfield code="a">research-article</subfield>
   <subfield code="2">jats</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">856</subfield>
   <subfield code="E">40</subfield>
   <subfield code="u">https://doi.org/10.1007/s00779-010-0315-7</subfield>
   <subfield code="q">text/html</subfield>
   <subfield code="z">Onlinezugriff via DOI</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Weller</subfield>
   <subfield code="D">Michael</subfield>
   <subfield code="u">Computational Design Lab, Carnegie Mellon University, 15213, Pittsburgh, PA, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Gross</subfield>
   <subfield code="D">Mark</subfield>
   <subfield code="u">Computational Design Lab, Carnegie Mellon University, 15213, Pittsburgh, PA, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">700</subfield>
   <subfield code="E">1-</subfield>
   <subfield code="a">Goldstein</subfield>
   <subfield code="D">Seth</subfield>
   <subfield code="u">Computer Science Department, Carnegie Mellon University, 15213, Pittsburgh, PA, USA</subfield>
   <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="950" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="P">773</subfield>
   <subfield code="E">0-</subfield>
   <subfield code="t">Personal and Ubiquitous Computing</subfield>
   <subfield code="d">Springer-Verlag</subfield>
   <subfield code="g">15/2(2011-02-01), 133-149</subfield>
   <subfield code="x">1617-4909</subfield>
   <subfield code="q">15:2&lt;133</subfield>
   <subfield code="1">2011</subfield>
   <subfield code="2">15</subfield>
   <subfield code="o">779</subfield>
  </datafield>
  <datafield tag="900" ind1=" " ind2="7">
   <subfield code="a">Metadata rights reserved</subfield>
   <subfield code="b">Springer special CC-BY-NC licence</subfield>
   <subfield code="2">nationallicence</subfield>
  </datafield>
  <datafield tag="898" ind1=" " ind2=" ">
   <subfield code="a">BK010053</subfield>
   <subfield code="b">XK010053</subfield>
   <subfield code="c">XK010000</subfield>
  </datafield>
  <datafield tag="949" ind1=" " ind2=" ">
   <subfield code="B">NATIONALLICENCE</subfield>
   <subfield code="F">NATIONALLICENCE</subfield>
   <subfield code="b">NL-springer</subfield>
  </datafield>
 </record>
</collection>
