Concise Resource Addressing via Dual Identifier Format
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current navigation systems use long, cryptic URLs that are not human-readable, server-specific, and do not support free-form target addressing or multiple target applications, leading to management difficulties and limitations in bookmarking and sharing.
Innovation Solution
A dual identifier format consisting of a textual identifier for human-readable descriptions and a contextual identifier for encoded descriptions, allowing for concise and stable resource addressing, with a resolving service to map identifiers to target applications based on user identity or role.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If traditional URLs are used for application navigation, then applications can be addressed uniquely, but the URLs become long and cryptic that are not human-readable
Solution Approach 1:
The URL is segmented into distinct components: a concise textual identifier for human readability and a contextual identifier for precise application targeting. This segmentation allows each part to serve its specific function - the textual identifier provides human-readable meaning while the contextual identifier ensures accurate routing to the target application
Solution Approach 2:
A resolving service acts as an intermediary between the concise dual-identifier URL and the actual application target. This mediator translates the human-friendly textual identifier into the system's internal application reference, enabling short URLs to resolve to specific applications without exposing the underlying complexity
2Adaptability or versatility
If server-specific URLs are used, then applications can be located on specific servers, but the URLs do not support free-form target addressing or multiple target applications
Solution Approach 1:
The dual-identifier URL structure provides universal addressing capability that works across multiple servers and applications. The textual identifier can represent any application regardless of server location, while the contextual identifier handles the complexity of routing to the correct target, enabling one URL format to serve multiple functions including free-form addressing and multi-target support
Solution Approach 2:
The resolving service dynamically determines the target application based on the textual identifier and contextual information, rather than relying on static server-specific URL patterns. This dynamic resolution enables flexible targeting of multiple applications through a single URL structure, adapting to different users, roles, and contexts
3Ease of operation
If long cryptic URLs are used, then applications can be addressed precisely, but bookmarking and sharing become difficult
Solution Approach 1:
The URL is divided into a human-readable textual identifier segment and a machine-processing contextual identifier segment. The textual segment is short and meaningful for easy bookmarking and sharing, while the contextual segment preserves the precision needed for accurate application identification through the resolving service
Solution Approach 2:
The textual identifier acts as a human-friendly copy or representation of the actual application target. Instead of requiring users to interact with the full complex URL structure, the system uses the concise textual copy for bookmarking and sharing while maintaining the ability to precisely identify the target application through the resolving service
Data Source
AI summary
The present disclosure involves systems, software, and computer-implemented methods for concise resource addressing. An example method includes receiving a request for an application including a resource identifier, the resource identifier including a textual identifier and a contextual identifier, the textual identifier including a textual description of the requested application, and the contextual identifier including an encoded description of the requested application; determining at least one target application associated with the resource identifier based at least in part on the textual identifier or the contextual identifier; and sending a response to the request include the at least one target application associated with the resource identifier.