Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 22.8

GraphDB Technology

General InformationGeneral Information help

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website: Go to site
Description: GraphDB is a graph database and semantic repository that uses ontologies to allow the repository to automatically reason about the data. Implemented in Java and packaged as a Storage and Inference Layer (SAIL) for a Resource Description Framework (RDF), GraphDB is a native RDF rule-entailment and storage engine. This technology works with a flexible and generic physical graph data model allowing for on-the-fly interpretation and adoption of new ontologies or metadata.

GraphDB stores all of its data in a No Structured Query Language (NoSQL) directory, usually called `STORAGE.` GraphDB maintains two main indices on statements for use in inference, query evaluation, and manipulation of RDF data: the predicate-object-subject (POS) index and the predicate-subject-object (PSO) index. The Workbench component provides management interfaces implemented on top of the GraphDB Server Representational State Transfer (REST) Application Programming Interface (API). This software provides a web application to write Simple Protocol and RDF Query Language (SPARQL) queries, import, export information and perform other maintenance activities. GraphDB Workbench also includes all GraphDB Server interfaces and can point them to an embedded database (i.e., no additional GraphDB Server installation is required) or a remote GraphDB Server. Additionally, this technology can optionally use Amazon Web Services (AWS) Cloud on a pay-per-use basis, or as a Database-as-a-Service for database storage.

Note: There are multiple editions of GraphDB: Free, Standard Edition (SE), Enterprise Edition (EE), and Cloud Edition. The scope of this entry is for the Free Edition, SE, and EE only.

The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at:
Technology/Standard Usage Requirements: Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information: This technology has been assessed by the Section 508 Office and found non-conformant. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Please see reference tab for more information concerning product versions.
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v20.4
Decision Date: 04/08/2020
Introduced By: TRM Request
Vendor Name: Ontotext
- The information contained on this page is accurate as of the Decision Date (04/08/2020).