<?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=30&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-02T00:24:45+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>30</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="2309" 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="49490">
                <text>Ariffin, Shamsul Arrieya</text>
              </elementText>
              <elementText elementTextId="49491">
                <text>Fathil, Nur Saadah</text>
              </elementText>
              <elementText elementTextId="49492">
                <text>Yatim, Maizatul Hayati Mohamad</text>
              </elementText>
              <elementText elementTextId="49493">
                <text>Samsuri, Muhammad Zulhilmi</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="49494">
                <text>2022-08-17</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49495">
                <text>This study examined the existing use of cultural design elements in design guidelines for mobile applications. Cultural design elements are used to include cultural values in the development of mobile applications. A review of existing design guidelines was conducted to identify cultural design elements practicality pertaining to the mobile application. The keywords "Application", "Design Guidelines", and "User Interface" were searched on ACM Digital Library, IEEE Xplore, and Scopus between 2017 and 2021, including 2022, with 281 articles before filtering and 3 articles selected after filtering. This review shows that cultural design elements in the mobile application played an important role in getting a high usability rate for user’s use. Although it is an important element, its use is still limited usage in the development of mobile applications. As a result, future research will focus on developing guidelines for mobile applications with cultural design elements appropriate for today's technological era in a local context.</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="49496">
                <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="49497">
                <text>https://online-journals.org/index.php/i-jim/article/view/30851</text>
              </elementText>
              <elementText elementTextId="49498">
                <text>10.3991/ijim.v16i15.30851</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49499">
                <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="49500">
                <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="49501">
                <text>https://online-journals.org/index.php/i-jim/article/view/30851/11821</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49502">
                <text>Copyright (c) 2022 Mr Muhammad Zulhilmi Samsuri, Shamsul Arrieya Ariffin, Nur Saadah Fathil</text>
              </elementText>
              <elementText elementTextId="49503">
                <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="49504">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 16 No. 15 (2022); pp. 78-92</text>
              </elementText>
              <elementText elementTextId="49505">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49506">
                <text>mobile application, user interface, cultural design element, design guidelines</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49507">
                <text>A Review on Cultural Design Elements for Mobile Applications User Interface</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="49508">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="49509">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="49510">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3328" 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="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="68357">
                <text>India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68358">
                <text>Syriac, Robin</text>
              </elementText>
              <elementText elementTextId="68359">
                <text>Prakash, M N Senthil</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="68360">
                <text>2023-01-02</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68361">
                <text>There are ever-increasing efforts on utilising non-conventional energy resources so as to reduce the global carbon footprint and reduce pollution caused by extensive use of energy from conventional sources. At the same time, the energy extraction from the abundant marine renewable energy resources available offshore need more development due to difference in the levelized cost of energy (LCOE) compared to energy extracted onshore, though the difference in the cost of energy is getting reduced faster than expected. Meanwhile hundreds of offshore platforms already existing in oil and gas industry will undergo decommissioning at the end of its life; which will require the platform to be removed or reused. In this context, the reuse possibility of such decommissioned offshore platforms to be used as support structures for marine renewable energy applications is examined. This paper presents a review on the research efforts on this topic and a discussion on the various aspects involved in the possible reuse of decommissioned offshore fixed platforms for marine renewable energy applications.
