Comparing Ontology with Database for Schema Change

碩士 === 國立中央大學 === 軟體工程研究所 === 101 === Different from traditional relational database, ontology uses a new way to store data as well as schema. Traditional relational database aims at saving space, thus stores no table relationship. On the other hand, ontology stores the relationship among its classe...

Full description

Bibliographic Details
Main Authors: Sheng-feng Lin, 林聖峰
Other Authors: Jen-yen Chen
Format: Others
Language:zh-TW
Published: 2013
Online Access:http://ndltd.ncl.edu.tw/handle/71668822804862416792
Description
Summary:碩士 === 國立中央大學 === 軟體工程研究所 === 101 === Different from traditional relational database, ontology uses a new way to store data as well as schema. Traditional relational database aims at saving space, thus stores no table relationship. On the other hand, ontology stores the relationship among its classes through property that should be considered in building it. We thus follow the seven steps by Stanford University to build a Taiwan Travel Ontology. This work presents two case studies of schema change. Case 1 discusses adding one attribute. Case 2 discusses extending two subclasses. Through the case studies, we probe into the difference between ontology and relational databases. If "save" time is included, database performs better because it is well optimized. If not, ontology do better. On the one hand, ontology stores relationship among its classes. On the other hand, relational database stores independent tables only, without their relationship. When it comes to schema change, ontology appears to be better than relational database.