US6353839B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Method for inline variables management in a hypermedia display language
Assignee: Unwired Planet LLC
•
Filing: 1998-04-30
•
Granted: 2002-03-05
•
Expires: 2018-04-30
Abstract
Abstract To accept, store, and use dynamic information within a markup language, a markup language variable system is introduced. The markup language variable system allows variable scopes to be created within markup language user agents. Variables can then be assigned using static variable assignment via markup language tags or dynamic variable assignment via user requests. Variables can be used within markup language displays or within addresses such as Uniform Resource Locators (URLs). Automatic escaping ensures that variables are correctly modified for use within certain contexts such as URLs.
Inventors
- 👤 Peter F. King
- 👤 Russell S. Greer
- 👤 Bruce V. Schwartz
- 👤 Bruce K. Martin, Jr.
- 👤 Mark G. Lentczner
- 👤 Lawrence M. Stein
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-05 00:04
CPC Classifications
G; G06; G06F; G06F40/00; G06F40/10; G06F40/103; G06F40/117; G06F40/12; G06F40/14; G06F40/143
Claims Analysis
Total Claims: 35
Claim 1
Independent Claim
59 words
A method of processing a markup language in a thin-client device with an interpreter that does not use an auxiliary scripting language to perform the method, said method comprising: creating a first new activity frame to store variables in response to a markup; and processing subsequent markup language commands that refer to variables in said first new activity frame.
Claim 2
Independent Claim
59 words
A method of processing a markup language in a thin-client device with an interpreter that does not use an auxiliary scripting language to perform the method, said method comprising: creating a first new activity frame to store variables in response to a markup; and processing subsequent markup language commands that refer to variables in said first new activity frame.
Claim 3
Dependent Claim
32 words
The method as claimed in claim 1 further comprising: accepting an input from a user; and storing said input from said user into a variable associated with said first new activity frame.
Claim 4
Dependent Claim
26 words
The method as claimed in claim 1 wherein said creating a first new activity frame comprises adding a first new entry on an activity frame stack.
Claim 5
Dependent Claim
22 words
The method as claimed in claim 1 wherein said markup further comprises a parameter defining variables in said first new activity frame.
Claim 6
Dependent Claim
25 words
The method as claimed in claim 4 further comprising: creating a first new activity, said first new activity comprising a set of markup language commands.
Claim 7
Dependent Claim
20 words
The method as claimed in claim 5 further comprising: returning a set of variables when said first new activity completes.
Claim 8
Dependent Claim
30 words
The method as claimed in claim 5 wherein said markup defining a first new activity further comprises a destination that will be accessed when said first new activity completes normally.
Claim 9
Dependent Claim
35 words
The method as claimed in claim 5 wherein said markup defines said first new activity and comprises a destination that will be accessed when said first new activity terminates with a negative indication of success.
Claim 10
Dependent Claim
28 words
The method as claimed in claim 5 wherein said markup defines said first new activity and comprises a parameter that specifies if said first new activity is trusted.
Claim 11
Dependent Claim
30 words
The method as claimed in claim 9 further comprising: specifying a new destination that will be accessed after said first new activity completes if said first new activity is trusted.
Claim 12
Dependent Claim
27 words
The method as claimed in claim 10 further comprising: clearing variables in a calling activity from said first new activity if said first new activity is trusted.
Claim 13
Dependent Claim
33 words
The method as claimed in claim 5 further comprising: detecting a markup defining an end of said first new activity; and destroying said first new activity frame associated with said first new activity.
Claim 14
Dependent Claim
18 words
The method as claimed in claim 12 further comprising: returning a set of variables to a calling activity.
Claim 15
Dependent Claim
38 words
The method as claimed in claim 5 further comprising: detecting a markup defining a second new activity; and creating a second new activity frame to store variables, said second new activity frame associated with said second new activity.
Claim 16
Dependent Claim
25 words
The method as claimed in claim 14 wherein said creating a second new activity frame comprises adding a second new entry on an activity stack.
Claim 17
Dependent Claim
26 words
The method as claimed in claim 14 wherein said markup defining a second new activity further comprises a parameter defining variables in said second new activity.
Claim 18
Dependent Claim
39 words
The method as claimed in claim 14 wherein said markup defining a second new activity further comprises a list of variables that said second new activity will return to said first new activity when said second new activity completes.
Claim 19
Independent Claim
74 words
A method of processing a markup language in a thin-client device, said method comprising: calling a secondary markup language deck from a primary markup language deck; and detecting a public markup in a secondary markup language deck, said public markup defining if said secondary markup language deck is publicly accessible, ceasing processing of said secondary markup language deck if said primary markup language deck is not authorized to access said secondary markup language deck.
Claim 20
Independent Claim
74 words
A method of processing a markup language in a thin-client device, said method comprising: calling a secondary markup language deck from a primary markup language deck; and detecting a public markup in a secondary markup language deck, said public markup defining if said secondary markup language deck is publicly accessible, ceasing processing of said secondary markup language deck if said primary markup language deck is not authorized to access said secondary markup language deck.
Claim 21
Dependent Claim
36 words
The method as claimed in claim 18 wherein a determination if said primary markup language deck is authorized to access said secondary markup language deck is based upon an address of said primary markup language deck.
Claim 22
Dependent Claim
36 words
The method as claimed in claim 18 further comprising: detecting an accessdomain markup in said primary markup language deck, said accessdomain markup defining an Internet domain that is authorized to access said secondary markup language deck.
Claim 23
Dependent Claim
42 words
The method as claimed in claim 18 further comprising: detecting an accesspath markup in said secondary markup language deck, said accesspath markup defining a base deck system path of markup language decks that are authorized to access said secondary markup language deck.
Claim 24
Independent Claim
54 words
A method of processing a markup language in a thin-client device that does not use an auxiliary scripting language to perform the method, said method comprising: parsing markup language file containing a variable reference; and replacing said variable reference with a variable value when a markup language file containing said variable reference is processed.
Claim 25
Independent Claim
54 words
A method of processing a markup language in a thin-client device that does not use an auxiliary scripting language to perform the method, said method comprising: parsing markup language file containing a variable reference; and replacing said variable reference with a variable value when a markup language file containing said variable reference is processed.
Claim 26
Independent Claim
53 words
A method of processing a markup language in a thin-client device that does not use an auxiliary scripting language to perform the method, said method comprising: accepting user input from said user; setting a first variable according to said input from said user; and storing said first variable in a current activity frame.
Claim 27
Independent Claim
53 words
A method of processing a markup language in a thin-client device that does not use an auxiliary scripting language to perform the method, said method comprising: accepting user input from said user; setting a first variable according to said input from said user; and storing said first variable in a current activity frame.
Claim 28
Dependent Claim
29 words
The method as claimed in claim 23 further comprising: detecting a markup requesting user input, said markup specifying said first variable that will be set by said user input.
Claim 29
Dependent Claim
31 words
The method as claimed in claim 24 further comprising: displaying a menu, said menu comprising at least one menu item; and setting a second variable according to a menu item selected.
Claim 30
Dependent Claim
13 words
The method as claimed in claim 23 wherein user input comprises alphanumeric text.
Claim 31
Dependent Claim
19 words
The method as claimed in claim 23 wherein a default parameter specifies a default value of said first variable.
Claim 32
Independent Claim
55 words
A method of processing a markup language file in a thin-client device that does not use an auxiliary scripting language to perform the method, said method comprising: parsing a string containing a variable reference; and replacing said variable reference with a variable value modified depending upon the context of said variable reference in said string.
Claim 33
Independent Claim
55 words
A method of processing a markup language file in a thin-client device that does not use an auxiliary scripting language to perform the method, said method comprising: parsing a string containing a variable reference; and replacing said variable reference with a variable value modified depending upon the context of said variable reference in said string.
Claim 34
Dependent Claim
24 words
The method of claim 28 wherein said variable value is modified to make said variable value acceptable for use in a Uniform Resource Locator.
Claim 35
Dependent Claim
23 words
The method of claim 28 wherein said variable reference is replaced with said variable value during the display of said markup language file.
References Cited (Backward Citations)
US5838906A
Cited
US5623656A
Cited
US5907704A
Cited
US6011546A
Cited
US5966535A
Cited
US5961601A
Cited
US5928324A
Cited
US5930341A
Cited
US6108406A
Cited
US5948066A
Cited
US5991760A
Cited
US6076099A
Cited
US6065120A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2005-03-04 | 2005-09-03 | 2006-03-05 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2009-03-04 | 2009-09-03 | 2010-03-05 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2013-03-04 | 2013-09-03 | 2014-03-05 | $7700.00 | Window Closed / Lapsed |