Journal of Naval Architecture and Marine Engineering Vol 19(2), December, 2022 p. 71-82</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="68362">
                <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="68363">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/50359</text>
              </elementText>
              <elementText elementTextId="68364">
                <text>10.3329/jname.v19i2.50359</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68365">
                <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="68366">
                <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="68367">
                <text>https://www.banglajol.info/index.php/JNAME/article/view/50359/44095</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68368">
                <text>Copyright (c) 2022 Journal of Naval Architecture and Marine Engineering</text>
              </elementText>
              <elementText elementTextId="68369">
                <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="68370">
                <text>Journal of Naval Architecture and Marine Engineering; Vol. 19 No. 2 (2022); 71-82</text>
              </elementText>
              <elementText elementTextId="68371">
                <text>2070-8998</text>
              </elementText>
              <elementText elementTextId="68372">
                <text>1813-8535</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68373">
                <text>Marine renewable energy, offshore fixed platforms, reuse, decommissioning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68374">
                <text>A review on the reuse possibilities of decommissioned offshore fixed platforms for marine renewable energy applications</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="68375">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="68376">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1987" 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="41906">
                <text>Ramya, Govindaraj</text>
              </elementText>
              <elementText elementTextId="41907">
                <text>Priya, Govindaraj</text>
              </elementText>
              <elementText elementTextId="41908">
                <text>Subrata, Chowdhury</text>
              </elementText>
              <elementText elementTextId="41909">
                <text>Kim, Dohyeun</text>
              </elementText>
              <elementText elementTextId="41910">
                <text>Tran, Duc Tan</text>
              </elementText>
              <elementText elementTextId="41911">
                <text>Le, Anh Ngoc</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="41912">
                <text>2021-05-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41913">
                <text>The extremely vibrant, scattered, and non–transparent nature of cloud computing formulate trust management a significant challenge. According to scholars the trust and security are the two issues that are in the topmost obstacles for adopting cloud computing. Also, SLA (Service Level Agreement) alone is not necessary to build trust between cloud because of vague and unpredictable clauses. Getting feedback from the consumers is the best way to know the trustworthiness of the cloud services, which will help them improve in the future. Several researchers have stated the necessity of building a robust management system and suggested many ideas to manage trust based on consumers' feedback. This paper has reviewed various reputation-based trust management systems, including trust management in cloud computing, peer-to-peer system, and Adhoc system. </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="41914">
                <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="41915">
                <text>https://online-journals.org/index.php/i-jim/article/view/21645</text>
              </elementText>
              <elementText elementTextId="41916">
                <text>10.3991/ijim.v15i10.21645</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41917">
                <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="41918">
                <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="41919">
                <text>https://online-journals.org/index.php/i-jim/article/view/21645/9255</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41920">
                <text>Copyright (c) 2021 Govindaraj Ramya, Govindaraj Priya, Chowdhury Subrata, Dohyeun Kim, Anh Ngoc Le</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="41921">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 15 No. 10 (2021); pp. 87-102</text>
              </elementText>
              <elementText elementTextId="41922">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41923">
                <text>Reputation</text>
              </elementText>
              <elementText elementTextId="41924">
                <text>Trust management</text>
              </elementText>
              <elementText elementTextId="41925">
                <text>Recommendation.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41926">
                <text>A Review on Various Applications of Reputation Based Trust Management</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="41927">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="41928">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="41929">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1796" 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="37543">
                <text>Hamad, Ibrahim Ismael</text>
              </elementText>
              <elementText elementTextId="37544">
                <text>Hasan, Mohammad S.</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="37545">
                <text>2020-11-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="37546">
                <text>Abstract-The path planning for Multi Mobile Robotic (MMR) system is a recent combinatorial optimisation problem. In the last decade, many researches have been published to solve this problem. Most of these researches focused on metaheuristic algorithms. This paper reviews articles on Ant Colony Optimisation (ACO) and its hybrid versions to solve the problem. The original Dorigo’s ACO algorithm uses exploration and exploitation phases to find the shortest route in a combinatorial optimisation problem in general without touching mapping, localisation and perception. Due to the properties of MMR, adaptations have been made to ACO algorithms. In this review paper, a literature survey of the recent studies on upgrading, modifications and applications of the ACO algorithms has been discussed to evaluate the application of the different versions of ACO in the MMR domain. The evaluation considered the quality, speed of convergence, robustness, scalability, flexibility of MMR and obstacle avoidance, static and dynamic environment characteristics of the tasks.</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="37547">
                <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="37548">
                <text>https://online-journals.org/index.php/i-jim/article/view/16371</text>
              </elementText>
              <elementText elementTextId="37549">
                <text>10.3991/ijim.v14i18.16371</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="37550">
                <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="37551">
                <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="37552">
                <text>https://online-journals.org/index.php/i-jim/article/view/16371/8137</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="37553">
                <text>Copyright (c) 2020 Ibrahim Ismael Hamad, Mohammad S. Hasan</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="37554">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 18 (2020); pp. 145-156</text>
              </elementText>
              <elementText elementTextId="37555">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="37556">
                <text>Multi-Robotics</text>
              </elementText>
              <elementText elementTextId="37557">
                <text>path planning (PP)</text>
              </elementText>
              <elementText elementTextId="37558">
                <text>ACO algorithm</text>
              </elementText>
              <elementText elementTextId="37559">
                <text>Metaheuristics. uncer-tainties</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="37560">
                <text>A Review: On using ACO Based Hybrid Algorithms for Path Planning of Multi-Mobile Robotics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="37561">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="37562">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="37563">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="592" 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="11888">
                <text>Curtotti, Michael</text>
              </elementText>
              <elementText elementTextId="11889">
                <text>McCreath, Eric</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="11890">
                <text>2013-12-18</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11891">
                <text>The widespread availability of legal materials online has opened the law to a new and greatly expanded readership. These new readers need the law to be readable by them when they encounter it. However, the available empirical research supports a conclusion that legislation is difficult to read if not incomprehensible to most citizens. We review approaches that have been used to measure the readability of text including readability metrics, cloze testing and application of machine learning. We report the creation and testing of an open online platform for readability research. This platform is made available to researchers interested in undertaking research on the readability of legal materials. To demonstrate the capabilities ofthe platform, we report its initial application to a corpus of legislation. Linguistic characteristics are extracted using the platform and then used as input features for machine learning using the Weka package. Wide divergences are found between sentences in a corpus of legislation and those in a corpus of graded reading material or in the Brown corpus (a balanced corpus of English written genres). Readability metrics are found to be of little value in classifying sentences by grade reading level (noting that such metrics were not designed to be used with isolated sentences).</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="11892">
                <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="11893">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11894">
                <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="11895">
                <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="11896">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/16/17</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="11897">
                <text>Journal of Open Access to Law; Vol. 1 No. 1 (2013)</text>
              </elementText>
              <elementText elementTextId="11898">
                <text>2372-7152</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11899">
                <text>readability</text>
              </elementText>
              <elementText elementTextId="11900">
                <text>legislation</text>
              </elementText>
              <elementText elementTextId="11901">
                <text>legal informatics</text>
              </elementText>
              <elementText elementTextId="11902">
                <text>corpus linguistics</text>
              </elementText>
              <elementText elementTextId="11903">
                <text>machine learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11904">
                <text>A Right to Access Implies A Right to Know: An Open Online Platform for Research on the Readability of Law</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11905">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="11906">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="11907">
                <text>Peer-reviewed article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1411" 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="28724">
                <text>Obeidat, Ibrahim</text>
              </elementText>
              <elementText elementTextId="28725">
                <text>Mughaid, Ala</text>
              </elementText>
              <elementText elementTextId="28726">
                <text>Alzoubi, Shadi</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="28727">
                <text>2019-05-21</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28728">
                <text>Abstract Users in the same network can trace the data being transmitted amongst users and other users to the internet using many available online tools such as packet sniffers and many packets capturing tools, the need to make the data resistible to be read comes obvious. The proposed solution is to encrypt the data using inscription algorithm. In this paper, we propose a solution to protect Network Clients from other Clients in the same network.</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="28729">
                <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="28730">
                <text>https://online-journals.org/index.php/i-jim/article/view/9845</text>
              </elementText>
              <elementText elementTextId="28731">
                <text>10.3991/ijim.v13i05.9845</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28732">
                <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="28733">
                <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="28734">
                <text>https://online-journals.org/index.php/i-jim/article/view/9845/5675</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28735">
                <text>Copyright (c) 2019 Ibrahim obeidat</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="28736">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 05 (2019); pp. 47-57</text>
              </elementText>
              <elementText elementTextId="28737">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28738">
                <text>Keywords</text>
              </elementText>
              <elementText elementTextId="28739">
                <text>Introduction</text>
              </elementText>
              <elementText elementTextId="28740">
                <text>Network Clients</text>
              </elementText>
              <elementText elementTextId="28741">
                <text>Security</text>
              </elementText>
              <elementText elementTextId="28742">
                <text>Cryptography</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28743">
                <text>A Secure Encrypted Protocol for Clients' Handshaking in the Same Network</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="28744">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="28745">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="28746">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2493" 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="53856">
                <text>Gashi, Luan</text>
              </elementText>
              <elementText elementTextId="53857">
                <text>Luma, Artan</text>
              </elementText>
              <elementText elementTextId="53858">
                <text>Snopçe, Halil</text>
              </elementText>
              <elementText elementTextId="53859">
                <text>Januzaj, Ylber</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="53860">
                <text>2023-06-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="53861">
                <text>Edge or fog computing are being used to reduce latency between end devices and traditional cloud computing. The latest developments that have improved the hardware aspects of wireless sensors and mobile networks, gave the opportunity for other enhancements if such technologies are integrated between them. Regarding this enhanced heterogeneous environment, the approach of placing services needs to reconsider the security aspects. We have developed a baseline method of a solution which fulfills the cybersecurity requirements converging with the proposed multi-tier integrated model, that enhances the K-means algorithm with added processing steps supplying the criteria of the CIA triad.</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="53862">
                <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="53863">
                <text>https://online-journals.org/index.php/i-jim/article/view/37369</text>
              </elementText>
              <elementText elementTextId="53864">
                <text>10.3991/ijim.v17i11.37369</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="53865">
                <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="53866">
                <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="53867">
                <text>https://online-journals.org/index.php/i-jim/article/view/37369/13295</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="53868">
                <text>Copyright (c) 2023 Luan Gashi, Artan Luma, Halil Snopçe, Ylber Januzaj</text>
              </elementText>
              <elementText elementTextId="53869">
                <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="53870">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 17 No. 11 (2023); pp. 115-130</text>
              </elementText>
              <elementText elementTextId="53871">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="53872">
                <text>networks service placement, fog and edge clustering, wireless networks, mobile com-munication, CIA triad</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="53873">
                <text>A Secure Recommender System Model for Service Placement in Wireless Networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="53874">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="53875">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="53876">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="844" 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="16508">
                <text>Yau, Jane</text>
              </elementText>
              <elementText elementTextId="16509">
                <text>Joy, Mike</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="16510">
                <text>2008-03-07</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16511">
                <text>Self-regulated students are able to create and maximize opportunities they have for studying or learning. We combine this learning approach with our Mobile Context-aware and Adaptive Learning Schedule (mCALS) tool which will create and enhance opportunities for students to study or learn in different locations. The learning schedule is used for two purposes, a) to help students organize their work and facilitate time management, and b) for capturing the usersâ?? activities which can be retrieved and translated as learning contexts later by our tool. These contexts are then used as a basis for selecting appropriate learning materials for the students. Using a learning schedule to capture and retrieve contexts is a novel approach in the context-aware mobile learning field. In this paper, we present the conceptual model and preliminary architecture of our mCALS tool, as well as our research questions and methodology for evaluating it. The learning materials we intend to use for our tool will be Java for novice programmers. This is appropriate because large amounts of time and motivation are necessary to learn an object-oriented programming language such as Java, and we are currently seeking ways to facilitate this for novice programmers.</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="16512">
                <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="16513">
                <text>https://online-journals.org/index.php/i-jim/article/view/268</text>
              </elementText>
              <elementText elementTextId="16514">
                <text>10.3991/ijim.v2i3.268</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16515">
                <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="16516">
                <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="16517">
                <text>https://online-journals.org/index.php/i-jim/article/view/268/480</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16518">
                <text>Copyright (c) 2017 Jane Yau, Mike Joy</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="16519">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 2 No. 3 (2008); pp. 52-57</text>
              </elementText>
              <elementText elementTextId="16520">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16521">
                <text>Context-aware</text>
              </elementText>
              <elementText elementTextId="16522">
                <text>Learning Schedule</text>
              </elementText>
              <elementText elementTextId="16523">
                <text>Mobile Learning</text>
              </elementText>
              <elementText elementTextId="16524">
                <text>Learning Java programming</text>
              </elementText>
              <elementText elementTextId="16525">
                <text>Learning Objects</text>
              </elementText>
              <elementText elementTextId="16526">
                <text>Self-Regulated Learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16527">
                <text>A Self-Regulated Learning Approach: A Mobile Context-aware and Adaptive Learning Schedule (mCALS) Tool</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="16528">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="16529">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1225" 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="24580">
                <text>AbdelFattah, Mohamed</text>
              </elementText>
              <elementText elementTextId="24581">
                <text>Galal, Dahab</text>
              </elementText>
              <elementText elementTextId="24582">
                <text>Hassan, Nada</text>
              </elementText>
              <elementText elementTextId="24583">
                <text>Elzanfaly, Doaa</text>
              </elementText>
              <elementText elementTextId="24584">
                <text>Tallent, Greg</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="24585">
                <text>2017-04-11</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24586">
                <text>Sentiment Analysis (SA) or Opinion Mining is the process of analysing natural language texts to detect an emotion or a pattern of emotions towards a certain product to make a decision about that product. SA is a topic of text mining, Natural Language Processing (NLP) and web mining disciplines. Research in SA is currently at its peak given the amount of data generated from social media networks. The concept is that consumers are expressing exactly what they need, want and expect from a product but on the other hand the companies don’t have the tools to analyse and understand these feelings to satisfy these consumers accordingly. One of the applications that generate a high rate of reactions and sentiments in social networks is Instagram. This study focuses on analysing the reactions generated by the top 50 fashion houses on Instagram given their top 20 images with the highest number of likes. The approach taken in this study is to qualify the visual aesthetics of fashion images and to establish why some succeed on social media more than others. The basic question asked in this paper is whether there are certain visual aesthetics that appeal more to the user and are therefore more successful on social media than others as determined by a measure we introduce, ‘Social Value’. To do so, a sentiment analysis tool is developed to measure the proposed social value of each image. An input of comments from each image will be processed. Each comment will go through a pre-processing phase; each word will be placed through a lexicon to identify if it is positive or negative. The output of the lexicon is a score value assigned to each comment to identify its degree of positivity, negativity, or it has no effect on the social value. Adding to these results, the number of likes and shares would also be taken into consideration quantifying the image’s value. A cumulative result is then produced to determine the social value of an image.</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="24587">
                <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="24588">
                <text>https://online-journals.org/index.php/i-jim/article/view/6563</text>
              </elementText>
              <elementText elementTextId="24589">
                <text>10.3991/ijim.v11i2.6563</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24590">
                <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="24591">
                <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="24592">
                <text>https://online-journals.org/index.php/i-jim/article/view/6563/4355</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24593">
                <text>Copyright (c) 2017 Mohamed AbdelFattah, Dahab Galal, Nada Hassan, Doaa Elzanfaly, Greg Tallent</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="24594">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 11 No. 2 (2017); pp. 66-73</text>
              </elementText>
              <elementText elementTextId="24595">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24596">
                <text>Sentiment Analysis</text>
              </elementText>
              <elementText elementTextId="24597">
                <text>Opinion Mining</text>
              </elementText>
              <elementText elementTextId="24598">
                <text>Instagram</text>
              </elementText>
              <elementText elementTextId="24599">
                <text>Social Value</text>
              </elementText>
              <elementText elementTextId="24600">
                <text>Aesthetics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24601">
                <text>A Sentiment Analysis Tool for Determining the Promotional Success of Fashion Images on Instagram</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="24602">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="24603">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="24604">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="975" 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="19251">
                <text>Ismail, Mohammad</text>
              </elementText>
              <elementText elementTextId="19252">
                <text>Che Razak, Razli</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="19253">
                <text>2011-06-27</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19254">
                <text>The purpose of this paper is to elucidate the major classification of the research in mobile marketing. It provides the trend and common approach in mobile marketing research.  The paper aims to highlight the significant area in mobile marketing research and the needs for further understanding of the mobile marketing definition and its phenomenon. This paper has significant implications in terms of understanding the classification and the mobile marketing focusing area.  This is a general review based on selected approximately forty-six journal publications which are published between year 2005 until 2010 from selected journals. Based on the selected reviewed literatures, the consumersâ?? adoption research only focuses on a few common areas. There is no agreement among the researchers on definition of mobile marketing and the conceptualization and phenomenon of mobile marketing remain unexplained. The value of this paper is that, it provides the fundamental guidelines for researchers on significant area to focus in the mobile marketing field and it also assists practitioners in identifying the research trend and major classifications which will assist them in designing the product and services to the right target market.</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="19255">
                <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="19256">
                <text>https://online-journals.org/index.php/i-jim/article/view/1581</text>
              </elementText>
              <elementText elementTextId="19257">
                <text>10.3991/ijim.v5i3.1581</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19258">
                <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="19259">
                <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="19260">
                <text>https://online-journals.org/index.php/i-jim/article/view/1581/1815</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19261">
                <text>Copyright (c) 2017 Mohammad Ismail, Razli Che Razak</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="19262">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 5 No. 3 (2011); pp. 38-42</text>
              </elementText>
              <elementText elementTextId="19263">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19264">
                <text>Mobile marketing</text>
              </elementText>
              <elementText elementTextId="19265">
                <text>Consumer Adoption</text>
              </elementText>
              <elementText elementTextId="19266">
                <text>Consumer Acceptance</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19267">
                <text>A Short Review on the Trend of Mobile Marketing Studies</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="19268">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="19269">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="19270">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
