United States Utility patent application by applicant matter number 60001.0263US01/MS303917.1, entitled “Programmable Object Model for Extensible Markup Language Schema Validation,” and United States Utility patent application by applicant matter number 60001.0270US01/MS303919.1, entitled “Programmable Object Model for Namespace or Schema Library Support in a Software Application,” are hereby incorporated by reference.
A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the United States Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
The present invention relates to programmable object models. More particularly, the present invention relates to a programmable object model for Extensible Markup Language markup in a software application.
Computer software applications allow users to create a variety of documents to assist them in work, education, and leisure. For example, popular word processing applications allow users to create letters, articles, books, memoranda, and the like. Spreadsheet applications allow users to store, manipulate, print, and display a variety of alphanumeric data. Such applications have a number of well known strengths including rich editing, formatting, printing, calculation and on-line and off-line editing.
Most computer software applications do not contain all necessary programming for providing functionality required or desired by every potential user. Many programmers often wish to take advantage of an existing application's capabilities in their own programs or to customize the functionality of an application and make it more suitable for a specific set of users or actions. For example, a programmer working in the financial industry may wish to customize a word processor for a user audience consisting of financial analysts editing financial reports. In recent years, the Extensible Markup Language has been used widely as an interchangeable data format for many users. A word processor or other application capable of receiving and editing XML data provides great value to its users. However, because the native .XML functionality of such an application is not exposed to users/programmers wishing to customize the functionality to further take advantage of the functionality for their own programs, such users/programmers are limited in their ability to utilize the XML functionality.
Accordingly, there is a need in the art for a programmable object model for allowing users/programmers to programmatically access the XML functionality of a software application in order to customize or otherwise modify the XML functionality to enhance their utilization of the functionality. It is with respect to these and other considerations that the present invention has been made.
The present invention provides methods and systems for allowing a user to programmatically access the Extensible Markup Language (XML) functionality of a software application by providing a programmable object model. According to one aspect of the present invention, a programmable object model comprised of a plurality of object-oriented message calls or application programming interfaces is provided for allowing a user to access the XML functionality of an application by sending one or more object-oriented message calls or application programming interfaces to the XML functionality of a given application along with any required parameters for customizing or otherwise manipulating XML markup applied to a document. Once the user has access to the XML functionality of a given application, the user may insert or delete XML markup in arbitrary locations in the document, the user may access richly formatted contents in areas contained inside an XML element or node, the user may locate specific XML nodes or elements in a document using queries, and the user may control or otherwise manipulate the application's XML-related settings and properties.
These and other features, advantages, and aspects of the present invention may be more clearly understood and appreciated from a review of the following detailed description of the disclosed embodiments and by reference to the appended drawings and claims.
Embodiments of the present invention are directed to methods and systems for allowing a user to programmatically call the Extensible Markup Language (XML) functionality of a software application for customizing, utilizing, and otherwise manipulating objects and properties of the XML functionality and for customizing, manipulating and enhancing the utilization of XML markup in a document. These embodiments may be combined, other embodiments may be utilized, and structural changes may be made without departing from the spirit or scope of the present invention. The following detailed description is therefore not to be taken in a limiting senses and the scope of the present invention is defined by the appended claims and their equivalents.
Referring now to the drawings, in which like numerals represent like elements through the several figures, aspects of the present invention and the exemplary operating environment will be described.
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Turning now to
The mass storage device 14 is connected to the CPU 4 through a mass storage controller (not shown) connected to the bus 12. The mass storage device 14 and its associated computer-readable media, provide non-volatile storage for the personal computer 2. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, it should be appreciated by those skilled in the art that computer-readable media can be any available media that can be accessed by the personal computer 2.
By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, DVD, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer.
According to various embodiments of the invention, the personal computer 2 may operate in a networked environment using logical connections to remote computers through a TCP/IP network 18, such as the Internet. The personal computer 2 may connect to the TCP/IP network 18 through a network interface unit 20 connected to the bus 12. It should be appreciated that the network interface unit 20 may also be utilized to connect to other types of networks and remote computer systems. The personal computer 2 may also include an input/output controller 22 for receiving and processing input from a number of devices, including a keyboard or mouse (not shown). Similarly, an input/output controller 22 may provide output to a display screen, a printer, or other type of output device.
As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 14 and RAM 8 of the personal computer 2, including an operating system 16 suitable for controlling the operation of a networked personal computer, such as the WINDOWS XP operating system from MICROSOFT CORPORATION of Redmond, Wash. The mass storage device 14 and RAM 8 may also store one or more application programs. In particular, the mass storage device 14 and RAM 8 may store an application program 305 for creating and editing an electronic document 310. For instance, the application program 305 may comprise a word processing application program, a spreadsheet application, a contact application, and the like. Application programs for creating and editing other types of electronic documents may also be used with the various embodiments of the present invention. A schema file 330 and a namespace/schema library 400, described below, are also shown.
Exemplary embodiments of the present invention are implemented by communications between different software objects in an object-oriented programming environment. For purposes of the following description of embodiments of the present invention, it is useful to briefly to describe components of an object-oriented programming environment.
A first object 210 may communicate with a second object 220 to obtain information or functionality from the second object 220 by calling the second object 220 via a message call 230. As is well know to those skilled in the art of object-oriented programming environment, the first object 210 may communicate with the second object 220 via application programming interfaces (API) that allow two disparate software objects 210, 220 to communicate with each other in order to obtain information and functionality from each other. For example, if the first object 210 requires the functionality provided by a method contained in the second object 220, the first object 210 may pass a message call 230 to the second object 220 in which the first object identifies the required method and in which the first object passes any required parameters to the second object required by the second object for operating the identified method. Once the second object 220 receives the call from the first object, the second object executes the called method based on the provided parameters and sends a return message 250 containing a value obtained from the executed method back to the first object 210.
For example, in terms of embodiments of the present invention, and as will be described below, a first object 210 may be a third party customized application that passes a message to a second object such as an Extensible Markup Language schema validation object whereby the first object identifies a method requiring the validation of a specified XML element in a document where the specified XML element is a parameter passed by the first object with the identified method. Upon receipt of the call from the first object, according to this example, the schema validation object executes the identified method on the specified XML element and returns a message to the first object in the form of a result or value associated with the validated XML element. Operation of object-oriented programming environments, as briefly described above, are well known to those skilled in the art.
As described below, embodiments of the present invention are implemented through the interaction of software objects in the use, customization, and application of components of the Extensible Markup Language (XML).
According to embodiments of the present invention, the text and XML markup entered into the document 310 may be saved according to a variety of different file formats and according to the native programming language of the application 305 with which the document 310 is created. For example, the text and XML markup may be saved according to a word processing application, a spreadsheet application, and the like. Alternatively, the text and XML markup entered into the document 310 may be saved as an XML format whereby the text or data, any applied XML markup, and any formatting such as font, style, paragraph structure, etc. may be saved as an XML representation. Accordingly, downstream or third party applications capable of understanding data saved as XML may open and consume the text or data thus saved as an XML representation. For a detailed discussion of saving text and XML markup and associated formatting and other attributes of a document 310 as XML, see U.S. patent application entitled “Word Processing Document Stored in a Single XML File that may be Manipulated by Applications that Understanding XML,” U.S. Ser. No. 10/187,060, filed Jun. 28, 2002, which is incorporated herein by reference as if fully set out herein.
In order to provide a definitional framework for XML markup elements (tags) applied to text or data, as illustrated in
According to the schema file 330, the <intro card> element serves as a root element for the schema file and also as a parent element to two child elements <title> and <body>. As is well known to those skilled in the art, a number of parent elements may be defined under a single root element, and a number of child elements may be defined under each parent element. Typically, however, a given schema file 330 contains only one root element. Referring still to
By applying such definitions or rules as attributes to XML elements, the creator of the schema may dictate the structure of data contained in a document associated with a given schema file. For example, if the creator of a schema file 330 for defining XML markup applied to a resume document desires that the experience section of the resume document contain no more than four present or previous job entries, the creator of the schema file 330 may define an attribute of an <experience> element, for example, to allow that no more than four present or past job entries may be entered between the <experience> tags in order for the experience text to be valid according to the schema file 330. As is well known to those skilled in the art, the schema file 330 may be attached to or otherwise associated with a given document 310 for application of allowable XML markup defined in the attached schema file to the document 310. According to one embodiment, the document 310 marked up with XML elements of the attached or associated schema file 330 may point to the attached or associated schema file by pointing to a uniform resource identifier (URI) associated with a Namespace identifying the attached or associated schema file 330.
According to embodiments of the present invention, a document 310 may have a plurality of attached schema files. That is, a creator of the document 310 may associate or attach more than one schema file 330 to the document 310 in order to provide a framework for the annotation of XML markup from more than one schema file. For example, a document 310 may contain text or data associated with financial data. A creator of the document 310 may wish to associate XML schema files 330 containing XML markup and definitions associated with multiple financial institutions. Accordingly, the creator of the document 310 may associate an XML schema file 330 from one or more financial institutions with the document 310. Likewise, a given XML schema file 330 may be associated with a particular document structure such as a template for placing financial data into a desirable format.
According to embodiments of the present invention, a collection of XML schema files and associated document solutions may be maintained in a Namespace or schema library located separately from the document 310. The document 310 may in turn contain pointers to URIs in the Namespace or schema library associated with the one or more schema files attached to otherwise associated with the document 310. As the document 310 requires information from one or more associated schema files, the document 310 points to the Namespace or schema library to obtain the required schema definitions. For a detailed description of the use of an operation of Namespace or schema libraries, see U.S. patent application entitled “System and Method for Providing Namespace Related Information,” U.S. Ser. No. 10/184,190, filed Jun. 27, 2002, and U.S. patent application entitled “System and Method for Obtaining and Using Namespace Related Information for Opening XML Documents,” U.S. Ser. No. 10/185,940, filed Jun. 27, 2002, both U.S. patent applications of which are incorporated herein by reference as if fully set out herein. For a detailed description of a mechanism for downloading software components such as XML schema files and associated solutions from a Namespace or schema library, see US patent application entitled Mechanism for Downloading Software Components from a Remote Source for Use by a Local Software Application, U.S. Ser. No. 10/164,260, filed Jun. 5, 2002.
Referring still to
According to embodiments of the present invention, the schema validation module 350 compares each XML markup element and associated text or data applied to the document 310 against the attached or associated schema file 330 to determine whether each element and associated text or data complies with the rules and definitions set out by the attached schema file 330. For example, if a user attempts to enter a character string exceeding twenty-five characters annotated by the <title> elements 320, the schema validation module will compare that text string against the text string attribute 340 of the attached schema file 330 and determine that the text string entered by the user exceeds the maximum allowable text string length. Accordingly, an error message or dialogue will be presented to the user to alert the user that the text string being-entered by the user exceeds the maximum allowable character length according to the attached schema file 330. Likewise, if the user attempts to add an XML markup element between the <title> and the <body> elements, the schema validation module 350 will determine that the XML markup element applied by the user is not a valid element allowed between the <title> and <body> elements according to the attached schema file 330. Accordingly, the schema validation module 350 will generate an error message or dialogue to the user to alert the user of the invalid XML markup.
Programmable Object Model for XML Markup in an Application
As described above with reference to
According to embodiments of the present invention, a user may access the XML functionality of an application by sending one or more object-oriented message calls or application programming interfaces to the XML functionality of the application 305 as described above with reference to
According to embodiments of the present invention, and as described above, the user may programmatically access the XML functionality of the software application to customize or otherwise manipulate the application of XML elements from the associated or attached schema file 330 to the document 310. For example, the user may desire to programmatically insert additional XML markup into the document at a specified range by sending an object-oriented message call specifying a method for inserting a given XML markup element into a particular range within the document. For another example, the user may desire to apply an Extensible Stylesheet Language Transformation (XSLT) to the document 310 in order to transform the document 310 to a format required by the user, for example HTML format. In order to effect such a transformation, the user is provided an object-oriented message call for calling the XML functionality of the application 305 and for providing the location of a desired XSLT transformation file for applying to the document 310.
The following is a description of objects and associated properties comprising object-oriented message calls (application programming interfaces) provided to a user for allowing the user to directly access the XML functionality of the software application 305, as described above. Following each of the objects or associated properties set out below is a description of the operation and functionality of the object or associated property.
Application Object
The following are properties and methods of this object related to XML markup.
.PrintXMLTag Property
The following are properties and methods of this object related to XML markup.
.TranformDocument
.XMLAfterInsert Event
.XMLBeforeDelete Event
.XMLHideNamespaces Property
XMLNodes Property
.XMLSaveDataOnly Property
.XMLSaveThroughXSLT Property
.XMLUseXSLTWhenSaving Property
The following are properties and methods of this object related to XML markup.
.ShowXMLMarkup Property
.ShowPlaceholderText Property
.InsertXML( ) Method
.XML Property
.XMLNodes Property
.XMLParentNode Property
.InsertXML( ) Method
.XML Property
.XMLNodes Property
.XMLParentNode Property
.Add( ) Method
.Application Property
.Count Property
.Creator Property
.Item( ) Method
.Parent Property
.Application Property
.Attributes Property
.BaseName Property
.ChildNodes Property
.Copy( ) Method
.Creator Property
.Cut( ) Method
.Delete( ) Method
.FirstChild Property
.HasChildNodes Property
.LastChild Property
.Level Property
.NamespaceURI Property
.NextSibling Property
.NodeType Property
.NodeValue Property
OwnerDocument Property
.Parent Property
.Parentnode Property
.PlaceholderText Property
A property controlling the placeholder text that shows up in place of elements when those elements are empty and their tags are not visible.
.PreviousSibling Property
.Range Property
.RemoveChild( ) Method
.SelectNodes( ) Method
.SelectSingleNode( ) Method
.SmartTag Property
.Text Property
.XML Property
As described herein, methods and systems are provided for allowing a user to programmatically access the Extensible Markup Language (XML) functionality of an application for accessing and customizing XML markup applied to a document created by the application and for controlling XML markup definitions and rules applied to the document by one or more associated or attached XML schema files. It will be apparent to those skilled in the art that various modifications or variations may be made in the present invention without departing from the scope or spirit of the invention. Other embodiments of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein.
Number | Name | Date | Kind |
---|---|---|---|
4674065 | Lange et al. | Jun 1987 | A |
4868750 | Kucera et al. | Sep 1989 | A |
5020019 | Ogawa | May 1991 | A |
5128865 | Sadler | Jul 1992 | A |
5159552 | van Gasteren et al. | Oct 1992 | A |
5267155 | Buchanan et al. | Nov 1993 | A |
5317546 | Balch et al. | May 1994 | A |
5337233 | Hofert et al. | Aug 1994 | A |
5341293 | Vertelney et al. | Aug 1994 | A |
5351190 | Kondo | Sep 1994 | A |
5392386 | Chalas | Feb 1995 | A |
5446891 | Kaplan et al. | Aug 1995 | A |
5541836 | Church et al. | Jul 1996 | A |
5596700 | Darnell et al. | Jan 1997 | A |
5617565 | Augenbraun et al. | Apr 1997 | A |
5625783 | Ezekiel et al. | Apr 1997 | A |
5627958 | Potts et al. | May 1997 | A |
5634019 | Koppolu et al. | May 1997 | A |
5640560 | Smith | Jun 1997 | A |
5657259 | Davis et al. | Aug 1997 | A |
5708825 | Sotomayor | Jan 1998 | A |
5717923 | Dedrick | Feb 1998 | A |
5752022 | Chiu et al. | May 1998 | A |
5761689 | Rayson et al. | Jun 1998 | A |
5781189 | Holleran et al. | Jul 1998 | A |
5781904 | Oren et al. | Jul 1998 | A |
5794257 | Liu et al. | Aug 1998 | A |
5802253 | Gross et al. | Sep 1998 | A |
5802262 | Van De Vanter | Sep 1998 | A |
5802299 | Logan et al. | Sep 1998 | A |
5802530 | van Hoff | Sep 1998 | A |
5805911 | Miller | Sep 1998 | A |
5809318 | Rivette et al. | Sep 1998 | A |
5815830 | Anthony | Sep 1998 | A |
5818447 | Wolf et al. | Oct 1998 | A |
5821931 | Berquist et al. | Oct 1998 | A |
5822539 | van Hoff | Oct 1998 | A |
5826025 | Gramlich | Oct 1998 | A |
5845077 | Fawcett | Dec 1998 | A |
5855007 | Jovicic et al. | Dec 1998 | A |
5859636 | Pandit | Jan 1999 | A |
5872973 | Mitchell et al. | Feb 1999 | A |
5875443 | Nielsen | Feb 1999 | A |
5892919 | Nielsen | Apr 1999 | A |
5893073 | Kasso et al. | Apr 1999 | A |
5895461 | De La Huerga et al. | Apr 1999 | A |
5896321 | Miller et al. | Apr 1999 | A |
5900004 | Gipson | May 1999 | A |
5913214 | Madnick et al. | Jun 1999 | A |
5920859 | Li | Jul 1999 | A |
5924099 | Guzak et al. | Jul 1999 | A |
5933498 | Schneck et al. | Aug 1999 | A |
5946647 | Miller et al. | Aug 1999 | A |
5948061 | Merriman et al. | Sep 1999 | A |
5956681 | Yamakita | Sep 1999 | A |
5974413 | Beauregard et al. | Oct 1999 | A |
5995756 | Hermann | Nov 1999 | A |
6006265 | Rangan et al. | Dec 1999 | A |
6006279 | Hayes | Dec 1999 | A |
6014616 | Kim | Jan 2000 | A |
6028605 | Conrad et al. | Feb 2000 | A |
6052531 | Waldin et al. | Apr 2000 | A |
6061516 | Yoshikawa et al. | May 2000 | A |
6067087 | Krauss et al. | May 2000 | A |
6085201 | Tso | Jul 2000 | A |
6092074 | Rodkin et al. | Jul 2000 | A |
6108674 | Murakami et al. | Aug 2000 | A |
6112209 | Gusack | Aug 2000 | A |
6121968 | Arcuri et al. | Sep 2000 | A |
6122647 | Horowitz et al. | Sep 2000 | A |
6126306 | Ando | Oct 2000 | A |
6137911 | Zhilyaev | Oct 2000 | A |
6141005 | Hetherington et al. | Oct 2000 | A |
6151643 | Cheng et al. | Nov 2000 | A |
6154738 | Call | Nov 2000 | A |
6167568 | Gandel et al. | Dec 2000 | A |
6173316 | De Boor et al. | Jan 2001 | B1 |
6182029 | Friedman | Jan 2001 | B1 |
6185550 | Snow et al. | Feb 2001 | B1 |
6185576 | McIntosh | Feb 2001 | B1 |
6199046 | Heinzle et al. | Mar 2001 | B1 |
6199081 | Meyerzon et al. | Mar 2001 | B1 |
6219698 | Iannucci et al. | Apr 2001 | B1 |
6262728 | Alexander | Jul 2001 | B1 |
6272074 | Winner | Aug 2001 | B1 |
6272505 | De La Huerga | Aug 2001 | B1 |
6292768 | Chan | Sep 2001 | B1 |
6295061 | Park et al. | Sep 2001 | B1 |
6308171 | De La Huerga | Oct 2001 | B1 |
6311177 | Dauerer et al. | Oct 2001 | B1 |
6311194 | Sheth et al. | Oct 2001 | B1 |
6323853 | Hedloy | Nov 2001 | B1 |
6336125 | Noda et al. | Jan 2002 | B2 |
6336131 | Wolfe | Jan 2002 | B1 |
6338059 | Fields et al. | Jan 2002 | B1 |
6347398 | Parthasarathy et al. | Feb 2002 | B1 |
6349295 | Tedesco et al. | Feb 2002 | B1 |
6353926 | Parthesarathy et al. | Mar 2002 | B1 |
6424979 | Livingston et al. | Jul 2002 | B1 |
6434567 | De La Huerga | Aug 2002 | B1 |
6438545 | Beauregard et al. | Aug 2002 | B1 |
6477510 | Johnson | Nov 2002 | B1 |
6480860 | Monday | Nov 2002 | B1 |
6493006 | Gourdol et al. | Dec 2002 | B1 |
6516321 | De La Huerga | Feb 2003 | B1 |
6519603 | Bays et al. | Feb 2003 | B1 |
6546433 | Matheson | Apr 2003 | B1 |
6556984 | Zien | Apr 2003 | B1 |
6571241 | Nosohara | May 2003 | B1 |
6618733 | White et al. | Sep 2003 | B1 |
6623527 | Hamzy | Sep 2003 | B1 |
6625581 | Perkowski | Sep 2003 | B1 |
6629079 | Spiegel et al. | Sep 2003 | B1 |
6631519 | Nicholson et al. | Oct 2003 | B1 |
6636880 | Bera | Oct 2003 | B1 |
6643633 | Chau et al. | Nov 2003 | B2 |
6658623 | Schilit et al. | Dec 2003 | B1 |
6687485 | Hopkins et al. | Feb 2004 | B2 |
6697824 | Bowman-Amuah | Feb 2004 | B1 |
6708189 | Fitzsimons et al. | Mar 2004 | B1 |
6715144 | Daynes et al. | Mar 2004 | B2 |
6717593 | Jennings | Apr 2004 | B1 |
6718516 | Claussen et al. | Apr 2004 | B1 |
6728679 | Strubbe et al. | Apr 2004 | B1 |
6732090 | Shanahan et al. | May 2004 | B2 |
6732361 | Andreoli et al. | May 2004 | B1 |
6745208 | Berg et al. | Jun 2004 | B2 |
6779154 | Nussbaum et al. | Aug 2004 | B1 |
6795808 | Strubbe et al. | Sep 2004 | B1 |
6826726 | Hsing et al. | Nov 2004 | B2 |
6868525 | Szabo | Mar 2005 | B1 |
6874143 | Murray et al. | Mar 2005 | B1 |
6880129 | Lee et al. | Apr 2005 | B1 |
6883137 | Girardot et al. | Apr 2005 | B1 |
6925457 | Britton et al. | Aug 2005 | B2 |
6925470 | Sangudi et al. | Aug 2005 | B1 |
6948133 | Haley | Sep 2005 | B2 |
20010029605 | Forbes et al. | Oct 2001 | A1 |
20010041328 | Fisher | Nov 2001 | A1 |
20010056461 | Kampe et al. | Dec 2001 | A1 |
20020004803 | Serebrennikov | Jan 2002 | A1 |
20020007309 | Reynar | Jan 2002 | A1 |
20020026450 | Kuramochi | Feb 2002 | A1 |
20020029304 | Reynar et al. | Mar 2002 | A1 |
20020035581 | Reynar et al. | Mar 2002 | A1 |
20020065110 | Enns et al. | May 2002 | A1 |
20020065891 | Malik | May 2002 | A1 |
20020066073 | Lienhard et al. | May 2002 | A1 |
20020078222 | Compas et al. | Jun 2002 | A1 |
20020091803 | Imamura et al. | Jul 2002 | A1 |
20020100036 | Moshir et al. | Jul 2002 | A1 |
20020103829 | Manning et al. | Aug 2002 | A1 |
20020104080 | Woodard et al. | Aug 2002 | A1 |
20020120685 | Srivastava et al. | Aug 2002 | A1 |
20020129107 | Loughran et al. | Sep 2002 | A1 |
20020133523 | Ambler et al. | Sep 2002 | A1 |
20020149601 | Rajarajan et al. | Oct 2002 | A1 |
20020156792 | Gombocz et al. | Oct 2002 | A1 |
20020178008 | Reynar | Nov 2002 | A1 |
20020178182 | Wang et al. | Nov 2002 | A1 |
20020184247 | Jokela et al. | Dec 2002 | A1 |
20020188941 | Cicciarelli et al. | Dec 2002 | A1 |
20020196281 | Audleman et al. | Dec 2002 | A1 |
20020198909 | Huynh et al. | Dec 2002 | A1 |
20030002391 | Biggs | Jan 2003 | A1 |
20030005411 | Gerken | Jan 2003 | A1 |
20030009489 | Griffin | Jan 2003 | A1 |
20030025728 | Ebbo et al. | Feb 2003 | A1 |
20030051236 | Pace et al. | Mar 2003 | A1 |
20030056207 | Fischer et al. | Mar 2003 | A1 |
20030081791 | Erickson et al. | May 2003 | A1 |
20030084138 | Tavis et al. | May 2003 | A1 |
20030097318 | Yu et al. | May 2003 | A1 |
20030101204 | Watson | May 2003 | A1 |
20030101416 | McInnes et al. | May 2003 | A1 |
20030106040 | Rubin et al. | Jun 2003 | A1 |
20030121033 | Peev et al. | Jun 2003 | A1 |
20030126136 | Omoigui | Jul 2003 | A1 |
20030140308 | Murthy et al. | Jul 2003 | A1 |
20030145197 | Lee et al. | Jul 2003 | A1 |
20030154144 | Pokomy et al. | Aug 2003 | A1 |
20030158841 | Britton et al. | Aug 2003 | A1 |
20030158851 | Britton et al. | Aug 2003 | A1 |
20030172343 | Leymaster et al. | Sep 2003 | A1 |
20030192040 | Vaughan | Oct 2003 | A1 |
20030212527 | Moore et al. | Nov 2003 | A1 |
20030220795 | Araysantiparb et al. | Nov 2003 | A1 |
20030229593 | Raley et al. | Dec 2003 | A1 |
20030233330 | Raley et al. | Dec 2003 | A1 |
20040003389 | Reynar et al. | Jan 2004 | A1 |
20040006741 | Radja et al. | Jan 2004 | A1 |
20040165007 | Shafron | Aug 2004 | A1 |
20040199861 | Lucovsky | Oct 2004 | A1 |
20040236717 | Demartini et al. | Nov 2004 | A1 |
20050050164 | Burd et al. | Mar 2005 | A1 |
20050055330 | Britton et al. | Mar 2005 | A1 |
20050120313 | Rudd et al. | Jun 2005 | A1 |
20050187926 | Britton et al. | Aug 2005 | A1 |
Number | Date | Country |
---|---|---|
0481784 | Apr 1992 | EP |
0598511 | May 1994 | EP |
0810520 | Dec 1998 | EP |
1093058 | Apr 2001 | EP |
1280068 | Jan 2003 | EP |
1361523 | Nov 2003 | EP |
1376392 | Jan 2004 | EP |
WO 9507510 | Mar 1995 | WO |
WO 9917240 | Apr 1999 | WO |
WO 0118687 | Mar 2001 | WO |
WO 0137170 | May 2001 | WO |
WO 0118639 | Nov 2001 | WO |
WO 0299627 | Jan 2002 | WO |
WO 0215518 | Feb 2002 | WO |