Semantic Analysis for Graph Database Query Editors

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern textual editors for database query languages like SQL and SPARQL struggle to provide semantic analysis features due to the absence of a self-contained schema in graph and tuple databases, limiting the exploitation of semantic analysis techniques.

Innovation Solution

A computerized method is introduced that extracts a schema from a tuple graph dataset to perform semantic analysis on an abstract syntax tree (AST) during query editing, using resource description framework (RDF) triples and schema statements to provide error alerting and code completion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a self-contained standalone schema is used (as in relational databases), then semantic analysis can be performed effectively, but graph and tuple databases cannot provide such schema separation

Engineering Contradiction:
Improvesemantic analysis capabilityVSAvoidschema organization structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges the schema and dataset into a unified graph structure where schema information is represented as special tuples within the graph itself. This allows semantic analysis to function by querying the graph for schema information rather than relying on separate schema files, resolving the contradiction between needing semantic analysis capability and the inherent complexity of graph database schema organization.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent introduces an intermediary layer that extracts schema information from the graph dataset and presents it to the semantic analyzer in a structured format. This intermediary process enables semantic analysis without requiring a traditional standalone schema, bridging the gap between graph database flexibility and semantic analysis requirements.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If traditional semantic analysis techniques are applied to graph databases, then error detection and code completion can be provided, but the absence of standalone schema prevents this

Engineering Contradiction:
Improveerror detection and code completionVSAvoidschema information accessibility
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent extracts schema information from the graph dataset by identifying and separating metadata tuples that define types, properties, and relationships. This extracted schema is then used by the semantic analysis engine to provide error detection and code completion, effectively taking out the necessary schema information from the bulk data while maintaining the graph database's unified structure.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent performs preliminary extraction and organization of schema information from the graph dataset before semantic analysis is conducted. This preliminary action prepares the schema data in advance, making it accessible to the semantic analyzer and enabling error detection and code completion features without losing information about the graph structure.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If schema information is embedded within the dataset, then graph database flexibility is maintained, but semantic analysis becomes more difficult

Engineering Contradiction:
Improvegraph database flexibilityVSAvoidschema information retrieval
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent applies local quality by assigning different roles to different tuples within the graph - some tuples are identified as schema definitions while others are data instances. This local differentiation allows the system to maintain the flexible embedded schema structure of graph databases while enabling efficient schema retrieval for semantic analysis by treating schema tuples differently from data tuples.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10614126B2Textual query editor for graph databases that performs semantic analysis using extracted information
Publication Date: 2020.04.07 ORACLE INT CORP
  • US10614126B2 patent drawing
  • US10614126B2 patent drawing
  • US10614126B2 patent drawing

AI summary

Techniques herein are for query editing with semantic analysis of a query based on information extracted from a tuple graph. In an embodiment, a computerized method involves processing a dataset to extract an extracted schema that describes types and relationships that occur within the dataset. The dataset is not associated with a schema that is not contained in the dataset. The dataset has a graph of tuples. During an incremental parse, an abstract syntax tree (AST) that represents a query is modified. The extracted schema and the dataset are used to perform semantic analysis on the AST. In an embodiment, the tuples are resource description framework (RDF) triples. In an embodiment, the RDF triples include RDF schema statements. Extracting an extracted schema involves processing RDF schema statements. In an embodiment, the query is a SPARQL query and semantic analysis includes error alerting and code completion.