A technique for automatically generating browsable language grammars. A grammar specification is used to identify the structure of an input grammar, so that a specification pre-processor, grammar parser and grammar generator can work together to generate a marked up grammar that is a browsable representation of the input grammar. The specification defines how a terminal is represented, how a non-terminal is represented, how production rules are represented, etc. Using the specification, the specification pre-processor generates the grammar parser for subsequent use with production rules found in the input grammar. When an actual set of production rules in the input grammar are provided to the grammar parser, it generates an intermediate form of the grammar that is then used by the grammar generator to generate the browsable, marked up version of the production rules.
|
1. A computer-implemented method for automatically generating a browsable language grammar, comprising:
(a) processing a grammar specification in a specification pre-processor to generate a grammar parser for subsequent use with production rules of an input grammar, wherein the grammar specification comprises a specified format of the input grammar; (b) parsing one or more of the production rules of the input grammar in the grammar parser to generate an intermediate form of a grammar; and (c) generating a marked up grammar in a grammar generator from the intermediate form of the grammar.
9. A system for automatically generating browsable language grammars, comprising:
(a) means for processing a grammar specification in a specification pre-processor to generate a grammar parser for subsequent use with production rules of an input grammar, wherein the grammar specification comprises a specified format of the input grammar; (b) means for parsing one or more of the production rules of the input grammar in the grammar parser to generate an intermediate form of a grammar; and (c) means for generating a marked up grammar in a grammar generator from the intermediate form of the grammar.
17. An article of manufacture embodying logic for performing a method for automatically generating browsable language grammars, comprising:
(a) processing a grammar specification in a specification pre-processor to generate a grammar parser for subsequent use with production rules of an input grammar, wherein the grammar specification comprises a specified format of the input grammar; (b) parsing one or more of the production rules of the input grammar in the grammar parser to generate an intermediate form of a grammar; and (c) generating a marked up grammar in a grammar generator from the intermediate form of the grammar.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
a non-terminal on a left-hand-side of a production rule pointing to its occurrence on a right-hand-side of a production rule; a non-terminal on a right side of a production rule pointing to its next and/or previous occurrence in a same or another production rule; a method for traversing from a right-hand-side occurrence of a production rule to its left-hand-side occurrence; a method for traversing from a right-hand side occurrence of a non-terminal to a particular occurrence of a non-terminal on a left-hand side of a production; a method for navigating over all production rules in which a particular non-terminal occurs on a left-hand side; a method for navigating over all production rules; a method for viewing all non-terminal occurrences in the set of production rules from a non-terminal; and a method optionally viewing semantic comments associated with one or more of the production rules.
8. The method of
a function for displaying a production rule for an item in the marked up grammar; a function for displaying a previous right-hand-side occurrence for an item in the marked up grammar; a function for displaying a next right-hand-side occurrence for an item in the marked up grammar; a function for displaying all occurrences of a non-terminal item in the marked up grammar; and a function for displaying comments associated with an item in the marked up grammar.
10. The system of
11. The system of
12. The system of
13. The system of
14. The system of
15. The system of
a non-terminal on a left-hand-side of a production rule pointing to its occurrence on a right-hand-side of a production rule; a non-terminal on a right side of a production rule pointing to its next and/or previous occurrence in a same or another production rule; a method for traversing from a right-hand-side occurrence of a production rule to its left-hand-side occurrence; a method for traversing from a right-hand side occurrence of a non-terminal to a particular occurrence of a non-terminal on a left-hand side of a production; a method for navigating over all production rules in which a particular non-terminal occurs on a left-hand side; a method for navigating over all production rules; a method for viewing all non-terminal occurrences in the set of production rules from a non-terminal; and a method optionally viewing semantic comments associated with one or more of the production rules.
16. The system of
a function for displaying a production rule for an item in the marked up grammar; a function for displaying a previous right-hand-side occurrence for an item in the marked up grammar; a function for displaying a next right-hand-side occurrence for an item in the marked up grammar; a function for displaying all occurrences of a non-terminal item in the marked up grammar; and a function for displaying comments associated with an item in the marked up grammar.
18. The article of manufacture of
19. The article of manufacture of
20. The article of manufacture of
21. The article of manufacture of
22. The article of manufacture of
23. The article of manufacture of
a non-terminal on a left-hand-side of a production rule pointing to its occurrence on a right-hand-side of a production rule; a non-terminal on a right side of a production rule pointing to its next and/or previous occurrence in a same or another production rule; a method for traversing from a right-hand-side occurrence of a production rule to its left-hand-side occurrence; a method for traversing from a right-hand side occurrence of a non-terminal to a particular occurrence of a non-terminal on a left-hand side of a production; a method for navigating over all production rules in which a particular non-terminal occurs on a left-hand side; a method for navigating over all production rules; a method for viewing all non-terminal occurrences in the set of production rules from a non-terminal; and a method optionally viewing semantic comments associated with one or more of the production rules.
24. The article of manufacture of
a function for displaying a production rule for an item in the marked up grammar; a function for displaying a previous right-hand-side occurrence for an item in the marked up grammar; a function for displaying a next right-hand-side occurrence for an item in the marked up grammar; a function for displaying all occurrences of a non-terminal item in the marked up grammar; and a function for displaying comments associated with an item in the marked up grammar.
|
|||||||||||||||||||||||||||||||||||
1. Field of the Invention
This invention relates in general to language grammars, and in particular, to a system for automatically generating browsable language grammars.
2. Description of Related Art
The World Wide Web (WWW) of the Internet has become the primary medium for communication and collaboration. Internet browsers have become ubiquitous as viewers and editors for documents. As a result, methods used to share, read, and update documents have changed significantly.
For example, as new specifications for programming languages, script languages, meta-data, etc., are drafted, browsable versions of these specifications are usually published on the Internet. Such specifications usually are published in the form of a grammar having production rules.
For people reading these specifications using a browser, it is useful to mark up production rules within the grammars to make them more understandable. Some publishers hand-code the production rules to make them more browsable, while other publishers do not make the production rules browsable at all.
In one example, U.S. Pat. No. 5,678,052 describes a method and system for converting a text-based Backus-Naur Form (BNF) grammar into a compressed syntax diagram. In another example, U.S. Pat. No. 5,526,522 describes an automatic program generating system that performs recursive conversion of a program specification into a syntactic tree format.
However, there is still a need then for a mechanism that automatically marks up grammar production rules to enhance their readability and accessibility. There is also a need for such mechanisms that are implemented using standardized markup languages.
To overcome the limitations in the prior art described above, and to overcome other limitations that will become apparent upon reading and understanding the present specification, the present invention discloses a method, system and article of manufacture for automatically generating browsable language grammars. A grammar specification is used to identify the structure of an input grammar, so that a specification pre-processor, grammar parser and grammar generator can work together to generate a marked up grammar that is a browsable representation of the input grammar. The specification defines how a terminal is represented, how a non-terminal is represented, how production rules are represented, etc. Using the specification, the specification pre-processor generates the grammar parser for subsequent use with production rules found in the input grammar. When an actual set of production rules of an input grammar are provided to the grammar parser, it generates an intermediate form of the grammar that is then used by the grammar generator to generate the browsable, marked up version of the input grammar.
Referring now to the drawings in which like reference numbers represent corresponding parts throughout:
In the following description of the preferred embodiment, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration a specific embodiment in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural and functional changes may be made without departing from the scope of the present invention.
The preferred embodiment of the present invention describes a technique for automatically marking up grammar production rules in a manner that enhances their readability and accessibility. A meta-language specification specifies the production rules of a grammar. For example, the specification defines how a terminal is represented (within quotes, etc.), how a non-terminal is represented (as names with their first letter capitalized, etc.), how productions are represented (what is the arrow "→" character for a productions, etc.). Using the specification, the system generates a parser for production rules found in an input grammar. When an actual set of production rules of an input grammar are provided to this parser, it generates an intermediate form of the input grammar that is then used by a grammar generator to generate a browsable, marked up version of the production rules.
However, those skilled in the art will recognize that the exemplary environment and components illustrated in
The preferred embodiment of the present invention is comprised of a number of different components executed by the server computer 104. A specification pre-processor 106 accepts a grammar specification 108, recognizes elements within the specification 108 for the grammar language, processes each of these elements, and generates the instructions for a grammar parser 110 accordingly. The grammar parser 110 accepts an input grammar 112, recognizes elements within the input grammar 112, and transforms the input grammar 112 into an intermediate form recognizable by a grammar generator 114. The grammar generator 114 translates or converts the intermediate form of the input grammar 114 to generate a browsable, marked up grammar 116.
In general, the specification pre-processor 106, grammar specification 108, grammar parser 110, input grammar 112, grammar generator 114, and browsable, marked up grammar 116 each are comprised of data and/or instructions which, when read, interpreted, and/or executed by the server computer 104, causes the computer 104 to perform the steps for performing and/or using the present invention. Generally, the data and/or instructions are embodied in and/or readable from a device, carrier or media, such as memory, data storage devices, and/or remote devices coupled to the computer 104 via data communications devices.
Thus, the present invention may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, hardware, firmware, or any combination thereof. In addition, the term "article of manufacture" as used herein is intended to encompass logic and/or data embodied in or accessible from any device, carrier, or media.
The syntax for a programming language is often represented in terms of a grammar having one or more production rules. Such grammars have terminals and non-terminals, wherein terminals are tokens or strings of the programming language and non-terminals are variables that can recursively expand to a sequence of terminals and non-terminals. Production rules for the grammar are typically expressed in BNF (Backus-Naur Form) or EBNF (extended BNF).
To generate a browsable, marked up grammar 116 in the preferred embodiment of the present invention, the following steps are performed:
1. A grammar specification 108 for the syntax of the grammar is provided to the specification pre-processor 106. An exemplary grammar specification 108 is illustrated in FIG. 2A. This specification 108 identifies the format of terminals, non-terminals, production operators, comments, right-hand-side separators for production rules, and empty production rules. Note that the specification 108 provided herein is fairly simple, but more complex specifications 108 could be used as well.
2. The specification pre-processor 106 uses this grammar specification 108 to generate and configure the grammar parser 110, which in turn can process any input grammar 112 written using this syntax or convention. Note that the programming of such grammar parsers 110 are well known in the art, and thus is not described further herein.
3. Once the grammar parser 110 is built, any set of production rules of an input grammar 112 written in this syntax can be processed by the parser 110. An exemplary input grammar 112 is illustrated in FIG. 2B. In this example, non-terminals are represented by names with the first letter in upper case, terminals are described as quoted strings, the arrows in the productions are represented as "→" (an equals sign followed by a greater-than sign), alternative right-hand-sides for the same left-hand-side are represented using "|" (vertical bars), empty productions are represented by putting an "e" on the right-hand-side, and comments are enclosed in "{ . . . }" (braces).
4. The grammar parser 110 is a front-end to the grammar generator 114, and generates an intermediate or common form of the input grammar 112 (such as a representation of BNF or EBNF) for use by the grammar generator 114. The grammar generator 114 parses any production rules from the intermediate form and generates a marked up grammar 116 as its output, wherein the marked up grammar 116 embodies the production rules of the input grammar 112 in a form suitable for browsing. An exemplary fragment of a marked up grammar 116 (comprising only the production rules labeled as "Top level production rules" in
The following semantics for marking up the production rules in the marked up grammar 116 are desirable although not required:
1. A non-terminal on the left-hand-side of a production rule points to its occurrence on the right-hand-side of a production rule.
2. A non-terminal on the right side of a production rule points to its next and/or previous occurrence in the same or another production rule.
3. There is a mechanism for traversing from the right-hand-side occurrence of a production rule to its left-hand-side occurrence.
4. There is a facility for traversing from the right-hand side occurrence of a non-terminal to a particular (e.g., first) occurrence of the non-terminal on the left-hand side of a production.
5. There is a facility for navigating over all the production rules in which a particular non-terminal occurs on the left-hand side.
6. There is a facility for navigating over all the production rules.
7. There is a mechanism for viewing all the non-terminal occurrences in the production rules from a non-terminal.
8. There is a mechanism for optionally viewing semantic comments associated with production rules.
In the example of
For example, the occurrence of "IfThenStatement" on the right-hand-side points to "#IfThenStatement", which refers to an HTML table that corresponds to the "IfThenStatement" non-terminal. Similarly, the HTML for "Top level production" described above is labeled "Statement" (because Statement is the left-hand-side non-terminal) through the "name" attribute of the <a> tag. Another production can refer to this using "#Statement".
The marked up grammar 116 is in an HTML format in the preferred embodiment because HTML is the moss widely used browser language on the Internet. However, HTML only implements a single directional link and does not include multidimensional links.
The present invention overcomes this problem by associating pop-up menus with an item in order to provide the semantics described above for marking up the production rules. For example, a marked up non-terminal on the right-hand-side of a production rule will have a pop-up menu with the following 5 menu items:
i. Go to its production rule.
ii. Go to its previous right-hand-side occurrence.
iii. Go to its next right-hand-side occurrence.
v. Show any comments associated with the item.
Moreover, those skilled in the art will recognize that the translation of the input grammar 114 to a marked up grammar 116 in an HTML format can achieve any number of different visual and navigational effects.
Although the grammar generator 116 in the preferred embodiment translates the production rules of the input grammar 112 into an HTML format, an alternative embodiment may generate the marked up grammar 116 in an eXtensible Markup Language (XML) format or the fan Cat of another mark up language. If the marked up grammar 116 is generated in an XML format, more powerful XML-style links (multi-dimensional links, semantic links, etc.) may be used for a better browsing experience.
For example, an Xlink extended link group can be formed corresponding to each non-terminal in the input grammar 112. The extended link, unlike a simple HTML link, can connect multiple resources (with possible one local resource).
For example, an Xlink extended link group can he generated for non-terminals as follows:
</nt-group-1 xml:link="extended" inline="false">
<locator href="#Statement.occ1" role="left-hand-side"/>
<locator href="#Statement.occ2" role="right-hand-side"/>
<locator href="#Statement.occ3" role="right-hand-side"/>
</nt-group>
In the above example, three occurrences of the non-terminal "Statement" are listed, one of them being its left-hand-side occurrence, and the others being its right-hand-side occurrences (this is indicated using the "role" attribute). Thus, using extended links, the left-hand-side occurrence of a non-terminal can be linked to each of its right-hand-side occurrences, which can be used in a visual display system to traverse over the occurrence of the same non-terminal across productions.
There are other attributes to the Xlink element like "show" (which describes a policy of how the link should be displayed when the resource is traversed), and "actuate" (which describes a policy for when to traverse a link). These attributes could be used in conjunction with the other Xlink attribute to generate different traversal behaviors.
In yet another embodiment, the marked up grammar 116 may be generated in an XML format, and converted again to an HTML/Dynamic HTML (HTML+scripts) format using a style-sheet specification language such as XSL.
Another advantage to generating the marked up grammar 116 in an XML format is that it is more general than HTML, and can be used for purposes other than just browsing. For example, XML provides a facility where tag names can be specified as belonging to different name spaces. The idea behind providing such a facility is that different processors can act on different parts of the same XML document by processing only those tags in the name space that they understand and ignoring other name spaces.
Thus, the grammar specification 108, input grammar 112, and browsable, marked up grammar 116 could each have their own name spaces within one or more XML documents. Further, the specification pre-processor 106, grammar parser 110, and grammar generator 114, and browsable, marked up grammar 116 could each operate only on their respective associated name space(s) of an XML document.
Block 300 represents the grammar parser 110 initializing.
Block 302 represents the specification pre-processor 106 accepting the grammar specification 108.
Block 304 represents the specification pre-processor 106 generating the instructions for a grammar parser 110 from the grammar specification 108.
Block 306 represents the grammar parser 110 initializing.
Block 308 represents the grammar parser 110 accepting the input grammar 112.
Block 310 represents the grammar parser 110 transforming the input grammar 112 into an intermediate form recognizable by a grammar generator 114.
Block 312 represents the grammar generator 114 initializing.
Block 314 represents the grammar generator 114 accepting the intermediate form from the grammar parser 110.
Block 300 represents the grammar generator 114 translating or converting the intermediate form of the input grammar 114 and generating the browsable, marked up grammar 116 accordingly.
This concludes the description of the preferred embodiment of the invention. The following describes some alternative embodiments for accomplishing the present invention. For example, any type of computer, such as a mainframe, minicomputer, or personal computer, could be used to implement the present invention. In addition, the computer may or may not be part of a network. Further, the present invention is not limited to specific formats recited herein for the grammar specifications, input grammars, or marked up grammars. For example, the marked up grammars could be generated in any number of different formats other than HTML or XML.
In summary, the present invention discloses a method, system, and article of manufacture for automatically generating browsable language grammars. A grammar specification is used to identify the structure of an input grammar, so that a specification pre-processor, grammar parser and grammar generator can work together to generate a marked up grammar that is a browsable representation of the input grammar. The specification defines how a terminal is represented, how a non-terminal is represented, how production rules are represented, etc. Using the specification, the specification pre-processor generates the grammar parser for subsequent use with production rules found in the input grammar. When an actual set of production rules of an input grammar are provided to the grammar parser, it generates an intermediate form of the grammar that is then used by the grammar generator to generate the browsable, marked up version of the production rules.
The foregoing description of the preferred embodiment of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto.
| Patent | Priority | Assignee | Title |
| 6591260, | Jan 28 2000 | Red Hat, Inc | Method of retrieving schemas for interpreting documents in an electronic commerce system |
| 6675370, | Feb 02 2000 | GOOGLE LLC | System and method for imbedding hyperlinked language grammar notation in a "literate" programming environment |
| 6782379, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Preparing output XML based on selected programs and XML templates |
| 6789127, | Feb 15 2000 | Lucent Technologies Inc | Preparation for network interface recognition of network packet portion with declarative notation for field thereof and constraint therefor |
| 6816871, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Delivering output XML with dynamically selectable processing |
| 6829745, | Jun 28 2001 | Pendragon Wireless LLC | Method and system for transforming an XML document to at least one XML document structured according to a subset of a set of XML grammar rules |
| 6930235, | Mar 15 2001 | MS Squared | System and method for relating electromagnetic waves to sound waves |
| 6954896, | Sep 03 1999 | Cisco Technology, Inc. | Browser-based arrangement for developing voice enabled web applications using extensible markup language documents |
| 6985910, | Feb 06 2003 | KYNDRYL, INC | Tilting tree spinning cones method and system for mapping XML to n-dimensional data structure using a single dimensional mapping array |
| 7017143, | Dec 01 1999 | Microsoft Technology Licensing, LLC | External resource files for application development and management |
| 7043686, | Feb 04 2000 | International Business Machines Corporation | Data compression apparatus, database system, data communication system, data compression method, storage medium and program transmission apparatus |
| 7080004, | Dec 05 2001 | Microsoft Technology Licensing, LLC | Grammar authoring system |
| 7152221, | Dec 01 1999 | Microsoft Technology Licensing, LLC | External resource files for application development and management |
| 7213249, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Blocking cache flush requests until completing current pending requests in a local server and remote server |
| 7216163, | May 15 2002 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Method and apparatus for provisioning tasks using a provisioning bridge server |
| 7225256, | Nov 30 2001 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Impersonation in an access system |
| 7243335, | Feb 17 2000 | Microsoft Technology Licensing, LLC | Method and system for reducing coding complexity by providing intelligent manipulable defaults |
| 7257529, | Sep 10 2001 | Intel Corporation | Apparatus and method for an automated grammar file expansion tool |
| 7340447, | Oct 09 2003 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Partitioning data access requests |
| 7349912, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Runtime modification of entries in an identity system |
| 7363339, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Determining group membership |
| 7380008, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Proxy system |
| 7415607, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Obtaining and maintaining real time certificate status |
| 7475136, | May 15 2002 | Oracle International Corporation | Method and apparatus for provisioning tasks using a provisioning bridge server |
| 7475151, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Policies for modifying group membership |
| 7581011, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Template based workflow definition |
| 7630974, | Sep 28 2004 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Multi-language support for enterprise identity and access management |
| 7673047, | Dec 22 2000 | Oracle International Corporation | Determining a user's groups |
| 7673227, | Jun 21 2000 | Microsoft Technology Licensing, LLC | User interface for integrated spreadsheets and word processing tables |
| 7673228, | Mar 30 2005 | Microsoft Technology Licensing, LLC | Data-driven actions for network forms |
| 7676843, | May 27 2004 | Microsoft Technology Licensing, LLC | Executing applications at appropriate trust levels |
| 7689929, | Jun 21 2000 | Microsoft Technology Licensing, LLC | Methods and systems of providing information to computer users |
| 7692636, | Sep 30 2004 | Microsoft Technology Licensing, LLC | Systems and methods for handwriting to a screen |
| 7711818, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Support for multiple data stores |
| 7721190, | Nov 16 2004 | Microsoft Technology Licensing, LLC | Methods and systems for server side form processing |
| 7725834, | Mar 04 2005 | Microsoft Technology Licensing, LLC | Designer-created aspect for an electronic form template |
| 7743063, | Jun 21 2000 | Microsoft Technology Licensing, LLC | Methods and systems for delivering software via a network |
| 7765298, | Nov 30 2001 | Campbell ERS LLC | Impersonation in an access system |
| 7774620, | May 27 2004 | Microsoft Technology Licensing, LLC | Executing applications at appropriate trust levels |
| 7779027, | Jun 21 2000 | Microsoft Technology Licensing, LLC | Methods, systems, architectures and data structures for delivering software via a network |
| 7802174, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Domain based workflows |
| 7818677, | Jun 21 2000 | Microsoft Technology Licensing, LLC | Single window navigation methods and systems |
| 7840658, | May 15 2002 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Employing job code attributes in provisioning |
| 7865477, | Mar 28 2003 | Microsoft Technology Licensing, LLC | System and method for real-time validation of structured data files |
| 7882132, | Oct 09 2003 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Support for RDBMS in LDAP system |
| 7900134, | Jun 21 2000 | Microsoft Technology Licensing, LLC | Authoring arbitrary XML documents using DHTML and XSLT |
| 7904487, | Oct 09 2003 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Translating data access requests |
| 7913159, | Mar 28 2003 | Microsoft Technology Licensing, LLC | System and method for real-time validation of structured data files |
| 7925621, | Mar 24 2003 | Microsoft Technology Licensing, LLC | Installing a solution |
| 7937651, | Jan 14 2005 | Microsoft Technology Licensing, LLC | Structural editing operations for network forms |
| 7937655, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Workflows with associated processes |
| 7971139, | Aug 06 2003 | Microsoft Technology Licensing, LLC | Correlation, association, or correspondence of electronic forms |
| 7979856, | Jun 21 2000 | Microsoft Technology Licensing, LLC | Network-based software extensions |
| 8001459, | Dec 05 2005 | Microsoft Technology Licensing, LLC | Enabling electronic documents for limited-capability computing devices |
| 8010343, | Dec 15 2005 | Microsoft Technology Licensing, LLC | Disambiguation systems and methods for use in generating grammars |
| 8010515, | Apr 15 2005 | Microsoft Technology Licensing, LLC | Query to an electronic form |
| 8015600, | Dec 22 2000 | ORACLE, USA; Oracle International Corporation; Oracle Corporation | Employing electronic certificate workflows |
| 8074217, | Jun 21 2000 | Microsoft Technology Licensing, LLC | Methods and systems for delivering software |
| 8117552, | Mar 24 2003 | Microsoft Technology Licensing, LLC | Incrementally designing electronic forms and hierarchical schemas |
| 8200975, | Jun 29 2005 | Microsoft Technology Licensing, LLC | Digital signatures for network forms |
| 8219385, | Apr 08 2008 | GOOGLE LLC | Computer-implemented method and system for conducting a search of electronically stored information |
| 8229733, | Feb 09 2006 | Method and apparatus for linguistic independent parsing in a natural language systems | |
| 8429522, | Aug 06 2003 | Microsoft Technology Licensing, LLC | Correlation, association, or correspondence of electronic forms |
| 8487879, | Oct 29 2004 | Microsoft Technology Licensing, LLC | Systems and methods for interacting with a computer through handwriting to a screen |
| 8676711, | Jun 10 2005 | Payment method and apparatus for use in digital distribution system | |
| 8819072, | Feb 02 2004 | Microsoft Technology Licensing, LLC | Promoting data from structured data files |
| 8892993, | Aug 01 2003 | Microsoft Technology Licensing, LLC | Translation file |
| 8918729, | Mar 24 2003 | Microsoft Technology Licensing, LLC | Designing electronic forms |
| 9210234, | Dec 05 2005 | Microsoft Technology Licensing, LLC | Enabling electronic documents for limited-capability computing devices |
| 9229917, | Mar 28 2003 | Microsoft Technology Licensing, LLC | Electronic form user interfaces |
| 9235649, | Dec 22 2000 | Oracle International Corporation | Domain based workflows |
| 9239821, | Aug 01 2003 | Microsoft Technology Licensing, LLC | Translation file |
| 9268760, | Aug 06 2003 | Microsoft Technology Licensing, LLC | Correlation, association, or correspondence of electronic forms |
| Patent | Priority | Assignee | Title |
| 5276679, | Feb 12 1992 | Qwest Communications International Inc | Method for maintaining channels and a subscriber station for use in an ISDN system |
| 5526522, | Mar 08 1991 | NEC Corporation | Automatic program generating system using recursive conversion of a program specification into syntactic tree format and using design knowledge base |
| 5677835, | Sep 04 1992 | Caterpillar Inc. | Integrated authoring and translation system |
| 5678052, | Jan 19 1995 | International Business Machines Corporation | Methods and system for converting a text-based grammar to a compressed syntax diagram |
| 5848386, | May 28 1996 | Ricoh Corporation | Method and system for translating documents using different translation resources for different portions of the documents |
| 5995920, | Dec 22 1994 | Caterpillar Inc. | Computer-based method and system for monolingual document development |
| 6243862, | Jan 23 1998 | Unisys Corporation | Methods and apparatus for testing components of a distributed transaction processing system |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Nov 05 1998 | SUNDARESAN, NEELAKANTAN | International Business Machines Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 009583 | /0636 | |
| Nov 10 1998 | International Business Machines Corporation | (assignment on the face of the patent) | / |
| Date | Maintenance Fee Events |
| May 01 2002 | ASPN: Payor Number Assigned. |
| Jun 29 2005 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
| Jul 13 2009 | REM: Maintenance Fee Reminder Mailed. |
| Jan 01 2010 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
| Date | Maintenance Schedule |
| Jan 01 2005 | 4 years fee payment window open |
| Jul 01 2005 | 6 months grace period start (w surcharge) |
| Jan 01 2006 | patent expiry (for year 4) |
| Jan 01 2008 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Jan 01 2009 | 8 years fee payment window open |
| Jul 01 2009 | 6 months grace period start (w surcharge) |
| Jan 01 2010 | patent expiry (for year 8) |
| Jan 01 2012 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Jan 01 2013 | 12 years fee payment window open |
| Jul 01 2013 | 6 months grace period start (w surcharge) |
| Jan 01 2014 | patent expiry (for year 12) |
| Jan 01 2016 | 2 years to revive unintentionally abandoned end. (for year 12) |