<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="14029" public="1" featured="0" 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://archives.christuniversity.in/items/show/14029?output=omeka-xml" accessDate="2026-05-15T04:53:58+00:00">
  <collection collectionId="5">
    <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="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</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="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93285">
              <text>Blockchain-Based Service Oriented Privacy-Preserving Data Sharing over Distributed Data Streams in Asynchronous Environment</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93286">
              <text>Blockchain; data sharing; Internet of Things; Privacy-preserving; Smart City; smart contract</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93287">
              <text>Innovative city applications use information and communication technologies to function various operations efficiently. The widespread use of the Internet of Things (IoT) can be viewed in several applications like smart cars, smart cities, e-commerce, and cyber-physical systems. The huge amount of data produced and transmitted by these systems is handled by cloud-based storage services, which are vulnerable to multiple threats risking the privacy and security features of the application. Cloud storage services employ encryption algorithms to ensure data confidentiality, but it fails to address the privacy issues. Apart from the privacy risks, in these systems, the identity of a user who shares and accesses the data is traceable, as it is required to verify user eligibility before providing access. Also, a vast amount of daily data is stored on a centralized system that processes service requests from multiple users, posing considerable risks to the system's stability during peak periods. To address these challenges faced during the data sharing process in a centralized system, Service Oriented Privacy-Preserving Data Sharing (SOPPDS) platform based on a blockchain framework is proposed. The modified Key Policy-Attribute-based Encryption (MKP-ABE) technique is applied to securely share the data between the service owners and the service consumers. It was evident from the performance evaluation of the proposed SOPPDS platform that the encryption process takes lesser time than the decryption process. Also, the cryptographic operations performed on the prime order sets exhibited increased latency and computational cost. It was observed that comparatively, cryptographic operations performed on composite order sets could overcome the issues in prime order sets. SOPPDS platform works well in preserving the users' privacy, ensuring anonymity in the data sharing process, and maintaining the confidentiality of the data shared in the system.  2023, Ismail Saritas. All rights reserved.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93288">
              <text>Suganthi P.; Malini A.; Felicia Lilian J.; Vetriveeran D.</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="93289">
              <text>International Journal of Intelligent Systems and Applications in Engineering, Vol-11, No. 4, pp. 591-602.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="93290">
              <text>Ismail Saritas</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="93291">
              <text>2023-01-01</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="93292">
              <text>&lt;a href="" target="_blank" rel="noreferrer noopener"&gt;&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85174799659&amp;amp;partnerID=40&amp;amp;md5=25521dc8cc9dc7da7a70ba6c00c53d1c" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85174799659&amp;amp;partnerID=40&amp;amp;md5=25521dc8cc9dc7da7a70ba6c00c53d1c&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93293">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="93294">
              <text>ISSN: 21476799</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="93295">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93296">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="93297">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="93298">
              <text>Suganthi P., Department of CSBS, Thiagarajar College of Engineering, Tamilnadu, Madurai, 625015, India; Malini A., Department of CSBS, Thiagarajar College of Engineering, Tamilnadu, Madurai, 625015, India; Felicia Lilian J., Department of CSBS, Thiagarajar College of Engineering, Tamilnadu, Madurai, 625015, India; Vetriveeran D., Department of CSE, School of Engineering and Technology, CHRIST University, Bangalore, 560074, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
