XML Schema Layout Integration for Business Document Reusability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current electronic business systems face challenges in exchanging business documents due to the lack of uniform and standardized methods for representing the structure and semantics of business data, leading to varied representations and the need for manual mapping between different document structures and semantics, even with the use of XML, which does not address non-uniform semantics effectively.
Innovation Solution
Incorporating layout information directly into schema definitions for data components, allowing for the tight coupling of semantic and relative layout information, enabling the use of reusable building blocks that include visual representation details, and allowing browsers to validate and visualize business documents based on standardized schema definitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If layout information is stored in separate external script files, then the document structure and layout can be independently maintained, but there is no tight conjunction between reusable building blocks and layout information, requiring complete new layout information to be developed for each new document
Solution Approach 1:
The patent merges layout information and document structure into a single XML schema definition. The schema includes both the data component definitions and their associated layout properties (such as display format, positioning, and visual presentation) within the same file, eliminating the need for separate external script files and enabling tight integration between reusable building blocks and their layout information.
Solution Approach 2:
The XML schema definition serves multiple functions simultaneously: it defines the document structure, validates the data, and specifies the layout information for visual presentation. This multi-functional approach allows the same schema to be used across different documents and formats, enhancing the reusability of building blocks while eliminating the need for separate layout development.
2Ease of operation
If external script files are used for layout information, then layout properties can be described separately, but current browsers do not understand the semantics and structure of reusable building blocks based on XML schemas
Solution Approach 1:
The patent introduces an intermediary processing layer that translates the integrated XML schema definitions into browser-compatible formats. This intermediary component enables browsers to understand and render the semantics and structure of reusable building blocks while maintaining the benefits of the integrated schema approach, effectively bridging the gap between the schema-based document model and browser capabilities.
3Productivity
If manual mapping is performed between different document structures and semantics, then document exchange between business partners is possible, but the process requires previous coordination and is not automated
Solution Approach 1:
The patent standardizes document structures using uniform XML schema definitions that incorporate both data semantics and layout information. By changing the parameter representation to a standardized format, the system eliminates the need for manual mapping between different document structures, enabling automated document exchange between business partners without requiring previous coordination or custom mapping procedures.
Data Source
AI summary
In a computer system that is configured to contain schema definitions for several data components, layout information for at least one of the data components is stored in the schema definition for the at least one data component. A method of providing display of data in a graphical user interface includes accessing layout information for a data component, the layout information being included in a schema definition for the data component, and providing, using the accessed layout information, an instance of the data component for display in a graphical user interface. A browser can parse XSD artifacts of reusable building blocks and generate a graphical user interface with the embedded relative layout information of every building block.