<?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://www.autokrew.com/igi.indrastra.com/items/browse?collection=36&amp;output=omeka-xml&amp;page=111" accessDate="2026-06-08T04:56:18+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>111</pageNumber>
      <perPage>10</perPage>
      <totalResults>1739</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="1454" 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="29708">
                <text>Nabeel, Nubila</text>
              </elementText>
              <elementText elementTextId="29709">
                <text>Habaebi, Mohamed Hadi</text>
              </elementText>
              <elementText elementTextId="29710">
                <text>Che Mustapha, Nurul Arfah</text>
              </elementText>
              <elementText elementTextId="29711">
                <text>Islam, Md Rafiqul</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="29712">
                <text>2019-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29713">
                <text>We are in the era of IoT and 5G technologies. IoT has wide range of applications in Smart Home, Smart cities, Agriculture, Health etc. Due to that, the number of connected sensor devices become increased. Along with that security of these devices become a challenging issue. By the next year there would be a great increase in the number of connected sensor devices. For the power constrained devices like sensors and actuators, they requires lightweight security mechanism. There are several Lightweight (LW) energy efficient Hashing techniques are available. They are photon, quark, spongent, Lesamnta-LW etc. These all are fixed length block sized and key sized LW hashing techniques. All transformation methods used today in LW hash function only support fixed block size and key size and requires high hardware requirements too. In this paper, we compare different types of LW hash families in terms of their design and introduce the possibility of variable length hash function using Mersenne number based transform.</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="29714">
                <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="29715">
                <text>https://online-journals.org/index.php/i-jim/article/view/10524</text>
              </elementText>
              <elementText elementTextId="29716">
                <text>10.3991/ijim.v13i04.10524</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29717">
                <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="29718">
                <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="29719">
                <text>https://online-journals.org/index.php/i-jim/article/view/10524/5593</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29720">
                <text>Copyright (c) 2019 Nubila Nabeel</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="29721">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 04 (2019); pp. 117-129</text>
              </elementText>
              <elementText elementTextId="29722">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29723">
                <text>Diffusion</text>
              </elementText>
              <elementText elementTextId="29724">
                <text>lightweight hashing techniques</text>
              </elementText>
              <elementText elementTextId="29725">
                <text>Mersenne number</text>
              </elementText>
              <elementText elementTextId="29726">
                <text>energy efficiency.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29727">
                <text>IoT Light Weight (LWT) Crypto Functions</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29728">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29729">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29730">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1453" 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="29679">
                <text>Ghazali, Osman</text>
              </elementText>
              <elementText elementTextId="29680">
                <text>Yang Leow, Chun</text>
              </elementText>
              <elementText elementTextId="29681">
                <text>Qaiser, Shahzad</text>
              </elementText>
              <elementText elementTextId="29682">
                <text>Pattabiraman, Nanthini</text>
              </elementText>
              <elementText elementTextId="29683">
                <text>Vasuthevan, Sathiyaroobaa</text>
              </elementText>
              <elementText elementTextId="29684">
                <text>Abdusalam, Eman Mohamed</text>
              </elementText>
              <elementText elementTextId="29685">
                <text>M. Barakat, Mustafa</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="29686">
                <text>2019-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29687">
                <text>Customer disposition to data, nature of the information on site, protection concerns, trust, security concerns, and the notoriety of organization efficaciously affect the trust of Internet shoppers in the site. Two noteworthy and basic issues for e-commerce sites and consumers are trust as well as security. A belief that someone is good and honest and will not harm you, or something is safe and reliable is called trust; while security is an attempt to safeguard the data from unauthorized access. Information security is a vital management as well as technical requirement over the internet for effective and secure payment transaction activities. The safety of e-commerce resources from use, destruction, unauthorized access and alteration is known as E-commerce security so there is an urgent need to study its dimensions such as authenticity, integrity, availability, privacy, confidentiality and non-repudiation. This paper reports a review of four popular online marketplaces which are Alibaba, Amazon, eBay andTaoBao as case study on two main criteria namely building trust among users and ensuring security on the platform. Furthermore, we discuss the methods being used by each online marketplace to build trust and their unique way ofimproving the security. Finally, different ways of building trust and technique to ensure the security is presented in a tabular form for each online marketplace.</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="29688">
                <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="29689">
                <text>https://online-journals.org/index.php/i-jim/article/view/10523</text>
              </elementText>
              <elementText elementTextId="29690">
                <text>10.3991/ijim.v13i04.10523</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29691">
                <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="29692">
                <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="29693">
                <text>https://online-journals.org/index.php/i-jim/article/view/10523/5591</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29694">
                <text>Copyright (c) 2019 Osman Ghazali</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="29695">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 04 (2019); pp. 96-116</text>
              </elementText>
              <elementText elementTextId="29696">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29697">
                <text>Building trust</text>
              </elementText>
              <elementText elementTextId="29698">
                <text>marketplaces</text>
              </elementText>
              <elementText elementTextId="29699">
                <text>trust</text>
              </elementText>
              <elementText elementTextId="29700">
                <text>risk</text>
              </elementText>
              <elementText elementTextId="29701">
                <text>behavior</text>
              </elementText>
              <elementText elementTextId="29702">
                <text>security</text>
              </elementText>
              <elementText elementTextId="29703">
                <text>e-commerce</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29704">
                <text>Cloud-Based Global Online Marketplaces Review on Trust and Security</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29705">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29706">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29707">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1452" 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="29656">
                <text>M, Khairudin</text>
              </elementText>
              <elementText elementTextId="29657">
                <text>A.K, Triatmaja</text>
              </elementText>
              <elementText elementTextId="29658">
                <text>W.J, Istanto</text>
              </elementText>
              <elementText elementTextId="29659">
                <text>M.N.A, Azman</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="29660">
                <text>2019-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29661">
                <text>This paper provides development of a virtual laboratorium for the subject of digital engineering. The virtual digital engineering laboratory based on mobile virtual reality is a finding that can be used for replacing a real laboratory. Using a virtual laboratory can be conducted a learning and teaching process at anytime and anywhere as long as it has an android device. This study applies a virtual laboratory to mobile virtual reality for a virtual digital engineering laboratory. The results of this study were fuctional application software to learn how to apply a virtual digital engineering laboratory through mobile virtual reality technology. A lot of components and circuits of logic gate can be simulated in this virtual laboratorium. This study presents a simple Android-based virtual tools for the visualization and investigation  in real time of circuits of logic gates without signal disturbances. The package can be used as an educational tool in various lectures or homework to aid teaching digital engineering theory or practically.</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="29662">
                <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="29663">
                <text>https://online-journals.org/index.php/i-jim/article/view/10522</text>
              </elementText>
              <elementText elementTextId="29664">
                <text>10.3991/ijim.v13i04.10522</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29665">
                <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="29666">
                <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="29667">
                <text>https://online-journals.org/index.php/i-jim/article/view/10522/5592</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29668">
                <text>Copyright (c) 2019 Khairudin M</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="29669">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 04 (2019); pp. 80-95</text>
              </elementText>
              <elementText elementTextId="29670">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29671">
                <text>Virtual laboratorium</text>
              </elementText>
              <elementText elementTextId="29672">
                <text>virtual reality</text>
              </elementText>
              <elementText elementTextId="29673">
                <text>mobile</text>
              </elementText>
              <elementText elementTextId="29674">
                <text>digital engineering</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29675">
                <text>Mobile Virtual Reality to Develop a Virtual Laboratorium for the Subject of Digital Engineering</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29676">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29677">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29678">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1451" 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="29630">
                <text>Adib Azhar, Mohamad</text>
              </elementText>
              <elementText elementTextId="29631">
                <text>Mohd Saudi, Madihah</text>
              </elementText>
              <elementText elementTextId="29632">
                <text>Ahmad, Azuan</text>
              </elementText>
              <elementText elementTextId="29633">
                <text>Abu Bakar, Azreena</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="29634">
                <text>2019-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29635">
                <text>Internet users all over the world are highly exposed to social media exploitation, where they are vulnerable to be targeted by this cyber-attack. Furthermore, excessive use of social media leads to Internet Addiction Disorder (IAD). Fortunately, social media exploitation and IAD can be monitored and controlled closely based on user’s mobile phone surveillance features which are camera, SMS, audio, geolocation (GPS) and call log. Hence to overcome these challenges, this paper presents five (5) Application Programming Interfaces (APIs) and four (4) permissions for SMS and camera that are mostly and widely used with the social media applications. These 9 APIs and permissions matched with 2.7% of the APIs and permissions training dataset that are related with SMS and camera. This experiment was conducted by using hybrid analysis, which inclusive of static analysis and dynamic analysis, with 1926 training dataset from Brunswick. These 9 APIs and permissions, if being misused by the attacker, could lead to privacy concerns of a mobile device. The finding from this paper can be used as a guidance and reference for the formation of new mobile malware detection technique and modeling in future.</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="29636">
                <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="29637">
                <text>https://online-journals.org/index.php/i-jim/article/view/10521</text>
              </elementText>
              <elementText elementTextId="29638">
                <text>10.3991/ijim.v13i04.10521</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29639">
                <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="29640">
                <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="29641">
                <text>https://online-journals.org/index.php/i-jim/article/view/10521/5590</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29642">
                <text>Copyright (c) 2019 Mohamad Adib Azhar</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="29643">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 04 (2019); pp. 61-79</text>
              </elementText>
              <elementText elementTextId="29644">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29645">
                <text>Social media exploitation</text>
              </elementText>
              <elementText elementTextId="29646">
                <text>API</text>
              </elementText>
              <elementText elementTextId="29647">
                <text>permission</text>
              </elementText>
              <elementText elementTextId="29648">
                <text>SMS</text>
              </elementText>
              <elementText elementTextId="29649">
                <text>camera</text>
              </elementText>
              <elementText elementTextId="29650">
                <text>mobile malwares</text>
              </elementText>
              <elementText elementTextId="29651">
                <text>mobile phone surveillance feature</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29652">
                <text>Detection of Social Media Exploitation via SMS and Camera</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29653">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29654">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29655">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1450" 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="29604">
                <text>Ahmed, Muhammed Zaharadeen</text>
              </elementText>
              <elementText elementTextId="29605">
                <text>Abdalla Hashim, Aisha Hassan</text>
              </elementText>
              <elementText elementTextId="29606">
                <text>O. Khalifa, Othman</text>
              </elementText>
              <elementText elementTextId="29607">
                <text>H. Alkali, Abdulkadir</text>
              </elementText>
              <elementText elementTextId="29608">
                <text>Bt Midi, Nur Shahida</text>
              </elementText>
              <elementText elementTextId="29609">
                <text>Abd. Rahman, Faridah Bt</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="29610">
                <text>2019-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29611">
                <text>Named Data Networking (NDN) performs its routing and forwarding decisions using name prefixes. This removes some of the issues affecting addresses in our traditional IP architecture such as limitation in address allocation and management, and even NAT translations etcetera. Another positivity of NDN is its ability to use the conventional routing like the link state and distance vector algorithm. In route announcement, NDN node broadcasts its name prefix which consists of the knowledge of the next communicating node. In this paper, we evaluate the performance of mobility management models used in forwarding NDN contents to a next hop. This makes it crucial to select an approach of mobility model that translates the nature of movement of the NDN mobile routers. A detailed analysis of the famous mobility model such as the Random Waypoint mobility and Constant Velocity were computed to determine the mobility rate of the NDN mobile router. Simulation analysis was carried out using ndnSIM 2.1 on Linux Version 16.1. we build and compile with modules and libraries in NS-3.29. The sample of movement of the mobile router is illustrated and our result present the viability of the Constant Velocity model as compared with the Random Way point.</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="29612">
                <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="29613">
                <text>https://online-journals.org/index.php/i-jim/article/view/10519</text>
              </elementText>
              <elementText elementTextId="29614">
                <text>10.3991/ijim.v13i04.10519</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29615">
                <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="29616">
                <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="29617">
                <text>https://online-journals.org/index.php/i-jim/article/view/10519/5589</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29618">
                <text>Copyright (c) 2019 Muhammed Zaharadeen Ahmed</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="29619">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 04 (2019); pp. 47-60</text>
              </elementText>
              <elementText elementTextId="29620">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29621">
                <text>Named Data Networking</text>
              </elementText>
              <elementText elementTextId="29622">
                <text>Prefix</text>
              </elementText>
              <elementText elementTextId="29623">
                <text>Broadcast</text>
              </elementText>
              <elementText elementTextId="29624">
                <text>ndnSIM</text>
              </elementText>
              <elementText elementTextId="29625">
                <text>NS-3.29</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29626">
                <text>Evaluating Mobility Management Models for Content Forwarding in Named Data Networking Environments</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29627">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29628">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29629">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1449" 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="29583">
                <text>Zenalden, Feras</text>
              </elementText>
              <elementText elementTextId="29584">
                <text>Hassan, Suhaidi</text>
              </elementText>
              <elementText elementTextId="29585">
                <text>Habbal, Adib</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="29586">
                <text>2019-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29587">
                <text>Device-to-Device (D2D) communication is an important component of the 5G mobile networks. D2D communication enables users to communicate either directly without network assistance or with minimum signalling information through a base station (BS). Hence, D2D communication can enhance system capacity, increase spectral efficiency, improve throughput and reduce latency. One of the main challenges in D2D communications that when a potential D2D pair can switch between direct and conventional cellular communications, there lies a challenge in identifying D2D mode selection between communicating devices (i.e. a D2D pair). This paper aims to evaluate the mode selection mechanism in different environments (indoor, outdoor). The mode selection mechanism is proposed using multi-criteria for decision-making technique, the mode selection mechanism based on Simple Additive Weighting (SAW) algorithm is used to wisely connect and switch between the available modes. The evaluation of the proposed mechanism for indoor environment and outdoor environment shows better performance based on user preferences.</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="29588">
                <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="29589">
                <text>https://online-journals.org/index.php/i-jim/article/view/10518</text>
              </elementText>
              <elementText elementTextId="29590">
                <text>10.3991/ijim.v13i04.10518</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29591">
                <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="29592">
                <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="29593">
                <text>https://online-journals.org/index.php/i-jim/article/view/10518/5588</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29594">
                <text>Copyright (c) 2019 Feras Zenalden</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="29595">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 04 (2019); pp. 33-46</text>
              </elementText>
              <elementText elementTextId="29596">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29597">
                <text>Device-to-Device</text>
              </elementText>
              <elementText elementTextId="29598">
                <text>Mode Selection</text>
              </elementText>
              <elementText elementTextId="29599">
                <text>Fifth Generation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29600">
                <text>Mode Selection Mechanism to Enable Effective Device-to-Device Communication System over Different Environments</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29601">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29602">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29603">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1448" 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="29562">
                <text>Annane, Boubakeur</text>
              </elementText>
              <elementText elementTextId="29563">
                <text>Ghazali, Osman</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="29564">
                <text>2019-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29565">
                <text>The principle constraints of mobile devices are their limited resources such as processing capability, storage space and battery life. While cloud computing offers a vast computing resources services. A new idea emerged by including the cloud computing into mobile devices to augment the capacities of the mobile devices resources such as smartphones, tablet, and other personal digital assistant (PDA) which provides a robust technology called Mobile Cloud Computing (MCC). Although MCC have brought many advantages for the mobile users, it also stills suffer from security and privacy side of data while hosted on virtual machines (VM) on remote cloud’s servers. Currently, the eyes of the security expert’s community turned towards the virtualization-based security technique either on the Cloud or on the mobile devices. The new challenge is to develop secure methods in order to authenticate high sensitive digital content. This paper investigates the main challenges regarding the security and privacy issues in mobile cloud exactly focusing on the virtualization issue layer and give clear strengths and weaknesses of recent relevant virtualization security techniques existing in the literature. Hence, the paper provides perspectives for researchers in order to achieve as a future 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="29566">
                <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="29567">
                <text>https://online-journals.org/index.php/i-jim/article/view/10515</text>
              </elementText>
              <elementText elementTextId="29568">
                <text>10.3991/ijim.v13i04.10515</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29569">
                <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="29570">
                <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="29571">
                <text>https://online-journals.org/index.php/i-jim/article/view/10515/5587</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29572">
                <text>Copyright (c) 2019 Boubakeur Annane, Osman Ghazali</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="29573">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 04 (2019); pp. 20-32</text>
              </elementText>
              <elementText elementTextId="29574">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29575">
                <text>Mobile cloud computing</text>
              </elementText>
              <elementText elementTextId="29576">
                <text>Virtualization</text>
              </elementText>
              <elementText elementTextId="29577">
                <text>Security and Privacy of Information</text>
              </elementText>
              <elementText elementTextId="29578">
                <text>User Virtual Machines</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29579">
                <text>Virtualization-Based Security Techniques on Mobile Cloud Computing: Research Gaps and Challenges</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29580">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29581">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29582">
                <text>Peer-reviewed Article</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="1446" 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="29514">
                <text>Suphachaimongkol, Chitralada</text>
              </elementText>
              <elementText elementTextId="29515">
                <text>Ratanatamskul, Chavalit</text>
              </elementText>
              <elementText elementTextId="29516">
                <text>Silapacharanan, Siriwan</text>
              </elementText>
              <elementText elementTextId="29517">
                <text>Utiswannakul, Patcha</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="29518">
                <text>2019-06-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29519">
                <text>Creative tourism has received increasing attention. At present, the concept of creative tourism is still in development stage since there are few or no indicators for assessing the potential of creative tourism to area-based sustainable goals. This document aims to introduce the process of mobile application for sustainable creative tourism (SCT) model development using confirmatory factor analysis (CFA) approach. The study was divided into 4 phases. The first phase involved establishing elements, indicators and criteria drawn from some previous studies and the opinions of experts’ judgement in this study. Secondly, indicators and criteria were selected by using Delphi technique. Thirdly, the indicators and criterias were confirmed by utilizing CFA, Finally, the prototype of SCT mobile application assessment tool is proposed for SCT in this study, based on CFA. Tools for the study included: 1) structured questionnaire from reviews of literature for interviewing the expert, 2) questionnaire for Delphi techniques among the experts for collecting an opinion about the selection of the indicators, and 3) a questionnaire to assess the possibility of data collection concerning the components and indicators of SCT. 300 samples from creative tourism enterprises from all around Thailand were collected and 253 were responded. Data analysis was conducted by using descriptive statistics and CFA. The study found that SCT model consists of 8 components and 36 indicators. The finding from our research shows that it is eligible to establish the novel SCT assessment indicators. The result of SCT application model is appropriate to develop mobile application for SCT assessment tool. </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="29520">
                <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="29521">
                <text>https://online-journals.org/index.php/i-jim/article/view/10500</text>
              </elementText>
              <elementText elementTextId="29522">
                <text>10.3991/ijim.v13i06.10500</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29523">
                <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="29524">
                <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="29525">
                <text>https://online-journals.org/index.php/i-jim/article/view/10500/5731</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29526">
                <text>Copyright (c) 2019 Chitralada Suphachaimongkol, Chavalit Ratanatamskul, Siriwan Silapacharanan, Patcha Utiswannakul</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="29527">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 13 No. 06 (2019); pp. 27-40</text>
              </elementText>
              <elementText elementTextId="29528">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29529">
                <text>Confirmatory factor analysis</text>
              </elementText>
              <elementText elementTextId="29530">
                <text>Indicators</text>
              </elementText>
              <elementText elementTextId="29531">
                <text>Mobile assessment tool</text>
              </elementText>
              <elementText elementTextId="29532">
                <text>Sustainable creative tourism</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29533">
                <text>Development of Mobile Application for Sustainable Creative Tourism Assessment using Confirmatory Factor Analysis Approach</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29534">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29535">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29536">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1445" 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="29488">
                <text>Rautela, Sonica</text>
              </elementText>
              <elementText elementTextId="29489">
                <text>Singhal, Tarun Kumar</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="29490">
                <text>2020-02-28</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29491">
                <text>One of the defining technological forces which are reshaping world today is the easy accessibility to the Internet. The Internet has changed the way people communicate with each other. Social media whose development was first marshaled by Web 2.0, has revolutionized the entire world of communication. The most intriguing fact is that the world of social media is constantly changing. The platforms which are topping the charts today may not be tomorrow. Also, it can be observed that the power has shifted from the hands of marketers to the hands of users which in turn have empowered users. The objective of the present study is to explore the different facets of social media in detail. These facets form the base for the world of social media and can be referred to as the 7 Cs of social media. These seven Cs are - content, community, conversation, capital (social), culture, collaboration, and conversion respectively. With an enhanced understanding of all these Cs of social media, the study proposes a conceptual model depicting the relationship between these seven Cs and social media. Companies should analyze each of these Cs in detail and design their social media strategies accordingly. This will not only assure the efficient and effective use of social media but also will help managers to decide where and how to allot firm resources in a better fashion.</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="29492">
                <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="29493">
                <text>https://online-journals.org/index.php/i-jim/article/view/10490</text>
              </elementText>
              <elementText elementTextId="29494">
                <text>10.3991/ijim.v14i03.10490</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29495">
                <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="29496">
                <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="29497">
                <text>https://online-journals.org/index.php/i-jim/article/view/10490/6589</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29498">
                <text>Copyright (c) 2020 Sonica Rautela, Tarun Kumar Singhal</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="29499">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 03 (2020); pp. 179-198</text>
              </elementText>
              <elementText elementTextId="29500">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29501">
                <text>Social Media</text>
              </elementText>
              <elementText elementTextId="29502">
                <text>Conceptual Model</text>
              </elementText>
              <elementText elementTextId="29503">
                <text>Content</text>
              </elementText>
              <elementText elementTextId="29504">
                <text>Community</text>
              </elementText>
              <elementText elementTextId="29505">
                <text>Conversation</text>
              </elementText>
              <elementText elementTextId="29506">
                <text>Social Capital</text>
              </elementText>
              <elementText elementTextId="29507">
                <text>Culture</text>
              </elementText>
              <elementText elementTextId="29508">
                <text>Collaboration</text>
              </elementText>
              <elementText elementTextId="29509">
                <text>Conversion</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29510">
                <text>Deconstructing the Seven Cs of Social Media: A Summative Perspective</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="29511">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="29512">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="29513">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
