Files as graph values

Files are graph values alongside strings, dates, and numbers. Legra's extended value model works with RDF and labelled property graphs (LPG).

Cypher and GQL

A vertex (node) can have a property whose value is an entire file. For a meeting recording:

If the recording has its own author, date, or other metadata, give it a separate vertex with a content property. Connect that vertex to the meeting with a has-recording edge.

RDF and SPARQL

An RDF triple expresses the same example as a subject, predicate, and object. Legra's extended RDF literals let the object contain the audio file:

Both views use the same file content and media type.

Keep Word documents, PDFs, spreadsheets, email, messages, images, audio, video, and other file types in the graph. Connect them to customers, authors, projects, or decisions through ordinary graph relationships.

Large files stream into and out of storage without requiring the complete value in memory. File content follows the workspace's access and encryption rules and version history.

Legra divides large content into reusable chunks, taking file structure into account. Identical chunks within a workspace are stored once and shared across files and versions. This deduplication lets a revised document reuse the parts that did not change.

File values are a platform capability available to every app. Drive adds directories, filenames, file versions, and connections to external file stores such as SharePoint.

Whole websites fit as collections of HTML, CSS, JavaScript, images, and other file values. Drive keeps their directory structure alongside their content in the graph.