<?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://igi.indrastra.com/items?output=omeka-xml&amp;page=238&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-14T22:04:14+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>238</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1294" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26087">
                <text>Ozdamli, Fezile</text>
              </elementText>
              <elementText elementTextId="26088">
                <text>Ercag, Erinc</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="26089">
                <text>2018-03-29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26090">
                <text>In order that mobile applications can be employed successfully in education, the opinions of teachers for using these applications must be identified and improved. For these reasons, the purpose of this study is to identify the opinions of teacher candidates, who are teachers of the future, on the usage of mobile applications in the process of multimedia project development. This study which was conducted with the purpose of identifying the opinions of teacher candidates on usage of mobile applications in education as means of communication employed qualitative method. Results is that using mobile applications in multimedia project development process attracted the attention of students and ensured effective communication. </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="26091">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="26092">
                <text>https://online-journals.org/index.php/i-jim/article/view/7679</text>
              </elementText>
              <elementText elementTextId="26093">
                <text>10.3991/ijim.v12i2.7679</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26094">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="26095">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="26096">
                <text>https://online-journals.org/index.php/i-jim/article/view/7679/4863</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26097">
                <text>Copyright (c) 2018 Fezile Ozdamli</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="26098">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 12 No. 2 (2018); pp. 27-38</text>
              </elementText>
              <elementText elementTextId="26099">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26100">
                <text>Opinions of Teacher Candidates on the Usage of Mobile Applications in the Multimedia Development Processes</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="26101">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="26102">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="26103">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="590" public="1" featured="0">
    <collection collectionId="28">
      <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="11779">
                  <text>Journal of Open Access to Law</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="45">
              <name>Publisher</name>
              <description>An entity responsible for making the resource available</description>
              <elementTextContainer>
                <elementText elementTextId="12877">
                  <text>Cornell University</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11855">
                <text>Phiri, Josiline</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="11856">
                <text>2013-12-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11857">
                <text>The wave of free access to law movement hit Zimbabwe leading to the establishment of the Zimbabwe Legal Information Institute (ZimLII). This was started with the help of African Legal Information Institute (AfricanLII) which sourced funds to kick start the project and then held training workshops to equip the people who will be working with the administrator. There is a steering committee which comprises of academics, lawyers, publishers, information technologists and librarians from various organisations. This board is chaired by the Director of Legal Resources Foundation. This led to the creation of a website and content has been uploaded to populate the site. The website is up and running and an administrator was employed to oversee the day to day running of the website and its maintenance. This paper is an account of the opportunities and challenges that has been faced by the institute. The major challenge was the issue of sustainability in terms of non availability of funds to continuously support the project. The ZimLII project can be regarded as one of the successful initiative towards the availability of legal information to the general public since there are plans to make it a one stop shop for those looking for such information.</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="11858">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="11859">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/13</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11860">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="11861">
                <text>Journal of Open Access to Law</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="11862">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/13/15</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="11863">
                <text>Journal of Open Access to Law; Vol. 1 No. 1 (2013)</text>
              </elementText>
              <elementText elementTextId="11864">
                <text>2372-7152</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11865">
                <text>Zimbabwe Legal Information Institute</text>
              </elementText>
              <elementText elementTextId="11866">
                <text>ZimLII</text>
              </elementText>
              <elementText elementTextId="11867">
                <text>Free access to law - Zimbabwe</text>
              </elementText>
              <elementText elementTextId="11868">
                <text>Open government data</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11869">
                <text>Opportunities and challenges to free access to law in a changing world: a case of Zimbabwe Legal Information Institute (ZimLII)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11870">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="11871">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="11872">
                <text>Peer-reviewed article</text>
              </elementText>
              <elementText elementTextId="11873">
                <text>Case study</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1447" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29537">
                <text>Hussaini, Muktar</text>
              </elementText>
              <elementText elementTextId="29538">
                <text>Awang Nor, Shahrudin</text>
              </elementText>
              <elementText elementTextId="29539">
                <text>Ahmad, Amran</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="29540">
                <text>2019-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29541">
                <text>Named Data Networking is a consumer-driven network that supports content consumer mobility due to the nature of in-network catching. The catching suppressed unnecessary Interest packets losses by providing an immediate copy of the data and consumer-driven nature influencedthe mobile consumer to resend unsatisfied Interest packet immediately after the handoff. Once the producer moves to a new location, the name prefix changed automatically after handoff to the new router or point of attachment. The entire network lacks the knowledge of producer movement unless if the producer announces its new prefix to update the FIBs of intermediate routers. Lack of producer’s movement knowledge causes an increase of handoff latency, signaling overhead cost, Interests packets losses, poor utilization of bandwidth and packets delivery. Therefore, there is needs to provide substantial producer mobility support to minimize the handoff latency, handoff signaling overhead cost, reduce the unnecessary Interest packets loss to improve data packets delivery once a content producer relocated. In this paper, broadcasting strategy is introduced to facilitate the handoff procedures and update the intermediate routers about the producer movement. Hence, analytical investigation result of this paper addresses the deficiency of Kite scheme by minimizing handoff signaling cost and provides data path optimization after the handoff.</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="29542">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="29543">
                <text>https://online-journals.org/index.php/i-jim/article/view/10513</text>
              </elementText>
              <elementText elementTextId="29544">
                <text>10.3991/ijim.v13i04.10513</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29545">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="29546">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="29547">
                <text>https://online-journals.org/index.php/i-jim/article/view/10513/5586</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29548">
                <text>Copyright (c) 2019 Muktar Hussaini, Shahrudin Awang Nor, Amran Ahmad</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="29549">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 04 (2019); pp. 4-19</text>
              </elementText>
              <elementText elementTextId="29550">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29551">
                <text>Network analysis model</text>
              </elementText>
              <elementText elementTextId="29552">
                <text>signaling cost</text>
              </elementText>
              <elementText elementTextId="29553">
                <text>handoff latency</text>
              </elementText>
              <elementText elementTextId="29554">
                <text>Named data networking</text>
              </elementText>
              <elementText elementTextId="29555">
                <text>Producer mobility support</text>
              </elementText>
              <elementText elementTextId="29556">
                <text>broadcast strategy</text>
              </elementText>
              <elementText elementTextId="29557">
                <text>mobility Interest</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29558">
                <text>Optimal Broadcast Strategy-Based Producer Mobility Support Scheme for Named Data Networking</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29559">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29560">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29561">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3172" public="1" featured="0">
    <collection collectionId="47">
      <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="64218">
                  <text>Journal of Naval Architecture and Marine Engineering</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64938">
                <text>Karim, Md Mashud</text>
              </elementText>
              <elementText elementTextId="64939">
                <text>Suzuki, K</text>
              </elementText>
              <elementText elementTextId="64940">
                <text>Kai, H</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="64941">
                <text>2009-02-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64942">
                <text>This paper presents results from the application of the genetic algorithm (GA) technique to the design optimization of hydrofoil and marine propeller incorporating potential based boundary element method (BEM). Although, larger population size as implemented by simple genetic algorithm (SGA) could find the optimal individual after a fewer number of generations than smaller population size, it is penalized by a longer amount of time to evaluate fitness in every generation. An investigation is, therefore, conducted in this research to implement micro genetic algorithm (Î¼GA) with a very small population, and with simple genetic parameters, in order to achieve faster convergence to better solution from generation to generation. The technique is applied here to optimize hydrofoils of different plan forms, e.g., rectangular, elliptical, trapezoidal etc. Firstly, the hydrofoil design parameters, such as, angle of incidence, maximum thickness and camber ratios, aspect ratio, taper ratio, angle of sweep etc. are initialized randomly and the generated hydrofoil is analyzed by potential based boundary element method. GA then updates the design parameters over generation after generation and finally, finds an improved hydrofoil of maximum lift-drag ratio or minimum drag coefficient satisfying some design constraints. An improved blade or hydrofoil section is also designed by GA satisfying some design constraints. Finally, the technique is applied to the optimum design of marine propeller. In this study, Î¼GA is found useful and prospective tool for the design optimization of hydrofoil and marine propeller due to its faster convergence. Keywords: Genetic algorithm, boundary element method, hydrofoil, propeller, design optimization Â doi: 10.3329/jname.v1i1.2038 Journal of Naval Architecture and Marine Engineering 1(2004) 47-61</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="64943">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="64944">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/2038</text>
              </elementText>
              <elementText elementTextId="64945">
                <text>10.3329/jname.v1i1.2038</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64946">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="64947">
                <text>Association of Naval Architects and Marine Engineers</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="64948">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/2038/1895</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="64949">
                <text>Journal of Naval Architecture and Marine Engineering; Vol. 1 No. 1 (2004); 47-61</text>
              </elementText>
              <elementText elementTextId="64950">
                <text>2070-8998</text>
              </elementText>
              <elementText elementTextId="64951">
                <text>1813-8535</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64952">
                <text>Genetic algorithm</text>
              </elementText>
              <elementText elementTextId="64953">
                <text>boundary element method</text>
              </elementText>
              <elementText elementTextId="64954">
                <text>hydrofoil</text>
              </elementText>
              <elementText elementTextId="64955">
                <text>propeller</text>
              </elementText>
              <elementText elementTextId="64956">
                <text>design optimization</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64957">
                <text>Optimal design of hydrofoil and marine propeller using micro-genetic algorithm (Î¼GA)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64958">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="64959">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1110" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22045">
                <text>Alkalbani, Abdullah Said</text>
              </elementText>
              <elementText elementTextId="22046">
                <text>Md Tap, Abu Osman</text>
              </elementText>
              <elementText elementTextId="22047">
                <text>Mantoro, Teddy</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="22048">
                <text>2015-01-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22049">
                <text>In this paper, popular routing protocols for Wireless Sensor Networks (WSNs) are studied. There are many issues and challenges that effect routing of data. First, high energy is consumed which reduces network lifetime. Second, security of routing path is another issue due to development in the cryptanalysis against nodes. The aim of this paper is to propose an energy aware routing approach that considers energy level for sensors during cluster heads and routing path selections. Performance, network efficiency and maximizing network lifetime are measured by simulation, analysis and comparison with other well-known mechanisms.</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="22050">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="22051">
                <text>https://online-journals.org/index.php/i-jim/article/view/4203</text>
              </elementText>
              <elementText elementTextId="22052">
                <text>10.3991/ijim.v9i1.4203</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22053">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="22054">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="22055">
                <text>https://online-journals.org/index.php/i-jim/article/view/4203/3360</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22056">
                <text>Copyright (c) 2017 Abdullah Said Alkalbani, Abu Osman Md Tap, Teddy Mantoro</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="22057">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 1 (2015); pp. 23-30</text>
              </elementText>
              <elementText elementTextId="22058">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22059">
                <text>WSNs</text>
              </elementText>
              <elementText elementTextId="22060">
                <text>Network efficiency</text>
              </elementText>
              <elementText elementTextId="22061">
                <text>Power Consumption</text>
              </elementText>
              <elementText elementTextId="22062">
                <text>Routing Protocol</text>
              </elementText>
              <elementText elementTextId="22063">
                <text>Energy Aware Routing Path</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22064">
                <text>Optimal Energy Aware Routing Path (OEARP) for Wireless Sensor Networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22065">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22066">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22067">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2392" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51458">
                <text>Maftah, Sara</text>
              </elementText>
              <elementText elementTextId="51459">
                <text>El Ghmary, Mohamed</text>
              </elementText>
              <elementText elementTextId="51460">
                <text>El Bouabidi, Hamid</text>
              </elementText>
              <elementText elementTextId="51461">
                <text>Amnai, Mohamed</text>
              </elementText>
              <elementText elementTextId="51462">
                <text>Ouacha, Ali</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="51463">
                <text>2022-10-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51464">
                <text>The appearance of Edge Computing with the possibility to bring powerful computation servers near the mobile device is a major stepping stone towards better user experience and resource consumption optimization. Due to the Internet of Things invasion that led to the constant demand for communication and computation resources, many issues were imposed in order to deliver a seamless service within an optimized cost of time and energy, since most of the applications nowadays require real response time and rely on a limited battery resource. Therefore, Mobile Edge Computing is the new reliable paradigm in terms of communication and computation consumption by the mobile devices. Mobile Edge Computing rely on computation offloading to surpass cloud-based technologies issues and break the limitations of mobile devices such as computing, storage and battery resources. However, computation offloading is not always the optimal choice to adopt, which makes the offloading decision a crucial part in which many parameters should be taken in consideration such as delegating the heavy tasks to the appropriate machine within the network by migrating the high-resource node to an edge server and lend these capabilities to the low-resources one. In this paper, we use an Edge Computing simulator to see how network delay can impact the delivery of a certain result, we also experiment computation offloading using a two-tier with Edge Orchestration architecture, which turns out to be efficient in terms of processing time.</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="51465">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="51466">
                <text>https://online-journals.org/index.php/i-jim/article/view/34373</text>
              </elementText>
              <elementText elementTextId="51467">
                <text>10.3991/ijim.v16i20.34373</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51468">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="51469">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="51470">
                <text>https://online-journals.org/index.php/i-jim/article/view/34373/12169</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51471">
                <text>Copyright (c) 2022 Sara Maftah, Mohamed El Ghmary, Hamid El Bouabidi, Mohamed Amnai, Ali Ouacha</text>
              </elementText>
              <elementText elementTextId="51472">
                <text>https://creativecommons.org/licenses/by/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="51473">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 20 (2022); pp. 130-142</text>
              </elementText>
              <elementText elementTextId="51474">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51475">
                <text>Mobile Edge Computing</text>
              </elementText>
              <elementText elementTextId="51476">
                <text>Computation offloading</text>
              </elementText>
              <elementText elementTextId="51477">
                <text>Resource optimization</text>
              </elementText>
              <elementText elementTextId="51478">
                <text>energy efficiency</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51479">
                <text>Optimal Task Processing and Energy Consumption Using Intelligent Offloading in Mobile Edge Computing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="51480">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="51481">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="51482">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2147" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45660">
                <text>Moutaib, Mohammed</text>
              </elementText>
              <elementText elementTextId="45661">
                <text>Ahajjam, Tarik</text>
              </elementText>
              <elementText elementTextId="45662">
                <text>Fattah, Mohammed</text>
              </elementText>
              <elementText elementTextId="45663">
                <text>Farhaoui, Youssef</text>
              </elementText>
              <elementText elementTextId="45664">
                <text>Aghoutane, Badraddine</text>
              </elementText>
              <elementText elementTextId="45665">
                <text>El Bekkali, Moulhime</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="45666">
                <text>2021-12-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45667">
                <text>The IoT is a growing new approach that has been defined as a global network of devices and machines capable of reliably communicating with each other without human intervention. It is one of the essential technologies in any field, such as medicine and attracts great attention in the future. It is applied in several areas that have achieved success. However, the power and the addition of connected objects to technology is based on the fact that its objects can establish several tasks: communicate, analyze, process and manage data in a parallel manner, which is very difficult in terms of energy consumption. Therefore, the problems related to consumption slow down considerably the evolution and the fast deployment of this high technology.Therefore, it is necessary to create a new lightweight and robust mechanism, which ensures the minimization of the consumption of the objects and makes these objects efficient and less costly while being adapted to the capacities of objects and technologies.That is why our paper aims to address this significant problem and present the role of energy consumption, which is essential in deploying successful IoT products and services and presenting the IoT categories for applications. First, we propose a method that minimizes energy consumption and meets our need through three essential steps: firstly, to study the existing methods to minimize energy consumption.  Next, based on these methods, we create a new concept using the data flows. Finally, we implement our solution in an intelligent parking lot to carry out our approach and describe our design steps and conclude with the result of our study and make an interpretation that summarizes our work.</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="45668">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="45669">
                <text>https://online-journals.org/index.php/i-jim/article/view/26985</text>
              </elementText>
              <elementText elementTextId="45670">
                <text>10.3991/ijim.v15i24.26985</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45671">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="45672">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="45673">
                <text>https://online-journals.org/index.php/i-jim/article/view/26985/10501</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45674">
                <text>Copyright (c) 2021 Mohammed Moutaib, Tarik AHAJJAM, Mohammed FATTAH, Youssef FARHAOUI, Badraddine AGHOUTANE, Moulhime EL BEKKALI</text>
              </elementText>
              <elementText elementTextId="45675">
                <text>https://creativecommons.org/licenses/by/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="45676">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 24 (2021); pp. 176-190</text>
              </elementText>
              <elementText elementTextId="45677">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45678">
                <text>IOT</text>
              </elementText>
              <elementText elementTextId="45679">
                <text>Cloud Computing</text>
              </elementText>
              <elementText elementTextId="45680">
                <text>RFID</text>
              </elementText>
              <elementText elementTextId="45681">
                <text>WSN.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45682">
                <text>Optimization of the Energy Consumption of Connected Objects</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="45683">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="45684">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="45685">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1733" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36134">
                <text>Yashina, Marina V.</text>
              </elementText>
              <elementText elementTextId="36135">
                <text>Tatashev, Alexander G.</text>
              </elementText>
              <elementText elementTextId="36136">
                <text>Fomina, Maria Yu.</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="36137">
                <text>2020-06-30</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36138">
                <text>In computer networks based on the principle of packet switching, the important transmitting function is to maintain packet queues and suppress congestion. Therefore, the problems of optimal control of the communication networks are relevant. For example, there are  users, and no more than a demand of one user can be served simultaneously. This paper considers a discrete dynamical system with two contours and two common points of the contours called the nodes. There are n cells and  particles, located in the cells. At any discrete moment the particles of each contour occupy neighboring cells and form a cluster. The nodes divide each contour into two parts of length  and  (non-symmetrical system). The particles move in accordance with rule of the elementary cellular automaton 240 in the Wolfram classification. Delays in the particle movement are due to that more than one particle cannot move through the node simultaneously. A competition (conflict) occurs when two clusters come to the same node simultaneously. We have proved that the spectrum of velocities contains no more than two values for any fixed n , d and l.  We have found an optimal rule which minimizes the average velocity of clusters. One of the competition clusters passes through the node first in accordance with a given competition rule. Two competition resolutions rules are introduced. The rules are called input priority and output priority resolution rules. These rules are Markovian, i.e., they takes into account only the present state of the system.  For each set of parameters n, d and l, one of these two rules is optimal, i.e., this rule maximizes the average velocity of clusters. These rules are compared with the left-priority resolution rule, which was considered earlier.  We have proved that the spectrum of velocities contains no more two values for any fixed n, l, and d. We have proved that the input priority rule is optimal if , and the output priority rule is optimal if   .</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="36139">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="36140">
                <text>https://online-journals.org/index.php/i-jim/article/view/14641</text>
              </elementText>
              <elementText elementTextId="36141">
                <text>10.3991/ijim.v14i10.14641</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36142">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="36143">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="36144">
                <text>https://online-journals.org/index.php/i-jim/article/view/14641/7351</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36145">
                <text>Copyright (c) 2020 Marina V. Yashina, Alexander G. Tatashev</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="36146">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 10 (2020); pp. 61-73</text>
              </elementText>
              <elementText elementTextId="36147">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36148">
                <text>dynamical systems</text>
              </elementText>
              <elementText elementTextId="36149">
                <text>optimal control</text>
              </elementText>
              <elementText elementTextId="36150">
                <text>self-organization</text>
              </elementText>
              <elementText elementTextId="36151">
                <text>mathematical models</text>
              </elementText>
              <elementText elementTextId="36152">
                <text>information and communication systems</text>
              </elementText>
              <elementText elementTextId="36153">
                <text>Buslaev networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36154">
                <text>Optimization of Velocity Mode in Buslaev Two-Contour Networks via Competition Resolution Rules</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="36155">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="36156">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="36157">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1571" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32398">
                <text>Christianah, Abikoye Oluwakemi</text>
              </elementText>
              <elementText elementTextId="32399">
                <text>Gyunka, Benjamin Aruwa</text>
              </elementText>
              <elementText elementTextId="32400">
                <text>Oluwatobi, Akande Noah</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="32401">
                <text>2020-06-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32402">
                <text>Android operating system has become very popular, with the highest market share, amongst all other mobile operating systems due to its open source nature and users friendliness. This has brought about an uncontrolled rise in malicious applications targeting the Android platform. Emerging trends of Android malware are employing highly sophisticated detection and analysis avoidance techniques such that the traditional signature-based detection methods have become less potent in their ability to detect new and unknown malware. Alternative approaches, such as the Machine learning techniques have taken the lead for timely zero-day anomaly detections.  The study aimed at developing an optimized Android malware detection model using ensemble learning technique. Random Forest, Support Vector Machine, and k-Nearest Neighbours were used to develop three distinct base models and their predictive results were further combined using Majority Vote combination function to produce an ensemble model. Reverse engineering procedure was employed to extract static features from large repository of malware samples and benign applications. WEKA 3.8.2 data mining suite was used to perform all the learning experiments. The results showed that Random Forest had a true positive rate of 97.9%, a false positive rate of 1.9% and was able to correctly classify instances with 98%, making it a strong base model. The ensemble model had a true positive rate of 98.1%, false positive rate of 1.8% and was able to correctly classify instances with 98.16%. The finding shows that, although the base learners had good detection results, the ensemble learner produced a better optimized detection model compared with the performances of those of the base learners.</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="32403">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="32404">
                <text>https://online-journals.org/index.php/i-jim/article/view/11548</text>
              </elementText>
              <elementText elementTextId="32405">
                <text>10.3991/ijim.v14i09.11548</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32406">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="32407">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="32408">
                <text>https://online-journals.org/index.php/i-jim/article/view/11548/7169</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32409">
                <text>Copyright (c) 2020 Akande Noah oluwatobi, Benjamin Aruwa Gyunka, Abikoye Oluwakemi Christianah</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="32410">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 09 (2020); pp. 61-78</text>
              </elementText>
              <elementText elementTextId="32411">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32412">
                <text>Android Malware Detection</text>
              </elementText>
              <elementText elementTextId="32413">
                <text>Machine Learning Models</text>
              </elementText>
              <elementText elementTextId="32414">
                <text>Base Learners</text>
              </elementText>
              <elementText elementTextId="32415">
                <text>Ensemble Learner</text>
              </elementText>
              <elementText elementTextId="32416">
                <text>Reverse Engineering</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32417">
                <text>Optimizing Android Malware Detection Via Ensemble Learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="32418">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="32419">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="32420">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="743" public="1" featured="0">
    <collection collectionId="30">
      <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="13509">
                  <text>AEGIS : Journal of International Relations</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="48">
              <name>Source</name>
              <description>A related resource from which the described resource is derived</description>
              <elementTextContainer>
                <elementText elementTextId="14704">
                  <text>School of International Relations, President University, Indonesia</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14564">
                <text>Zerlina, Andhita</text>
              </elementText>
              <elementText elementTextId="14565">
                <text>Haryono, Endi</text>
              </elementText>
              <elementText elementTextId="14566">
                <text>Elvianti, Witri</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="14567">
                <text>2016-11-24</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14568">
                <text>By the implementation of ASEAN Economic Community in 2015, all ASEAN member countriesare preparing themselves to survive in the economic competition including the aviation sector through ASEAN Open Skies Policy 2015. As the Indonesian national carrier, Garuda Indonesia has significant efforts in various sectors to support Indonesia in ASEAN Open Skies Policy 2015. The focus of this research is to critically examine the implementation of Garuda Indonesia’s Quantum Leap Program in supporting Indonesia in the implementation of ASEAN Open Sky Policy in 2015. This research also refers to several concepts such as regionalism and cultural diplomacy to explain the phenomenon of ASEAN Economic Community in which Garuda Indonesia displays its roles to promote Indonesia to foreign public.</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="14569">
                <text>application/pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="43">
            <name>Identifier</name>
            <description>An unambiguous reference to the resource within a given context</description>
            <elementTextContainer>
              <elementText elementTextId="14570">
                <text>http://e-journal.president.ac.id/presunivojs/index.php/AEGIS/article/view/75</text>
              </elementText>
              <elementText elementTextId="14571">
                <text>10.33021/aegis.v1i1.75</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14572">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="14573">
                <text>President University</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="14574">
                <text>http://e-journal.president.ac.id/presunivojs/index.php/AEGIS/article/view/75/58</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14575">
                <text>Copyright (c) 2016 AEGIS : Journal of International Relations</text>
              </elementText>
              <elementText elementTextId="14576">
                <text>http://creativecommons.org/licenses/by-nc/4.0</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="48">
            <name>Source</name>
            <description>A related resource from which the described resource is derived</description>
            <elementTextContainer>
              <elementText elementTextId="14577">
                <text>AEGIS : Journal of International Relations; Vol 1, No 1 (2016): September 2016 - February 2017</text>
              </elementText>
              <elementText elementTextId="14578">
                <text>2548-4532</text>
              </elementText>
              <elementText elementTextId="14579">
                <text>2541-1373</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14580">
                <text>OPTIMIZING THE IMPLEMENTATION OF QUANTUM LEAP PROGRAM TO FACE THE CHALLENGES OF ASEAN OPEN SKY POLICY: LESSONS FROM GARUDA INDONESIA</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="14581">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="14582">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
