Disclosed is a system, method, and program for determining a structure of objects in a document, such as an XML document. The document is parsed to determine instances of objects within the document. Each instance of each object is parsed to determine whether a value is provided for the object. Information is returned on each instance of each object in the document and location information is returned of the value for each object in the document having a value. The returned information identifies the objects in the documents and the location of any values for identified objects in the document. When the location information is returned, a string comprising the value from the document is not returned.
|
1. A method for determining a structure of objects in a document, comprising:
while scanning a document type declaration in the document, generating a handle addressing each different object name in memory, wherein there are one or more instances of each different object name in the document, and wherein the handle for an object name is used for each instance of the object having that object name in the document; parsing the document to determine instances of objects within the document; parsing each instance of each object to determine whether a value is provided for the object; returning information on each instance of each object in the document by returning the handle addressing the object name of the object; and returning location information of the value for each object in the document having a value, wherein the returned information identifies the objects in the documents and the location of any values for identified objects in the document without returning a string comprising the value from the document.
10. A system for determining a structure of objects in a document, comprising:
means for, while scanning a document type declaration in the document, generating a handle addressing a each different object name in memory, wherein there are one or more instances of each different object name in the document, and wherein the handle for an object name is used for each instance of the object having that object name in the document; means for parsing the document to determine instances of objects within the document; means for parsing each instance of each object to determine whether a value is provided for the object; means for returning information on each instance of each object in the document by returning the handle addressing the object name of the object; and means for returning location information of the value for each object in the document having a value, wherein the returned information identifies the objects in the documents and the location of any values for identified objects in the document without returning a string comprising the value from the document.
19. An article of manufacture for use in determining a structure of objects in a document, the article of manufacture comprising computer usable media including at least one computer program embedded therein that causes the computer to perform:
while scanning a document type declaration in the document, generating a handle addressing a each different object name in memory, wherein there are one or more instances of each different object name in the document, and wherein the handle for an object name is used for each instance of the object having that object name in the document; parsing the document to determine instances of objects within the document; parsing each instance of each object to determine whether a value is provided for the object; returning information on each instance of each object in the document by returning the handle addressing the object name of the object; and returning location information of the value for each object in the document having a value, wherein the returned information identifies the objects in the documents and the location of any values for identified objects in the document without returning a string comprising the value from the document.
2. The method of
4. The method of
5. The method of
parsing the document type declaration identifying the objects within the document and the hierarchical relationship of the objects within the document; and returning information on the hierarchical relationship of the document.
6. The method of
generating a node for each object indicated in the returned information, wherein the generated nodes are defined according to the hierarchical relationship included in the returned information; and associating with each node generated for an object having a value the returned location information of the location of the value in the document.
7. The method of
determining one object to access having a value from returned information from the parser; determining the location information of the value for the determined object; and requesting the parser to obtain a string of data comprising the value at the location defined in the determined location information, wherein the parser converts the requested string of data from a first encoding to a second encoding and returns the data in the second encoding to the application program.
8. The method of
requesting, with the parser, whether a character indicates the start of an instance of one object in the document; returning a boolean response, with the reader, indicating whether the character indicates the start of an object instance in the document; requesting, with the parser, information on the instance of the object if the returned boolean response indicates that the character indicates the start of an object instance, wherein the reader returns a name of the object instance and any attributes thereof, and location information of values for any attributes of the object instance in the document.
9. The method of
11. The system of
13. The system of
14. The system of
means for parsing the document type declaration identifying the objects within the document and the hierarchical relationship of the objects within the document; and means for returning information on the hierarchical relationship of the document.
15. The system of
means for generating a node for each object indicated in the returned information, wherein the generated nodes are defined according to the hierarchical relationship included in the returned information; and means for associating with each node generated for an object having a value the returned location information of the location of the value in the document.
16. The system of
means for determining one object to access having a value from returned information from the parser; means for determining the location information of the value for the determined object; and means for requesting the parser to obtain a string of data comprising the value at the location defined in the determined location information, wherein the parser converts the requested string of data from a first encoding to a second encoding and returns the data in the second encoding to the application program.
17. The system of
means, performed by the parser, for requesting whether a character indicates the start of an instance of one object in the document; means, performed by the reader, for returning a boolean response indicating whether the character indicates the start of an object instance in the document; means for requesting, with the parser, information on the instance of the object if the returned boolean response indicates that the character indicates the start of an object instance, wherein the reader returns a name of the object instance and any attributes thereof, and location information of values for any attributes of the object instance in the document.
18. The system 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
parsing the document type declaration identifying the objects within the document and the hierarchical relationship of the objects within the document; and returning information on the hierarchical relationship of the document.
24. The article of manufacture of
generating a node for each object indicated in the returned information, wherein the generated nodes are defined according to the hierarchical relationship included in the returned information; and associating with each node generated for an object having a value the returned location information of the location of the value in the document.
25. The article of manufacture of
determining one object to access having a value from returned information from the parser; determining the location information of the value for the determined object; and requesting the parser to obtain a string of data comprising the value at the location defined in the determined location information, wherein the parser converts the requested string of data from a first encoding to a second encoding and returns the data in the second encoding to the application program.
26. The article of manufacture of
requesting, with the parser, whether a character indicates the start of an instance of one object in the document; returning a boolean response, with the reader, indicating whether the character indicates the start of an object instance in the document; requesting, with the parser, information on the instance of the object if the returned boolean response indicates that the character indicates the start of am object instance, wherein the reader returns a name of the object instance and any attributes thereof, and location information of values for any attributes of the object instance in the document.
27. The article of manufacture of
|
1. Field of the Invention
The present invention relates to a method, system, and program for providing access to objects in a document, such as a well formed document.
2. Description of the Related Art
The Extensible Mark-up Language (XML), which is a subset of the Standard Generalized Markup Language (SGML), is designed to provide the capability to exchange structured documents over the Internet. XML files clearly mark where the start and end of each of the logical parts (called elements) of an interchanged document occur. For instance, if the XML document defines a book, the elements would include the table of contents, chapters, appendices, etc. The XML document includes a definition of each element in a formal model, known as a Document Type Definition (DTD). The DTD provides attributes for each element and indicates the relationship of the elements. Elements are arranged in a hierarchical relationship. The DTD would define the hierarchical relationship of the elements to one another and the attributes of the elements. Further details of XML are described in the publication "Extensible Markup Language (XML) 1.0, document no. REC-xml-19980210 (Copyright W3C, 1998), which publication is incorporated herein by reference in its entirety.
Users can encode and view an XML document with the Document Object Model (DOM) application program interface (API). The DOM interface is described in the publication entitled "Document Object Model (DOM) Level 1 Specification, Version 1.0," document no. REC-DOM-Level-1-19981001 (Copyright W3C 1998), which publication is incorporated herein by reference in its entirety. The DOM interface represents the document as a hierarchical arrangement of nodes. When applied to the XML document, each node comprises one of the elements or attributes of the elements. For instance, the user may define the DTD (1) below to include elements of a book.
The DOM interface would represent the above elements in the tree illustrated in FIG. 1. Rather than describing the order and fashion in which the data should be displayed, the tags indicate what each item of data means (whether it is a <title> element, an <author> element, and so forth.). Any receiver of this data can then decode the document, each using it for his own purposes. For example, a bookstore might use the information to fill an order, a market analyst might use many similar orders to discover which books are most popular, and an individual might file it as a record of his purchases.
XML Application Program Interfaces (APIs) used to parse the XML document generally fall into two categories: event-based and tree-based. An event-based API (such as SAX) uses callbacks to report parsing events to the application. The application deals with these events through customized event handlers. Events include the start and end of elements and characters. Unlike tree-based APIs, event-based APIs usually do not build in-memory tree representations of the XML documents. Therefore, in general, SAX is useful for applications that do not need to manipulate the XML tree, such as search operations, among others. To process an XML document, the programmer creates a class that implements interface org.xml.sax.DocumentHandler. The Parser object (that is, the object that implements org.xml.sax.Parser) reads the XML from its input source, calling the methods of the DocumentHandler when tags, input strings, and so on are recognized at the input. The SAX interface parses the XML file and executes particular actions whenever certain structures (like tags) appear in the input. The DOM API represents the XML document as a tree of nodes. A JAVA** (or other language) program returns a representation of the, file as a tree of objects.
The XML parser processes the XML document character-by-character, searching for particular tags that define the objects within the document. The XML parser or scanner will send a request to an XML reader requesting the current character being processed in the text. The XML reader, which is capable of processing the XML file using the file encoding, converts the character from the file encoding, which may be ASCII or some other language specific encoding, to Unicode. This conversion process may require the XML reader to convert the character from a one byte encoding to the Unicode two byte encoding. This character conversion operation requires processor resources to allocate additional memory for the Unicode encoding and perform the conversion. The XML parser then processes the returned Unicode characters to determine the object in the document being analyzed. From the returned information, a DOM XML parser builds the DOM tree by scanning and converting each character in the XML document from the file encoding to Unicode. During this process, the XML parser would return to the application all the characters of the document converted into Unicode, which the application may then maintain as objects.
There is a need in the art for an improved technique for scanning an XML file to provide the application program access to the structure of the document.
To overcome the limitations in the prior art described above, preferred embodiments disclose a method, system, and program for determining a structure of objects in a document. The document is parsed to determine instances of objects within the document. Each instance of each object is parsed to determine whether a value is provided for the object. Information is returned on each instance of each object in the document and location information is returned on a location of the value for each object in the document having a value. The returned information identifies the objects in the documents and the location of any values for identified objects in the document. When the location information is returned, a string comprising the value from the document is not returned.
In further embodiments, the objects include element objects having a name. When an element object has associated attribute objects, each attribute object comprises a name and value. The location information of the values indicates the location in the document of the attribute values.
In still further embodiments, for each object in the document, a handle addressing a name of each element and attribute object in the document is generated. In such case, the handle addressing the name of the object is returned when returning information for each object.
In yet further embodiments, the steps of parsing and returning information are performed by a parser. An application program determines one object to access having a value from the information returned from the parser and the location information of the value for the determined object. The application program then requests the parser to obtain a string of data comprising the value at the determined location information. The parser converts the requested string of data from a first encoding to a second encoding and returns the data in the second encoding to the application program.
Preferred embodiments provide a method, system, and program for providing an application program information on the structure of a document, such as an XML document. This structural information includes information on instances of objects in the document and location information on any values for the objects in the document. In this way, the application program is provided a definition of the document structure without having the parser convert the characters in the document from a document encoding to Unicode.
When providing information on the structure of the document, prior art parsers typically convert all the characters to Unicode, which requires substantial processor cycles to allocate the additional memory for the Unicode characters and to perform the conversion operations. These Unicode conversion operations can substantially degrade performance when processing especially large XML documents. Preferred embodiments provide a technique for providing an application program all the information needed to define the structure of objects in the document and access such objects without having to convert characters to Unicode. If the application program wants specific content within the document, then the application program can request the parser to return specific strings of content identified in the returned location information. At this point, when specific content is requested, the parser would convert the characters to the Unicode encoding.
Thus, preferred embodiments provide a method, system, and program for providing access to objects within a document without converting the content of the objects to a new encoding, such as Unicode.
Referring now to the drawings in which like reference numbers represent corresponding parts throughout:
In the following description, reference is made to the accompanying drawings which form a part hereof and which illustrate several embodiments of the present invention. It is understood that other embodiments may be utilized and structural and operational changes may be made without departing from the scope of the present invention.
If the character is a start tag (at block 104), then the XML parser 8 scans (at block 114) the name of the tagged object and accesses (at block 116) the handle for the name of the tagged object. All information about the document is returned to the application program 6. The XML parser 8 then calls the XML Reader 12 to skip (at block 118) to the character following the name of the tagged object, which would require skipping a white space following the named of a tagged object. If this next current character is an end tag for the object (at block 120), then control proceeds back to block 110 to consider the next character in the XML document 4. Otherwise, the next string of characters followed by a whitespace must be an attribute of the tagged object. In such case, the XML parser 8 determines (at block 122) the name of the attribute beginning at the current character by scanning the characters from the current character to the whitespace. The XML parser 8 then accesses (at block 124) the handle pointing to the attribute name in the storage pool to return to the application program 6. The XML parser 8 further issues calls to the XML reader 12 to determine (at block 126) the start and end locations of the value in the text for the determined attribute, which would typically follow an equal sign "=" following the attribute name. This location information is returned to the application program 6. The XML parser 8 then instructs the XML reader 12 to skip (at block 128) to the character following the attribute value. Control proceeds back to block 120 to consider this next character.
Using the logic of
Once this information on the structure is obtained for all nodes or any particular node, then the application program 6 can obtain information and content on any part of the document because the structure and the location in the XML document 4 of values for attributes are known. To obtain the value of a particular part of the XML document, the application program 6 would issue a request to the XML parser 6, which would then call the XML reader 12 to read the value from the document at the location indicated in the location information and convert the value to a Unicode string to return to the application program 6.
A DOM parser may utilize the logic of
The preferred method for parsing the XML document to determine the structure of the objects requires substantially less processor and memory resources than current parsing methods. As discussed, in the prior art, the XML parser converts every character to Unicode and allocates space in memory for the converted Unicode data. The prior art XML processor would create objects in memory for the entire converted document when providing the application program 6 information on the structure of the XML document. If the XML document is in a one byte encoding, such as ASCII, then the conversion to Unicode, which requires 2 bytes, would double the memory allocation to the file and require full conversion of the document even though the application program 6 may initially only need the base structure without the content or values of all the elements and attributes.
Preferred embodiments avoid having to allocate memory for converting the characters in the XML document 4 to Unicode because the XML parser 8 of the preferred embodiments returns handles for attribute and element names that point to strings in the storage pool and location offsets of attribute values within the document. Moreover, handles may be used to provide a pointer to a commonly used attribute values or list of values. In this way, the XML parser 8 would return the handle to the value instead of the actual value itself. The use of integer handles further reduces the information the application program 6 needs to maintain to represent the structure of the document. Instead of maintaining numerous instances of the same name, type and/or value, only a single integer handle is maintained, which typically uses less bits than used by the actual characters for the name, type or value.
The preferred embodiments provide a fast processing technique that minimizes use of processor and memory resources to provide the application program 6 the structure of the XML document 4 including location information to allow the application program 6 to access the actual data for any of the objects of the XML document, e.g., elements and attributes. With the preferred embodiments, only a minimal amount of information is needed to define the document structure to the application program 6. If the application program 6 wants any further document data, then it would use the element information and offsets to locate a specific section of the XML document including
It has been noticed that products implementing the preferred embodiment logic, such as the IBM XML4J EA2 parser, can process large documents to determine the structure substantially faster then current XML parser techniques. For instance, it has been noticed that the current XML4J EA2 can process an approximately 10MB XML document twice as fast as current XML parsers. Preferred embodiments improve processing speed by avoiding having to allocate objects in memory for the conversion of the entire XML document to Unicode.
This concludes the description of the preferred embodiments of the invention. The following describes some alternative embodiments for accomplishing the present invention.
The preferred embodiments may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. The term "article of manufacture" (or alternatively, "computer program product") as used herein is intended to encompass one or more computer programs and/or data files accessible from one or more computer-readable devices, carriers, or media, such as magnetic storage media, "floppy disk," CD-ROM, optical disks, holographic units, volatile or non-volatile electronic memory, a file server providing access to the programs via a network transmission line, wireless transmission media, signals propagating through space, etc. Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope of the present invention.
The program flow logic described in the flowcharts above indicated certain events occurring in a certain order. Those skilled in the art will recognize that the ordering of certain programming steps or program flow may be modified without affecting the overall operation performed by the preferred embodiment logic, and such modifications are in accordance with the preferred embodiments.
Preferred embodiments described generating a method to access elements within a document arranged in a hierarchical fashion. However, in alternative embodiments, the elements do not have to be in a hierarchical relationship to one another and may be accessible through interfaces other than the DOM interface.
Preferred embodiments of the document and parser were described as implemented for XML documents. However, the logic for parsing and defining the structure of the XML documents may apply to compiling other document types known in the art, such as Dynamic Hypertext Mark-Up Language (DHTML), Cascading Style Sheets, any other Standard Generalized Markup Language (SGML), or any other language known in the art for creating interchangeable, structured documents. In yet further embodiments, the requested file may be in any other file format, i.e., other than an SGML type format, capable of being displayed or otherwise executed by the requesting client.
The program interface of the preferred embodiments that provides direct access to elements in the XML document is implemented in JAVA** methods. However, any other program calls or interfaces could be used to implement the controls that provide direct access to the elements in the document to allow the user to more readily and directly manipulate the elements in the document.
Preferred embodiments described particular methods that could be generated for each class of elements. However, the default methods generated may include any methods that could be used to manipulate or otherwise affect the elements in the XML document.
Preferred embodiments were described with respect to providing information on elements and attributes within an XML document. However, the preferred method for compiling and obtaining structural information on the document may apply to any objects within the document, not just elements and attributes.
Although the logic of the preferred embodiments is implemented in the IBM XML parser XML4J EA2, the preferred logic may be implemented in any XML parser to increase processing speed and reduce memory usage during the initial rendering of the document structure.
In summary, preferred embodiments disclose a method, system, and program for determining a structure of objects in a document. The document is parsed to determine instances of objects within the document. Each instance of each object is parsed to determine whether a value is provided for the object. Information is returned on each instance of each object in the document and location information is returned of the value for each object in the document having a value. The returned information identifies the objects in the documents and the location of any values for identified objects in the document. When the location information is returned, a string comprising the value from the document is not returned.
The foregoing description of the preferred embodiments 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. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
JAVA and all JAVA-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Patent | Priority | Assignee | Title |
11586715, | Jul 30 2021 | Coupang Corp. | Electronic apparatus for providing information based on existence of a user account and method thereof |
6886166, | Sep 20 2000 | International Business Machines Corporation | Message parsing in message processing systems |
6950866, | Dec 19 2000 | RPX Corporation | XML-based integrated services parsing |
7013425, | Jun 28 2001 | International Business Machines Corporation | Data processing method, and encoder, decoder and XML parser for encoding and decoding an XML document |
7092967, | Sep 28 2001 | Oracle International Corporation | Loadable units for lazy manifestation of XML documents |
7162530, | Dec 22 2000 | Microsoft Technology Licensing, LLC | System and method for encapsulating data within a formatted data protocol |
7188340, | Jun 28 2002 | Microsoft Technology Licensing, LLC | Hybrid tree for mixed user interface elements and sequential data |
7293230, | Jan 27 2000 | Liberty Peak Ventures, LLC | Information architecture for the interactive environment |
7305667, | Jun 15 2001 | Oracle International Corporation | Call back structures for user defined DOMs |
7321900, | Jun 15 2001 | Oracle International Corporation | Reducing memory requirements needed to represent XML entities |
7337401, | Dec 18 2002 | Microsoft Technology Licensing, LLC | User interface element representation with simplified view |
7346921, | Apr 30 2001 | GE Capital Corporation | Definition of low-level security rules in terms of high-level security concepts |
7409634, | Jul 26 2006 | International Business Machines Corporation | Method and apparatus for end-to-end content publishing system using XML with an object dependency graph |
7437662, | Jun 15 2001 | Oracle International Corporation | Representing deltas between XML versions using XSLT |
7440954, | Apr 09 2004 | Oracle International Corporation | Index maintenance for operations involving indexed XML data |
7478100, | Sep 05 2003 | Oracle International Corporation | Method and mechanism for efficient storage and query of XML documents based on paths |
7519546, | Apr 30 2001 | General Electric Company | Maintaining synchronization of information published to multiple subscribers |
7730032, | Jan 12 2006 | Oracle International Corporation | Efficient queriability of version histories in a repository |
7747580, | Aug 25 2003 | NOMIR MEDICAL TECHNOLOGIES, INC | Direct loading of opaque types |
7797310, | Oct 16 2006 | Oracle International Corporation | Technique to estimate the cost of streaming evaluation of XPaths |
7802180, | Jun 23 2004 | Oracle International Corporation | Techniques for serialization of instances of the XQuery data model |
7814047, | Aug 25 2003 | Oracle International Corporation | Direct loading of semistructured data |
7853936, | Feb 10 2005 | SAP Portals Israel Ltd. | Compilation of nested regular expressions |
7870143, | Feb 28 2003 | Oracle International Corporation | Systems and methods for processing XML document as a stream of events using XPath context |
7873645, | Sep 05 2003 | Oracle International Corporation | Method and mechanism for handling arbitrarily-sized XML in SQL operator tree |
7885980, | Jul 02 2004 | Oracle International Corporation | Mechanism for improving performance on XML over XML data using path subsetting |
7921101, | Apr 09 2004 | Oracle International Corporation | Index maintenance for operations involving indexed XML data |
7930277, | Apr 21 2004 | Oracle International Corporation | Cost-based optimizer for an XML data repository within a database |
7933928, | Dec 22 2005 | Oracle International Corporation | Method and mechanism for loading XML documents into memory |
7933935, | Oct 16 2006 | Oracle International Corporation | Efficient partitioning technique while managing large XML documents |
7954046, | Feb 28 2003 | Microsoft Technology Licensing, LLC | Importing and exporting markup language data in a spreadsheet application document |
7962925, | Feb 22 2002 | Oracle International Corporation | System and method for XML data binding |
7991768, | Nov 08 2007 | Oracle International Corporation | Global query normalization to improve XML index based rewrites for path subsetted index |
7992079, | Jan 27 2000 | Liberty Peak Ventures, LLC | Information architecture for the interactive environment |
8073841, | Oct 07 2005 | Oracle International Corporation | Optimizing correlated XML extracts |
8074160, | Sep 16 2005 | Oracle International Corporation | Streaming parser API for processing XML document |
8099438, | Feb 28 2003 | Oracle International Corporation | Systems and methods for processing XML document as a stream of events using a schema |
8209352, | Sep 05 2003 | Oracle International Corporation | Method and mechanism for efficient storage and query of XML documents based on paths |
8250062, | Nov 09 2007 | Oracle International Corporation | Optimized streaming evaluation of XML queries |
8266188, | Mar 08 2005 | CA, INC | Method and system for extracting structural information from a data file |
8429196, | Jun 06 2008 | Oracle International Corporation | Fast extraction of scalar values from binary encoded XML |
8429526, | Apr 10 2006 | Oracle International Corporation | Efficient evaluation for diff of XML documents |
8510292, | May 25 2006 | Oracle International Coporation | Isolation for applications working on shared XML data |
8543898, | Nov 09 2007 | Oracle International Corporation | Techniques for more efficient generation of XML events from XML data sources |
8683310, | Jan 27 2000 | Liberty Peak Ventures, LLC | Information architecture for the interactive environment |
8782230, | Jun 21 2000 | RPX CLEARINGHOUSE LLC | Method and apparatus for using a command design pattern to access and configure network elements |
8930348, | May 25 2006 | Oracle International Corporation | Isolation for applications working on shared XML data |
9229967, | Feb 22 2006 | Oracle International Corporation | Efficient processing of path related operations on data organized hierarchically in an RDBMS |
9842090, | Dec 05 2007 | Oracle International Corporation | Efficient streaming evaluation of XPaths on binary-encoded XML schema-based documents |
9946807, | Jun 04 2004 | VITALSOURCE TECHNOLOGIES INC | System, method and computer program product for providing content based upon a representation of the same |
Patent | Priority | Assignee | Title |
5682158, | Sep 13 1995 | Apple Inc | Code converter with truncation processing |
5724593, | Jun 07 1995 | LIONBRIDGE US, INC | Machine assisted translation tools |
5732270, | Sep 15 1994 | INFORMATION BUILDERS, INC | System and method for providing interoperability among heterogeneous object systems |
5758314, | May 21 1996 | SYBASE, Inc.; SYBASE, INC | Client/server database system with methods for improved soundex processing in a heterogeneous language environment |
5778213, | Jul 12 1996 | Microsoft Technology Licensing, LLC | Multilingual storage and retrieval |
5784069, | Sep 13 1995 | Apple Inc | Bidirectional code converter |
5784071, | Sep 13 1995 | Apple Inc | Context-based code convertor |
5787452, | May 21 1996 | SYBASE, Inc.; SYBASE, INC , A CORPORATION OF DELAWARE | Client/server database system with methods for multi-threaded data processing in a heterogeneous language environment |
5793381, | Sep 13 1995 | Apple Inc | Unicode converter |
5832507, | Apr 01 1996 | Oracle America, Inc | Method and apparatus for converting ASCII path names to parsed path name structures |
5873111, | May 10 1996 | Apple Inc | Method and system for collation in a processing system of a variety of distinct sets of information |
6204782, | Sep 25 1998 | Apple Inc | Unicode conversion into multiple encodings |
6226675, | Oct 16 1998 | Red Hat, Inc | Participant server which process documents for commerce in trading partner networks |
6408311, | Jun 30 1999 | Unisys Corp.; Unisys Corporation | Method for identifying UML objects in a repository with objects in XML content |
6502112, | Aug 27 1999 | Unisys Corporation | Method in a computing system for comparing XMI-based XML documents for identical contents |
20030005410, | |||
20030028561, | |||
WO9710556, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Dec 10 1999 | MARCY, GLENN A | International Business Machines Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 010450 | /0293 | |
Dec 13 1999 | International Business Machines Corporation | (assignment on the face of the patent) | / | |||
May 03 2011 | International Business Machines Corporation | Google Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 026664 | /0866 | |
Sep 29 2017 | Google Inc | GOOGLE LLC | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 044127 | /0735 |
Date | Maintenance Fee Events |
Apr 02 2004 | ASPN: Payor Number Assigned. |
Jan 10 2007 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Jun 09 2011 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Jun 09 2015 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Dec 09 2006 | 4 years fee payment window open |
Jun 09 2007 | 6 months grace period start (w surcharge) |
Dec 09 2007 | patent expiry (for year 4) |
Dec 09 2009 | 2 years to revive unintentionally abandoned end. (for year 4) |
Dec 09 2010 | 8 years fee payment window open |
Jun 09 2011 | 6 months grace period start (w surcharge) |
Dec 09 2011 | patent expiry (for year 8) |
Dec 09 2013 | 2 years to revive unintentionally abandoned end. (for year 8) |
Dec 09 2014 | 12 years fee payment window open |
Jun 09 2015 | 6 months grace period start (w surcharge) |
Dec 09 2015 | patent expiry (for year 12) |
Dec 09 2017 | 2 years to revive unintentionally abandoned end. (for year 12) |