IP Library Granted Patent US 12,307,083
Granted Patent B2
US 12,307,083 · App. 18/225,412 · Granted May 20, 2025

System and method for specifying properties for a protocol-compliant uniform resource locator

Inventors: Scott David Shaw (Stockley, GB); Jack Llewellyn Cockerell (Kemble, GB)
Assignee: Hexagon Technology Center GmbH
G06F3/0486G06F3/04817G06F3/0482G06F9/451G06F16/9566G06F2203/04803
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,307,083
App. No.
18/225,412
Granted
May 20, 2025
Kind
B2
Abstract

A graphical user interface is configured to guide a user through a method of creating a RESTful API protocol-compliant URL, without requiring that the user be familiar with syntax of the RESTful API protocol. The graphical user interface includes a URL output that indicates to the user features within a user-edited URL that render the user-edited URL non-compliant with the RESTful API protocol. The graphical user interface includes a set of graphical input devices to solicit and receive from the user input specifying a set of query options, which user input is used to define the RESTful API protocol-compliant URL. The graphical user interface is automatically customized to solicit and receive from the user input only for options available from a specific data service.

Claims (56)

1. A method of creating a uniform resource locator that complies with a RESTful API protocol (a “protocol-compliant” URL) at a computer remote from a data service, the method comprising:

obtaining, from a metadata source, metadata describing source data available from the data service;

customizing a graphical user interface (“GUI”) by populating a set of graphical input devices within the GUI with information specified by the metadata, such that the GUI is configured to solicit and receive user input specifying a set of query options to request, from the data service, data available from the data service, wherein customizing the graphical user interface comprises:

populating and displaying first window with a set of column icons, each column icon of the set of column icons associated with corresponding data available from the data service, and each column icon of the set of column icons specified by the metadata from the metadata source; and

providing a second window configured to receive one or more column icons dragged from the first window and dropped into the second window;

receiving user input via the graphical user interface, the user input comprising receipt at the second window of at least one column icon of the set of column icons dragged from the first window and dropped into the second window; and

generating the protocol-compliant uniform resource locator by application of a set of rules to the user input, the protocol-compliant uniform resource locator configured to solicit from the data source response data defined by the user input.

2. The method of claim 1 , wherein:

receiving at the second window a plurality of column icons from the set of column icons, said plurality of column icons arranged in a column order in the second window; and wherein:

generating the protocol-compliant uniform resource locator by application of a set of rules to the user input comprises generating the protocol-compliant uniform resource locator configured to solicit from the data source responsive data defined by the user input, and in the column order.

3. The method of claim 1 , wherein the metadata source is the data service.

4. The method of claim 1 , wherein application of a rule from the set of rules comprises applying a rule that formats the user input into a format defined by the RESTful API protocol.

5. The method of claim 1 , wherein application of a rule from the set of rules comprises adding, to the user input, a prefix defined by the RESTful API protocol.

6. The method of claim 1 , wherein generating the protocol-compliant uniform resource locator by application of a set of rules to the user input comprises, for at least one item of user input:

appending a prefix to said user input and adding the prefix and user input to the protocol-compliant uniform resource locator.

7. The method of claim 1 , wherein:

the metadata describes a plurality of categories of source data available from the available from the data service;

customizing a graphical user interface comprises providing a third graphical input device configured to receive user input specifying a set of filters, wherein each filter further limits the data of a selected category provided as responsive data; and wherein

receiving user input via the graphical user interface comprises receiving user specification of each filter in the set of filters; and wherein

generating the protocol-compliant uniform resource locator by application of a set of rules to the user input comprises formatting said specification of each filter in the set of filters into a format defined by the RESTful API protocol, such that protocol-compliant uniform resource locator is configured to cause the data service to provide, as responsive data, a filtered subset of source data from the selected category.

8. A computer-implemented system for creating a uniform resource locator that complies with a RESTful API protocol, said uniform resource locator being a “protocol-compliant” URL, for requesting source data from a data service, the system comprising:

a communications interface configured to obtain, from a metadata source, metadata describing source data available from the data service;

a graphical user interface driver configured to customize a graphical user interface (“GUI”) by populating a set of graphical input devices within the GUI with information specified by the metadata, such that the GUI is configured to solicit and receive user input specifying a set of query options to request, from the data service, data available from the data service, wherein customizing the graphical user interface comprises:

populating and displaying first window with a set of column icons, each column icon of the set of column icons associated with corresponding data available from the data service, and each column icon of the set of column icons specified by the metadata from the metadata source; and

providing a second window configured to receive one or more column icons dragged from the first window and dropped into the second window; and

a protocol-compliant URL generator configured:

to receive user input comprising receipt at the second window of at least one column icon of the set of column icons dragged from the first window and dropped into the second window, and

to apply a set of rules to the user input, said user input comprising to produce, from said user input, a protocol-compliant URL.

9. The computer-implemented system of claim 8 , wherein

receiving at the second window of at least one column icon comprises receiving a plurality of column icons from the set of column icons, said plurality of column icons arranged in a column order in the second window; and wherein:

generating the protocol-compliant uniform resource locator by application of a set of rules to the user input comprises generating the protocol-compliant uniform resource locator configured to solicit from the data source responsive data defined by the user input, and in the column order.

10. The computer-implemented system of claim 8 , wherein the metadata source is the data service.

11. The computer-implemented system of claim 8 , wherein application of a set of rules comprises applying a rule that formats the user input into a format defined by the RESTful API protocol.

12. The computer-implemented system of claim 8 , wherein application of a set of rules comprises adding, to at least one item of the user input, a prefix defined by the RESTful API protocol.

