<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd" xmlns="http://www.loc.gov/MARC21/slim">
 <record>
  <leader>00000ctm a22000004a 4500</leader>
  <controlfield tag="001">UP-99796217611425983</controlfield>
  <controlfield tag="003">Buklod</controlfield>
  <controlfield tag="005">20230215105418.0</controlfield>
  <controlfield tag="006">m    |o  d |      </controlfield>
  <controlfield tag="007">ta</controlfield>
  <controlfield tag="008">141010s        xx     d     r    |||| u|</controlfield>
  <datafield tag="035" ind1=" " ind2=" ">
   <subfield code="a">(iLib)UPD-00234405468</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
   <subfield code="a">DENGII</subfield>
   <subfield code="e">rda</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
   <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="042" ind1=" " ind2=" ">
   <subfield code="a">DMLUC</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
   <subfield code="a">LG 995 2014 C65</subfield>
   <subfield code="b">T36</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
   <subfield code="a">Tan, Gianne Clarize</subfield>
   <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
   <subfield code="a">Use of graph database with native query for OWL data storage and reasoning</subfield>
   <subfield code="c">Gianne Clarize Tan.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
   <subfield code="a">Quezon City</subfield>
   <subfield code="b">College of Engineering, University of the Philippines Diliman</subfield>
   <subfield code="c">2014.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
   <subfield code="a">ix, 47 leaves</subfield>
   <subfield code="b">color illustrations</subfield>
   <subfield code="c">28 cm</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
   <subfield code="a">text</subfield>
   <subfield code="2">rdacontent</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
   <subfield code="a">unmediated</subfield>
   <subfield code="2">rdamedia</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
   <subfield code="a">volume</subfield>
   <subfield code="2">rdacarrier</subfield>
  </datafield>
  <datafield tag="502" ind1=" " ind2=" ">
   <subfield code="a">Thesis (M.S. Computer Science)--University of the Philippines, Diliman.</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
   <subfield code="a">The recent rise of web data and the need for domain-specific information to be interoperable led to the standardization of ontologies into the Web Ontology Language (OWL). OWL provides specifications for representing ontology elements and defining relationships among individual elements. Given an established standard, the challenge was implementing a suitable OWL management methodology that was scalable both as a permanent storage of data and in directly inferencing information from the ontology. Current OWL data storage types range from flat files, traditional relational database to triple stores. Meanwhile, the common query language supported across storages on top of native queries is SPARQL. However, these storage types all had limitations. Flat files and pure relational database have scalability issues. Both require programmatic inferencing and need in-memory loading for imported data before being able to do a complete query. On the other hand, storage types that use SPARQL query plug-ins have translation overhead.  This research explored the potential of a graph database with a native query language as a scalable permanent storage and direct retrieval of OWL data. The node-relationship-node structure of a graph database was suitable for mapping relationships between OWL elements. For instance, OWL classes and instances were treated as nodes while OWL constructs were treated as relationships. The native query language Cypher of the graph database would not require in-memory loading of the data set during execution. A Java program using Neo4j was created to load OWL files from the Leigh University Benchmark (LUBM) - 1 dataset. A set of general mapping rules of SPARQL query to Cypher query was devised and employed in this research to transform LUBM SPARQL benchmark queries. These Cypher queries were then executed against the loaded dataset. For comparison, LUBM SPARQL queries were also executed on an existing ontology repository OWLIM. Results showed that graph database storage was scalable as the query time did not degrade in increasing data. Cypher querying was able to outperform SPARQL querying by more than a hundred percent on half of the LUBM test queries. The nature of the queries generally used indexes in node ID matching and did not involve unbounded depth search. This research opened opportunities for further enhancement of storing not yet paid data in a graph database for faster query performance.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Ontologies (Information retrieval).</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
   <subfield code="a">Web Ontology Language (OWL).</subfield>
  </datafield>
  <datafield tag="842" ind1=" " ind2=" ">
   <subfield code="a">Thesis</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
   <subfield code="a">FI</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
   <subfield code="a">UP</subfield>
  </datafield>
  <datafield tag="852" ind1="0" ind2=" ">
   <subfield code="a">UPD</subfield>
   <subfield code="b">DARCHIVES</subfield>
   <subfield code="h">LG 995 2014 C65</subfield>
   <subfield code="i">T36</subfield>
  </datafield>
  <datafield tag="852" ind1="0" ind2=" ">
   <subfield code="a">UPD</subfield>
   <subfield code="b">DENG-II</subfield>
   <subfield code="h">LG 995 2014 C65</subfield>
   <subfield code="i">T36</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
   <subfield code="a">Thesis</subfield>
  </datafield>
 </record>
</collection>
