Digital Ink File Metadata for Device-Specific Stroke Reproduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing digital ink technologies fail to process stroke data based on the input device, maintain complex before-and-after relations among multiple strokes, and handle diverse pen identification information formats, leading to inefficiencies in data reproduction and application compatibility.
Innovation Solution
The method generates stroke data based on event data, associates metadata with the input device, and converts pen identification information into logical formats, enabling device-specific reproduction and handling diverse pen ID formats.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If stroke data is stored without device-specific metadata, then file compatibility is improved, but device-specific reproduction capability is lost
Solution Approach 1:
The patent segments the ink file into distinct components: stroke data and device metadata blocks. Each stroke can be independently associated with specific device information through metadata blocks, allowing device-specific reproduction without complicating the overall data structure. The segmentation enables selective processing of stroke data based on device capabilities.
Solution Approach 2:
The patent introduces metadata blocks as intermediary elements that bridge stroke data and device information. These metadata blocks contain device identifiers and capabilities, acting as mediators that enable the system to match stroke data with appropriate reproduction devices without direct coupling between the two.
2Adaptability or versatility
If multiple pen identification information formats are supported, then device compatibility is improved, but data processing complexity increases
Solution Approach 1:
The patent changes the parameter representation by storing pen identification information in a standardized format within metadata blocks. Instead of handling multiple formats directly, the system converts diverse pen ID formats into a unified representation, changing the data parameter from format-specific to format-agnostic.
Solution Approach 2:
The patent creates copies of pen identification information in a standardized format within metadata blocks. Rather than requiring the system to interpret and process multiple native formats directly, it generates standardized copies that can be uniformly processed, eliminating format conversion complexity.
3Productivity
If stroke data is processed without order information, then processing speed is improved, but complex stroke relation reproduction is lost
Solution Approach 1:
The patent performs preliminary action by pre-calculating and storing order information (rendering order, intersection relationships) within the stroke data structure during the data generation phase. This allows the reproduction phase to simply retrieve and apply the pre-computed order information without performing complex real-time calculations, maintaining both speed and accuracy.
4Manufacturing precision
If device metadata is stored with each stroke, then reproduction accuracy is improved, but file size increases
Solution Approach 1:
The patent merges device metadata with stroke data by associating metadata blocks with specific strokes through identifiers. This combining approach allows the system to store device-specific information only where needed (for strokes that require device-specific reproduction) rather than duplicating metadata for every stroke, reducing overall file size while maintaining reproduction accuracy.
Data Source
AI summary
An ink file output method is provided, which includes: generating M (M is an integer of 1 or more) pieces of stroke data SD on the basis of event data generated as M input devices move, respectively; generating N (N is an integer of 1 or more and M or less) kinds of logical names LN (metadata) identifying the M number of input devices; generating a metadata block associating the M pieces of stroke data SD with the N kinds of logical names LN; and writing the M pieces of stroke data SD and the metadata block to an ink file.