13. The computer-implemented system of claim 8 , wherein generating the protocol-compliant uniform resource locator by application of a set of rules to the user input comprises, for at least one item of user input:

appending a prefix to said user input and adding the prefix and user input to the protocol-compliant uniform resource locator.

14. The computer-implemented system of claim 8 , wherein

the metadata describes a plurality of categories of source data available from the available from the data service;

customizing a graphical user interface comprises providing a third graphical input device configured to receive user input specifying a set of filters, wherein each filter further limits the data of a selected category provided as responsive data; and wherein

receiving user input via the graphical user interface comprises receiving user specification of each filter in the set of filters; and wherein

generating the protocol-compliant uniform resource locator by application of a set of rules to the user input comprises formatting said specification of each filter in the set of filters into a format defined by the RESTful API protocol, such that protocol-compliant uniform resource locator is configured to cause the data service to provide, as responsive data, a filtered subset of source data from the selected category.

15. A non-transitory computer-readable medium having computer code thereon, the computer code configured to be executed by a computer, the computer code causing the computer to execute a method comprising:

obtaining, from a metadata source, metadata describing source data available from the data service;

customizing a graphical user interface (“GUI”) by populating a set of graphical input devices within the GUI with information specified by the metadata, such that the GUI is configured to solicit and receive user input specifying a set of query options to request, from the data service, data available from the data service, wherein customizing the graphical user interface comprises:

populating and displaying first window with a set of column icons, each column icon of the set of column icons associated with corresponding data available from the data service, and each column icon of the set of column icons specified by the metadata from the metadata source; and

providing a second window configured to receive one or more column icons dragged from the first window and dropped into the second window;

receiving user input via the graphical user interface, the user input comprising receipt at the second window of at least one column icon of the set of column icons dragged from the first window and dropped into the second window; and

generating the protocol-compliant uniform resource locator by application of a set of rules to the user input, the protocol-compliant uniform resource locator configured to solicit from the data source response data defined by the user input.

16. The non-transitory computer-readable medium of claim 15 , wherein the method further comprises:

receiving at the second window a plurality of column icons from the set of column, said plurality of column icons arranged in a column order in the second window; and wherein:

generating the protocol-compliant uniform resource locator by application of a set of rules to the user input comprises generating the protocol-compliant uniform resource locator configured to solicit from the data source responsive data defined by the user input, and in the column order.

17. The non-transitory computer-readable medium of claim 15 , wherein the metadata source is the data service.

18. The non-transitory computer-readable medium of claim 15 , wherein application of a rule from the set of rules comprises applying a rule that formats the user input into a format defined by the RESTful API protocol.

19. The non-transitory computer-readable medium of claim 15 , wherein application of a rule from the set of rules comprises adding, to at least one item of the user input, a prefix defined by the RESTful API protocol.

20. The non-transitory computer-readable medium of claim 15 , wherein generating the protocol-compliant uniform resource locator by application of a set of rules to the user input comprises, for at least one item of user input:

appending a prefix to said user input and adding the prefix and user input to the protocol-compliant uniform resource locator.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 10, 2023
From: SHAW, SCOTT DAVID; COCKERELL, JACK LLEWELLYN
To: HEXAGON TECHNOLOGY CENTER GMBH
Reel/Frame 064551/0867 →
Continuity (4)
Continuation In Part 18143809 · May 5, 2023
Continuation In Part 18096815 · Jan 13, 2023
Continuation In Part 17691877 · Mar 10, 2022
Related Publication 20230367471A1 · Nov 16, 2023
References Cited (28)
US 7519688B2 · Behrens et al. · 2009 [cited by applicant]
US 8429189B1 · Spielberg et al. · 2013 [cited by applicant]
US 11570230B1 · Shaw et al. · 2023 [cited by applicant]
US 11995296B2 · Shaw · 2024 [cited by examiner]
US 20060155529A1 · Ludviksson et al. · 2006 [cited by applicant]
US 20100235469A1 · Morris · 2010 [cited by applicant]
US 20130110978A1 · Gordon · 2013 [cited by examiner]
US 20140250377A1 · Bisca et al. · 2014 [cited by applicant]
US 20140372956A1 · Bisca et al. · 2014 [cited by applicant]
US 20150294377A1 · Chow · 2015 [cited by applicant]
US 20160253708A1 · Mody et al. · 2016 [cited by applicant]
US 20170012920A1 · Chheda et al. · 2017 [cited by applicant]
US 20170021356A1 · Dority et al. · 2017 [cited by applicant]
US 20170094017A1 · Jakobs · 2017 [cited by applicant]
US 20170155736A1 · Schukovets et al. · 2017 [cited by applicant]
US 20170364346A1 · Peng et al. · 2017 [cited by applicant]
US 20180107525A1 · Govindaraju et al. · 2018 [cited by applicant]
US 20180217818A1 · Douglas et al. · 2018 [cited by applicant]
US 20190028360A1 · Douglas et al. · 2019 [cited by applicant]
US 20200267435A1 · Gordon · 2020 [cited by examiner]
US 20200293680A1 · Navarro-Dimm et al. · 2020 [cited by applicant]
US 20220182699A1 · Gordon · 2022 [cited by examiner]
US 20230289041A1 · Shaw · 2023 [cited by examiner]
US 20230350965A1 · Shaw · 2023 [cited by examiner]
US 20230367471A1 · Shaw · 2023 [cited by examiner]
US 20230418828A1 · Shaw · 2023 [cited by examiner]
Author Unknown—Oasis Committee Note “What's New in Odata,” Version 4.01, dated Sep. 26, 2019, 488 pages. [cited by applicant]
Author Unknown—PragmatiQa XOData: “Overview with an Example,” doc version 1.3, 12 pages, undated. [cited by applicant]