Extensible Remote Tag Markup System for Enterprise Data Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing remote tag markup systems are not extensible enough to fully leverage enterprise server functionality for HTML content from remote servers, limiting content developers' ability to use their preferred tools and access enterprise server data.
Innovation Solution
An extensible remote markup tag system that includes an enterprise server, gateway, transformer component, and tag transformation engine, allowing HTML content from remote servers to be parsed and converted for enterprise server functionality, with a library of remote markup tags that can be extended and executed on the enterprise server, and providing access to enterprise server data beyond the remote access API.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If remote tag markup systems use standard JSP tags or .NET server controls, then tag markup functionality is provided, but the system cannot access enterprise server data beyond remote access API and cannot leverage enterprise server functionality
Solution Approach 1:
The patent introduces a gateway as an intermediary component that bridges remote servers and the enterprise server. The gateway collects HTML content from remote servers and forwards it to the enterprise server for processing, enabling access to enterprise server functionality while maintaining a clean separation between remote content delivery and enterprise server operations.
Solution Approach 2:
The system is divided into distinct functional segments: remote servers that deliver HTML content, a gateway that collects and forwards content, an enterprise server that processes tags and accesses enterprise data, and a tag transformation engine that executes tags. This segmentation allows each component to specialize in its function while accessing enterprise server capabilities through the coordinated system architecture.
2Adaptability or versatility
If content developers use enterprise server tools, then access to enterprise server data is enabled, but content developers cannot use their preferred external content development tools
Solution Approach 1:
The enterprise server is designed to handle multiple types of tag markup from different sources (JSP tags, .NET server controls, and custom remote markup tags). The tag transformation engine can process various tag formats and convert them into enterprise server functionality, allowing content developers to use their preferred tools while the system universally processes all tag types through a common interface.
3Adaptability or versatility
If the system processes HTML content from remote servers through the enterprise server, then enterprise server functionality is applied to remote content, but processing time and system overhead increase
Solution Approach 1:
The gateway collects HTML content from remote servers in advance and prepares it for processing by the enterprise server. By pre-collecting and staging the content before enterprise server processing, the system reduces the time required for actual tag transformation and execution, as the content is already available and prepared when the enterprise server needs to process it.
Data Source
AI summary
Functionality available on an enterprise server is applied to HTML content from a remote server. HTML content is collected from remote servers including remote markup tags upon request from an end user. The HTML content for the remote markup tags is parsed and converted to content formatted for enterprise server functionality. The converted content is executed at the enterprise server. Remote server and enterprise server data are then transmitted to the end user. Tags and/or libraries may be extensible, such that they may be created or modified, and the tags may or may not be included within a supplied library of tags and/or a created library of tags, or any combination thereof.