1 Ocak 2019 Dergi makalesi Açık Erişim

Bejan, A.; Gunes, U.; Sahin, B.

MARC21 XML

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">user-tubitak-destekli-proje-yayinlari</subfield>
    <subfield code="o">oai:zenodo.org:72415</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">The literature reviewed in this article shows that the evolution of vehicles is in line with the evolution of animal locomotion and that it is predictable from the constructal law of design and evolution in nature. The evolution of ships and airplanes illustrates the evolutionary design of the human-and-machine species as it moves and spreads on Earth: farther, faster, more efficiently, and with greater lasting power (sustainability). Every vehicle size has its design. The bigger vehicle is not a magnified facsimile of the smaller. The size fraction that the lifting organs occupy in the overall vehicle increases with the body size. Every vehicle size has its niche, the supporting territory, and population to which it belongs. All the designs of movement on the globe evolve. Vehicles do not evolve by themselves; they evolve hand in glove with the humans who design and use them. The result is hierarchy, and it is why hierarchy is natural and unavoidable. We see it in geophysical movement (river basins), animal movement (food chain), human social movement (global air and maritime traffic), and everywhere else. The appearance of a new hierarchical design of movement on earth does not eliminate the existing hierarchical designs of movement. The new hierarchy joins the old, and what works is kept. No evolving system deviates from the features dictated by the law of physics of evolution in nature.</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">article</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="a">Creative Commons Attribution</subfield>
    <subfield code="u">http://www.opendefinition.org/licenses/cc-by</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Bejan, A.</subfield>
    <subfield code="u">Duke Univ, Dept Mech Engn &amp; Mat Sci, Durham, NC 27708 USA</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="z">md5:0471c8b64690269a8f7a6430b57ad250</subfield>
    <subfield code="s">116</subfield>
    <subfield code="u">https://aperta.ulakbim.gov.trrecord/72415/files/bib-6e4d3aa4-31be-4e63-b369-afbe0d8146d6.txt</subfield>
  </datafield>
  <controlfield tag="005">20210316034308.0</controlfield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2019-01-01</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.1063/1.5099626</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">The evolution of air and maritime transport</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="4">
    <subfield code="v">6</subfield>
    <subfield code="p">APPLIED PHYSICS REVIEWS</subfield>
    <subfield code="n">2</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Gunes, U.</subfield>
    <subfield code="u">Yildiz Tech Univ, Dept Naval Architecture &amp; Marine Engn, TR-34349 Istanbul, Turkey</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Sahin, B.</subfield>
    <subfield code="u">Yildiz Tech Univ, Dept Naval Architecture &amp; Marine Engn, TR-34349 Istanbul, Turkey</subfield>
  </datafield>
  <controlfield tag="001">72415</controlfield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-tubitak-destekli-proje-yayinlari</subfield>
  </datafield>
</record>