README
¶
Layered Schemas
Layered Schema Architecture (LSA) enables semantic interoperability between heterogeneous systems. LSA uses a schema base (such as FHIR schemas for health data) to define data structures, and overlays to add semantics, contextual metadata, and processing directives. A schema variant is the composition of the schema base and use-case specific overlays. Different schema variants can be used to ingest data from or export data to disparate systems. Each variant encodes source specific metadata and rules to ingest data into a knowledge graph, or target specific metadata and rules to translate the knowledge graph into another format.
A layered schema defines a mapping from structured data (in JSON, XML, tabular format) to linked data. For instance, when a JSON document is ingested using a layered schema, a labeled property graph is constructed by combining schema information with the input data elements. The resulting graph contains both the input data, and the schema annotations. This allows processing data based on its semantic attributes instead of its attributes names or other structural properties. For example, it is possible to use layered schema to ingest health data, mark certain attributes as "identifiable", and then, remove all attributes that are marked as such. The algorithm to remove "identifiable" elements can be written without any knowledge of the input structure. Same algorithm can be used to de-identify health data as well as marketing data.
The main documentation site for layered schemas is:
This Go module contains the reference implementation of the layered schema specification. It contains a layered schema compiler to slice/compose schemas, import JSON schemas, and annotate data from JSON/CSV sources.
Building
Once you clone the repository, you can build the schema compiler using the Go build system.
cd layers
go build
This will build the layers binary in the current directory.
Examples
The examples/ directory contains some example data processing
scenarios.
Commercial Support
Commercial support for this library is available from Cloud Privacy Labs: support@cloudprivacylabs.com
Directories