Browse Prior Art Database

Language information for Triplestore Disclosure Number: IPCOM000207671D
Publication Date: 2011-Jun-09
Document File: 2 page(s) / 54K

Publishing Venue

The Prior Art Database


Language information storage within a triplestore.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 56% of the total text.

Page 01 of 2

Language information for Triplestore

Commercially and academically triplestore is widely used to implement complex data modelling. Value expression with complex language labelling is often required in a triplestore. Normally the language information can be stored in either a primary table or an auxiliary table. A primary table is usually big and with detailed language information it becomes even larger with low performance. If language information is stored in the auxiliary table with the primary table referring to it, the query with language will become slow.

    We present in this disclosure a method to spread out language information across the primary table and the auxiliary table. The novelty in this solution is that the primary table only contains small amount of information for fast language query and the detailed language information can be available in the auxiliary table. The strength of this solution is that the volume of the triplestore doesn't increase dramatically with language information and the performance of language query is better than common solutions.

    Triplestores are widely used to express complicated data modelling with simple triples of subject, predicate, and object. Many other data designs (such as Object Relational Mapping) can be implemented easily with a triplestore. To implement a triplestore, one solution is to make use of the existing relational databases since commercial relational databases provides users the merits of scalability, security, and reliability and portability.

    The three elements of a triplestore can be conceptually stored as three columns in a table in a relational database. In practice, all kinds of values of the triples can be stored in the table and the table can be very big. A usual situation is that the values of the triples need to be labelled with the language information.

    Following the ISO language coding standard, the language information can include 2 bytes of language code, 2 bytes of country code, and variable length of extra variant information. If we add all the language information into the triple table, the table would become much larger than before. In the normal query even without language information, the table joining operation can be very costly, incurring poor performance. One common alternative is to store all the language information into a different auxiliary table, and the triple table (primary table) can refer to the auxiliary table with a foreign key. But the language information is often used as a query constraint along with other tripl...