Universal Repository Access via Directed Graph Model
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current content management systems (CMS) lack interoperability, requiring custom client software and APIs to access different data repositories, and there is no universal solution to interact with various underlying data structures, limiting the ability to access and manage content across multiple repositories.
Innovation Solution
A method utilizing a generalized repository directed graph data model with named object nodes and resources, enabling access via HTTP GET and POST operations, allowing for a distributed, virtual repository that spans multiple physical repositories and provides a common interface for read and write operations using on-the-wire protocols like HTTP/1.1.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If custom client software and APIs are used to access different data repositories, then access to specific repository functionality is achieved, but system complexity and interoperability difficulties increase
Solution Approach 1:
The patent implements a universal client application that can access multiple different content repositories through a single unified interface. The client application includes a repository access module that automatically detects repository types and selects appropriate access methods, eliminating the need for separate custom client software for each repository type. This universal approach allows one client to perform multiple repository access functions without increasing system complexity.
Solution Approach 2:
The patent introduces an intermediary layer consisting of repository access modules that act as mediators between the universal client application and various content repositories. These modules handle the complexity of different repository protocols and data structures, translating them into a unified interface for the client. The intermediary approach isolates the client from repository-specific complexities while maintaining full access functionality.
2Reliability
If bespoke API software is installed for each repository protocol, then proper interaction with each repository is enabled, but the number of software components and installation complexity increase
Solution Approach 1:
The patent merges multiple repository access modules into a single universal client application. Instead of requiring separate API software installations for each repository type, the client application integrates multiple access modules (FTP module, HTTP module, file system module, etc.) that can be dynamically selected based on the repository type. This combining approach maintains reliable interaction with different repositories while reducing the number of separate software components from many individual APIs to one unified application.
3Adaptability or versatility
If a universal client application is created to access all repositories, then interoperability improves, but the complexity of handling diverse data structures increases
Solution Approach 1:
The patent implements a dynamic repository access module within the universal client application that automatically adapts to different repository types and data structures. The access module detects the repository type (FTP, HTTP, file system, etc.) and dynamically selects the appropriate access strategy and data interpretation method. This dynamic adaptation allows the universal client to handle diverse data structures without requiring static complex configuration, as the system adjusts its behavior based on the specific repository it is accessing.
Data Source
AI summary
A method of providing internet access to a data object repository comprising managing data objects hosted by said repository using a generalised repository directed graph data model having object nodes and resources, said resources comprising at least one of(i) a literal;(ii) actual resource data; and/or(iii) a URI directing a request for resources to an address;wherein said object nodes comprise higher level abstractions of data objects;wherein all object nodes and resources are named, as well as all arcs between object nodes and other object nodes or resources, said arcs modelling properties of said nodes;wherein each said directed graph has a graph interface which represents data as a directed graph of nodes and resources; andwherein said graph interface is capable of enabling access to data represented by said directed graph by traversal of said directed graph using http:GET.