Graph Elements schema

[Aaron J. Seigo]

On Monday 31 January 2005 03:38, John Tapsell wrote:
> How would a full text search hook into this?

here's a snippet from some notes i'm keeping as i continue to think about 
these things ...

-------------
storage is split into two primary domains: the graph (a mesh of nodes) and
content (e.g. full text indexes). nodes in the graph (primarily infons) are 
referenced by entries in the content. note that "content" does not 
necessarily mean the literal content of the data being represented (e.g. 
email, notes, songs, outlines...). the content that is stored may be 
processed representations of said data, such as in the form of full text 
search vectors, etc.. nodes in the graph are strictly short strings of text, 
while content may consist of a variety of sizes of a variety of data types.

so while id3 tags may appear in the graph itself, full text indexes would 
appear in the content area and reference nodes in the graph.

term searches are done on the content primarily and on the graph nodes 
secondarily, while navigation is done by traversing the graph. in this way 
content provides entry points into the graph which is then traversed. 

alternatively one can start navigating the graph directly by starting with a 
specific monaform (e.g. 'Audio') or location (e.g. 
'file:/home/aseigo/mobydick.pdf')
--------------

so the schema as it appears thus far doesn't provide the "content" area of 
storage yet, which is where things like full text vectors would be stored. 
the content needs to reference into the graph as well, but i haven't gotten 
that far in copula.sql

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/klink/attachments/20050201/0b1feefd/attachment.pgp