Resource Identifier Parser for Non-Browser Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computing devices often rely heavily on network browser applications to access and interact with network resources, limiting the flexibility of non-browser application programs which can only accept specific types of data and lack the ability to utilize information from resource identifiers beyond their alphanumeric characters.

Innovation Solution

A resource identifier parser is introduced to extract and provide utilizable information from resource identifiers to non-browser application programs, enabling them to access and manipulate network resources without requiring a browser application, and can be customized or accessed as a network service to handle various resource identifier structures.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If non-browser application programs are used to access network resources, then application flexibility and functionality are improved, but the ability to utilize information from resource identifiers deteriorates because they can only accept specific types of data

Engineering Contradiction:
Improveapplication functionalityVSAvoidresource identifier information
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

A parser component is introduced as an intermediary between resource identifiers and non-browser application programs. The parser extracts meaningful information from resource identifiers and transforms it into a format that non-browser applications can utilize, enabling these applications to access and process network resource information without requiring a browser environment.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system changes the parameter format of resource identifier information by parsing it into structured data elements. This transformation converts the raw resource identifier string into extracted parameters and properties that can be directly consumed by non-browser application programs, expanding their capability to handle network resource data.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If resource identifiers are parsed to extract information, then non-browser application functionality is extended, but device complexity increases due to the need for parsing components

Engineering Contradiction:
Improveapplication capabilityVSAvoidsystem structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The parser serves as a dedicated intermediary component that handles the complexity of resource identifier parsing. By isolating the parsing logic in a separate module, the main application programs remain simple while the parser absorbs the complexity of interpreting various resource identifier formats and extracting relevant information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The parser is designed as a universal component that can handle multiple types of resource identifiers and extract various kinds of information. This multi-functional parser reduces overall system complexity by providing a single entry point for all resource identifier processing needs, rather than requiring separate parsing logic in each application.

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

3Reliability

If browser applications are used to access network resources, then resource access capability is maintained, but time consumption increases due to the need for browser mediation

Engineering Contradiction:
Improveresource accessVSAvoidaccess time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The essential functionality of extracting and utilizing resource identifier information is taken out from the browser application context and made available directly to non-browser applications. This extraction eliminates the mandatory mediation step of launching a browser, allowing applications to directly access and process network resource information in a more time-efficient manner while maintaining reliability through the parser's accurate information extraction.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS8862737B2Application integration of network data based on resource identifiers
Publication Date: 2014.10.14 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8862737B2 patent drawing
  • US8862737B2 patent drawing
  • US8862737B2 patent drawing

AI summary

A resource identifier parser can derive information from resource identifiers that are provided to non-browser application programs or the operating system, such as through the desktop area of a windows-based user interface. The resource identifier parser can understand the formatting of resource identifiers of specific domains and can derive therefrom information such as coordinates of a map page, the title of classified listings, and other like information. If the resource identifier cannot be parsed, the identified data page can be referenced to identify services offered by the page, such as data feed services, which can then be presented to the non-browser application program or the operating system to which the resource identifier was provided. As yet another alternative, the domain can provide a customized resource identifier parser to parse its resource identifiers. Such a customized parser can be either downloadable and locally executable or it can be a network service.