<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="20948" 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/20948?output=omeka-xml" accessDate="2026-04-08T21:15:06+00:00">
  <collection collectionId="16">
    <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="51377">
                <text>Conference Papers</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="28">
    <name>Conference Paper</name>
    <description>Faculty Publications- Conference Papers</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="188753">
              <text>An online signature method using DNA based bio-hash for positive identification and non-repudiation</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="188754">
              <text>Bio-Sign; DNA-Hash; e-Signature; Non-Repudiation; Positive Identification; Signature DNA</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="188755">
              <text>This work focuses on using biological data as a unique feature to generate e-Signature. DNA, the blue print of life is of unique nature. The signature created using biological data will be difficult to repudiate in the scenario of a legal dispute. Applications of human DNA are not limited to molecular biology, with the advents of fast growing technologies it is possible to inject DNA into e-Signature for positive identification. The proposed methodology uses Signature DNA as a unique biological feature for the registrant. This work has various phases, the first phase includes creating the Signature DNA using hybridized unique DNA segments of the individual (Registrant) which is the unique identification of the user and difficult to duplicate and repudiate. It generates a Bio-Hash of the Signature DNA. The DNA-Hash generated serves for positive identification of the user which computed with the hash of the e-Document and a random value serve as a Bio-Sign (e-Signature) for the e-Document in the second phase. Bio-Sign converted into QR code with a link to the e-Sign service providers website will ensure usability for verification. In the verification phase the verifier scans the QR code which connects to the e-Service provider's web link. The service provider computes and verifies the document and ensures the e-Signature is valid or not to the verifier. If the signer repudiates the signature, positive identification using DNA helps to achieve Non-Repudiation, the last phase. In the scenario of a legal dispute, the registrant cannot repudiate as the authorities can provide positive identification using the DNA Signature for greater assurance. The proposed technique ensures authentication, integrity and Non-Repudiation with Zero knowledge scenario to the verifier.  2017 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="188756">
              <text>Sreeja C.S.; Misbahuddin 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="188757">
              <text>2017 International Conference on Public Key Infrastructure and its Applications, PKIA 2017 - Proceedings, Vol-2018-January, pp. 28-35.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="188758">
              <text>Institute of Electrical and Electronics Engineers Inc.</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="188759">
              <text>2017-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="188760">
              <text>&lt;a href="https://doi.org/10.1109/PKIA.2017.8278957" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/PKIA.2017.8278957&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85050852818&amp;amp;doi=10.1109%2FPKIA.2017.8278957&amp;amp;partnerID=40&amp;amp;md5=7ba8ae4abcc79378087bd984fe020387" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85050852818&amp;amp;doi=10.1109%2fPKIA.2017.8278957&amp;amp;partnerID=40&amp;amp;md5=7ba8ae4abcc79378087bd984fe020387&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="188761">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="188762">
              <text>ISBN: 978-153862356-5</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="188763">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="188764">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="188765">
              <text>Conference paper</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="188766">
              <text>Sreeja C.S., Dept. of Computer Science, Christ University, Bengaluru, India; Misbahuddin M., Computer Networks and Internet Engineering Division, C-DAC, Electronic City, Bengaluru, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
