Distributed Wiki Content Sharing via Standardized Intermediary Format

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current wiki engines are monolithic and unable to share content with each other due to different syntax and user interfaces, limiting the breadth of information and causing redundancy across systems, especially in environments with slow or intermittent network connectivity.

Innovation Solution

A distributed wiki system utilizing distributed revision control allows wikis to share content by automatically merging changes and synchronizing on a periodic or event-driven basis, enabling collaboration and content sharing even without continuous internet connection, with features like delta encoding and conflict resolution that permit conflicting changes to persist.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If wikis use different syntax and user interfaces, then each wiki can maintain its own unique characteristics and functionality, but wikis are unable to share content with each other

Engineering Contradiction:
Improvewiki uniquenessVSAvoidcontent sharing
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces a standardized content format as an intermediary that enables content exchange between wikis with different syntaxes and interfaces. This intermediary format acts as a universal translation layer, allowing wikis to maintain their unique characteristics while sharing content through the standardized format.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments wiki content into standardized, interchangeable units that can be independently shared and reassembled. By dividing content into discrete, format-independent elements, wikis can exchange specific content pieces without requiring full compatibility of their overall syntax and interface structures.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If wikis are monolithic applications, then they can maintain simple internal structure and operation, but the breadth of information is limited and redundancy increases

Engineering Contradiction:
Improvewiki structureVSAvoidinformation breadth
Core Design Contradiction:
Device complexityVSQuantity of substance

Solution Approach 1:

The patent merges multiple monolithic wikis into a distributed network where content can be shared and combined. By connecting separate wiki instances through the standardized format, the system achieves greater information breadth while each individual wiki maintains its simple internal structure.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The standardized content format provides universal functionality across different wikis, enabling a single content unit to be shared and utilized across multiple wiki instances. This multi-functionality allows wikis to access broader information without increasing their individual structural complexity.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If wikis require continuous internet connection for synchronization, then content sharing is real-time and accurate, but users with intermittent connectivity cannot access or contribute content

Engineering Contradiction:
Improvesynchronization accuracyVSAvoidconnectivity flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements preliminary action by allowing wikis to store and queue content changes locally before synchronization occurs. Users can create and edit content offline, and the system automatically attempts to synchronize these changes when connectivity becomes available, ensuring both reliability and connectivity flexibility.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent employs periodic action through scheduled synchronization attempts. The system periodically tries to synchronize content between wikis and external systems, allowing users with intermittent connectivity to contribute content at any time while maintaining eventual consistency when connections are available.

Inventive Principle:
Principle #19Periodic action

4Reliability

If content synchronization occurs frequently, then wikis stay up-to-date with changes, but network bandwidth and system resources are consumed

Engineering Contradiction:
Improvecontent currencyVSAvoidnetwork bandwidth
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies partial action by synchronizing only the specific content elements that have changed rather than performing full content transfers. This selective synchronization maintains content currency while significantly reducing network bandwidth consumption compared to frequent complete synchronizations.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The system implements feedback mechanisms to track which content has been synchronized and which changes need to be propagated. This feedback information allows the system to intelligently determine synchronization needs, performing updates only when necessary and avoiding redundant data transfers that would consume unnecessary network resources.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS10067996B2Selection of content for sharing between multiple databases
Publication Date: 2018.09.04 RED HAT INC
  • US10067996B2 patent drawing
  • US10067996B2 patent drawing
  • US10067996B2 patent drawing

AI summary

Selection of content for sharing is described. An indication of desired content to be shared between a first database and a second database is sent from the first database to the second database. The first database receives desired content corresponding to the indication and a relevancy determination corresponding to a threshold fraction of users that tag the desired content to a particular category. A first version of the desired content is identified in the first database. A second version of the desired content is received by the first database from the second database upon an identification, at the second database, of the second version of the desired content.