Semantic Web does not provide reference to object properties

Semantic web knowledge representation is build on triples, which represent subject - predicate - object. Semantic web Standards are using those triples as atomic building blocks for their own specification and any ontology. With triples knowledge can be specified like in the sentence: "Paul is a Person". "Paul" is the subject, "is a" is the predicate, "Person" is the object. Subject and object are considered as entities while predicates are considered as object properties are connecting those entities. From this perspective representation of every knowledge is quiet similar to the usage of early days' entity-relationship-diagrams. Also some shortcomings seem to be adopted. Sentences like: "Paul takes Pauls Car to reach Pauls Office" cannot be described easily. It requires an intermediate, unnatural entity like "Pauls Vehicle Choice" and many sentences: "Pauls Vehicle Choice chosen by Paul", "Pauls Vehicle Choice is Pauls Car", "Pauls Vehicle Choice reaches Pauls Office". Instead of one sentences there are three sentences for describing the equivalent problem. Isn't there an alternative approach possible?

How to store ontologies in a relational database?

The Semantic Web brings closer to realization the possibility of semantically organized data repositories, or ontologies, throughout the Internet that can be used for intelligent information searching both by humans and computational agents. Ontologies are important to application integration solutions. However, while today there is an un-precedented wealth of information available on the Web, to fully realize the power of ontologies and to enable efficient and flexible information gathering, persistent storage of ontologies and its subsequent retrieval is of paramount importance. Therefore, storing ontologies in a relational database is one way to get around this problem.

Work with RDF

RDF (Resource Description Framework) is a set of specifications, designed to provide metadata for your data model (general method of modelling information). RDF-Files are stored in a XML like syntax and are used to additional describe the data contained. There also exist an SQL-Query like query language which allows you to extract data from these files. However it would be nice to store these files into a database and easily update or read the data.

Using RDF(S) without XML.

RDF can be written in some ways: A RDF triple could be represented through a RDF graph, through FOL expressions like P(X,Y), or - most common used for web development - through XML. There are some good RDF/XML parsers for the most common web development languages like Perl or Python. But is there another way of writing RDF, which is supported by a parser for programming/script languages?

rdf resource declaration-solution

It is possible to define resource in one place and add properities in another like this:

<rdf:Description rdf:about="http://www.example.sk/Maria_Juana">
<rdf:type rdf:resource="http://xmlns.com/foaf/0.1/Person"/>

<rdf:Description rdf:about="http://www.example.sk/Maria_Juana">
<rdf:name>Maria Juana</rdf:name>


rdf resource declaration

Data in the file is not written in the same order in which I need to process them. So my question is, whether should be all properties of one resource declared at one place (in one description tag) and thus whole file processed at once and only then created rdf. Or whether it is possible to add properties to previously declared resource anywhere in document during data processing?


Subscribe to rdf