Source: http://www.google.com/patents/US20060136433?dq=inventor:%22Arthur+R.+Hair%22&ei=VAy0Tsa4NYTl0QGQiqWiBA
Timestamp: 2014-03-17 10:11:46
Document Index: 656789843

Matched Legal Cases: ['art 217', 'art 202', 'art 217', 'art 202', 'art 217', 'art 205', 'art 207', 'art 210', 'art 212', 'art 240', 'art 220', 'art 214', 'art 218', 'art 222', 'art 224', 'art 225', 'art 242', 'art 244', 'art 247', 'art 254', 'art 218', 'art 248', 'art 230', 'art 245', 'art 257', 'art 252', 'art 232', 'art 228', 'art 228', 'art 228', 'art 234', 'art 235', 'art 237', 'art 212', 'art 214', 'art 217', 'art 234', 'art 235', 'art 237', 'art 240', 'art 220', 'art 218', 'art 228', 'art 230', 'art 245', 'art 202', 'arts 217', 'art 202', 'art 217', 'art 202', 'art 248', 'art 254']

Patent US20060136433 - File formats, methods, and computer program products for representing workbooks - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsFile formats, methods, and computer program products are provided for representing a workbook in a modular content framework. The modular content framework may include a file format container associated with modular parts. A file format includes logically separate modular parts that are associated with...http://www.google.com/patents/US20060136433?utm_source=gb-gplus-sharePatent US20060136433 - File formats, methods, and computer program products for representing workbooksAdvanced Patent SearchPublication numberUS20060136433 A1Publication typeApplicationApplication numberUS 11/018,912Publication dateJun 22, 2006Filing dateDec 20, 2004Priority dateDec 20, 2004Also published asCA2525735A1, CN1794224A, EP1672528A2, EP1672528A3, US7617444Publication number018912, 11018912, US 2006/0136433 A1, US 2006/136433 A1, US 20060136433 A1, US 20060136433A1, US 2006136433 A1, US 2006136433A1, US-A1-20060136433, US-A1-2006136433, US2006/0136433A1, US2006/136433A1, US20060136433 A1, US20060136433A1, US2006136433 A1, US2006136433A1InventorsChad Rothschiller, Su-Piao WuOriginal AssigneeMicrosoft CorporationExport CitationBiBTeX, EndNote, RefManReferenced by (5), Classifications (11), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetFile formats, methods, and computer program products for representing workbooksUS 20060136433 A1Abstract File formats, methods, and computer program products are provided for representing a workbook in a modular content framework. The modular content framework may include a file format container associated with modular parts. A file format includes logically separate modular parts that are associated with each other by one or more relationships where each modular part is associated with a relationship type. The modular parts include a workbook part operative as a guide for properties of the workbook and a worksheet part associated with the workbook part and operative to specify a definition of cells within a worksheet associated with the worksheet part. The modular parts may also include a document properties part containing built-in properties associated with the file format and a thumbnail part containing associated thumbnails. Each modular part is capable of being interrogated separately, extracted from the workbook, and/or reused in a different workbook. Images(7) Claims(20)
DETAILED DESCRIPTION Referring now to the drawings, in which like numerals represent like elements, various aspects of the present invention will be described. In particular, FIG. 1 and the corresponding discussion are intended to provide a brief, general description of a suitable computing environment in which embodiments of the invention may be implemented. While the invention will be described in the general context of program modules that execute in conjunction with program modules that run on an operating system on a personal computer, those skilled in the art will recognize that the invention may also be implemented in combination with other types of computer systems and program modules. Generally, program modules include routines, programs, operations, 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. Referring now to FIG. 1, an illustrative computer architecture for a computer 2 utilized in an embodiment of the invention will be described. The computer architecture shown in FIG. 1 illustrates a computing apparatus, such as a server, desktop, laptop, or handheld computing apparatus, including a central processing unit 5 (�CPU�), a system memory 7, including a random access memory 9 (�RAM�) and a read-only memory (�ROM�) 11, and a system bus 12 that couples the memory to the CPU 5. A basic input/output system containing the basic routines that help to transfer information between elements within the computer, such as during startup, is stored in the ROM 11. The computer 2 further includes a mass storage device 14 for storing an operating system 16, application programs, and other program modules, which will be described in greater detail below. The mass storage device 14 is connected to the CPU 5 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 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 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, digital versatile disks (�DVJS�), 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 2. According to various embodiments of the invention, the computer 2 may operate in a networked environment using logical connections to remote computers through a network 18, such as the Internet. The computer 2 may connect to the 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 computer 2 may also include an input/output controller 22 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in FIG. 1). 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 9 of the 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 9 may also store one or more program modules. In particular, the mass storage device 14 and the RAM 9 may store a spreadsheet application program 10. The spreadsheet application program 10 is operative to provide functionality for the creation and structure of workbooks, such as a workbook 27, in an open file format 24, such as an XML file format. According to one embodiment of the invention, the spreadsheet application program 10 and other application programs 26 comprise the OFFICE suite of application programs from MICROSOFT CORPORATION including the WORD, EXCEL, and POWERPOINT application programs. Embodiments of the present invention greatly simplify and clarify the organization of workbook features and data. The spreadsheet program 10 organizes the �parts� of a workbook file (features, data, themes, styles, objects, etc) into logical, separate pieces, and then expresses relationships among the separate parts. These relationships, and the logical separation of �parts� of a workbook, make up a new file organization that can be easily accessed, such as by a developer's code, without using the spreadsheet application itself. Referring now to FIGS. 2 a-2 c, block diagrams illustrating a workbook relationship hierarchy for various modular parts utilized in the file format 24 for representing a workbook according to various illustrative embodiments of the invention will be described. The workbook relationship hierarchy 208 lists specific spreadsheet application relationships. Optional relationships with respect to validation are indicated in italics, and dashed connecting lines 203 indicate a one to potentially many relationship. Thus, for example there is a worksheet part 217 for each worksheet associated with a workbook 202. The various modular parts or components of the presentation hierarchy 208 are logically separate but are associated by one or more relationships. Each modular part is also associated with a relationship type and is capable of being interrogated separately with or without the spreadsheet application program 10 and/or with or without other modular parts being interrogated. Thus, for example, it is easier to locate the contents of a worksheet cell because instead of searching through all the binary records for cell information, code can be written to easily inspect the relationships in a workbook and find the worksheet parts, effectively ignoring the other features and data in the file format 24. Thus, the code is written to step through the cells in a much simpler fashion than previous interrogation code. Further, �authoring� scenarios, where a developer writes code to insert a new part, or to insert a completely new file without running the spreadsheet application, are simplified due to the modular part file format. A modular content framework may include a file format container 204 associated with the modular parts. The modular parts include, the workbook part 202 operative as a guide for properties of the workbook and the worksheet part 217 associated with the workbook part 202 and operative to specify a definition of cells within a worksheet associated with the worksheet part 217. The workbook hierarchy 208 may also include a document properties part 205 containing built-in properties associated with the file format 24, and a thumbnail part 207 containing a thumbnail associated with the file format 24. The modular parts also include a sheet part 210 containing data associated with a macro sheet, a chart sheet part 212 containing data associated with defining a chart, and a style sheet part 240 representing a theme in the workbook. It should be appreciated that each modular part is capable of being extracted from or copied from the workbook and reused in a different workbook along with associated modular parts identified by traversing relationships of the modular part reused. Associated modular parts are identified when the spreadsheet application 10 traverses inbound and outbound relationships of the modular part reused. Other modular parts may include a style part 220 containing data associated with a style at a cell level in the workbook, a dialog sheet part 214 containing data associated with workbook dialog, a markup maps part 218 containing visuals depicting a markup language format associated with the workbook, and a shared strings part 222 containing a string associated with a plurality of cells in the workbook. Still other modular parts include a workbook connections part 224 containing data associated with interfacing with the workbook, a background picture part 225, a mail envelope part 242 containing envelope data where a user of the workbook has sent the workbook via electronic mail, a code file part 244 containing code associated with the workbook, and a comments part 247 containing comments associated with the workbook. Still further, the modular parts may include a schemas part 254 containing schemas associated with the markup maps part 218, an image part 248 containing image data associated with the workbook, and an embedded object part 230 containing an object associated with the workbook. Other modular parts may also include a user data part 245 containing customized data capable of being read into the workbook and changed, a drawing object part 257 containing an object built using a drawing platform, a legacy drawing object part 252, such as an Escher 1.0 object, a table index part 232 containing data defining a table index associated with the worksheet, and a list part 228 containing data defining a list associated with the worksheet. As an example, embodiments of the present invention make it easier to locate a list in a workbook because any list has a list part 228 separate in the file format 24 with corresponding relationships expressed. The list part 228, as are other modular parts, is logically broken-out and separate from other features & data of the workbook. Further, because the logical structure of a list is clearly understood, it is also less complicated to add more rows of data to a list. Other modular parts associated with the workbook may include a pivot table part 234 containing data defining a pivot table associated with the worksheet, a pivot cache definition part 235 containing data defining a cache associated with the pivot table, and a pivot cache records part 237 containing data associated with the pivot cache definition part. A pivot table is a program tool that allows selected columns and rows of data in a spreadsheet or database table to be reorganized and summarized in order to obtain a desired report. A pivot table turns the data to view it from different perspectives. It should be appreciated that modular parts that are shared in more than one relationship are typically only written to the file once. It should also be appreciated that certain modular parts are global and thus, can be used anywhere in the file format. In contrast, some modular parts are non-global and thus, can only be shared on a limited basis. In various embodiments of the invention, the file format 24 may be formatted according to extensible markup language (�XML�) and/or a binary format. As is understood by those skilled in the art, XML is a standard format for communicating data. In the XML data format, a schema is used to provide XML data with a set of grammatical and data type rules governing the types and structure of data that may be communicated. The XML data format is well-known to those skilled in the art, and therefore not discussed in further detail herein. The XML formatting closely reflects the internal memory structure of an entire workbook. Thus, an increase in load and save speed is evident. Embodiments of the present invention make workbooks more programmatically accessible. This enables a significant number of new uses that are simply too hard for previous file formats to accomplish. For instance, utilizing embodiments of the present invention, a server-side program is able to create a workbook for someone based on their input. For example, creating an analysis report on Company A for the time period of Jan. 1, 2004-Dec. 12, 2004 where all variable input is italicized. Other examples include, an external process scanning and rewriting all workbooks on a network in order to update a company logo and visual color scheme, a chart in one workbook being programmatically copied and inserted into another workbook, and calculation results being retrieved from a workbook and updated to a database nightly. Still another example is a government agency can process workbooks, and more easily convert the features and data to their internal text-based format. FIGS. 2 a-2 c also include relationship types utilized in the file format 24 according to various illustrative embodiments of the invention. The relationship types associated with the modular parts not only identify an association or dependency but also identify the basis of the dependency. The relationship types include the following: a code file relationship capable of identifying code files, a user data relationship, a style sheet relationship, a comments relationship, an embedded object relationship, a drawing object relationship, an image relationship, a sound relationship, a mail envelope relationship, a document properties relationship, a thumbnail relationship, a schema relationship, a chart sheet relationship, a dialog sheet relationship, a worksheet relationship, and a pivot table relationship, a shared string relationship, a lists relationship, a pivot cache relationship, a styles relationship, a markup maps relationship, and a pivot cache metadata relationship Referring to FIG. 2 c also illustrates the listing 259 that lists collection types for organizing the modular parts. The collection types include a chart sheet collection including the chart sheet part 212, a dialog sheet collection including the dialog sheet part 214, a worksheets collection including the worksheet part 217, a pivots collection including the pivot table part 234, and a pivot cache collection including the pivot cache definition part 235 and the pivot cache records part 237. The collection types also include a styles collection including the styles sheet part 240 and the styles part 220, a markup maps collection including the markup maps part 218, a lists collection including the lists part 228, and an embeddings collection including the embedded object part 230 and the user data part 245. FIGS. 3-4 are illustrative routines performed in representing workbooks in a modular content framework according to illustrative embodiments of the invention. When reading the discussion of the routines presented herein, it should be appreciated that the logical operations of various embodiments of the present invention are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance requirements of the computing system implementing the invention. Accordingly, the logical operations illustrated in FIGS. 3-4, and making up the embodiments of the present invention described herein are referred to variously as operations, structural devices, acts or modules. It will be recognized by one skilled in the art that these operations, structural devices, acts and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof without deviating from the spirit and scope of the present invention as recited within the claims set forth herein. Referring now to FIGS. 2 a-2 c and 3, the routine 300 begins at operation 304, where the spreadsheet application program 10 writes the workbook part 202. The routine 300 continues from operation 304 to operation 305, where the spreadsheet application program 10 queries the workbook for worksheet relationships. Next, at operation 307, the spreadsheet application writes the worksheet parts 217 referenced in the workbook part 202 and establishes relationships between each worksheet part 217 and the workbook part 202. Next, at operation 308, the spreadsheet application 10 writes other modular parts associated with relationship types, such as the image part 248, and the schema part 254. Any modular part to be shared between other modular parts is written only once. The routine 300 then continues to operation 310. At operation 310, the spreadsheet application 10 establishes relationships between newly written and previously written modular parts. The routine 300 then terminates at return operation 312. Referring now to FIG. 4, the routine 400 for writing modular parts will be described. The routine 400 begins at operation 402 where the spreadsheet application 10 examines data in the spreadsheet application. The routine 400 then continues to detect operation 404 where a determination is made as to whether the data has been written to a modular part. When the data has not been written to a modular part, the routine 400 continues from detect operation 404 to operation 405 where the spreadsheet application writes a modular part including the data examined. The routine 400 then continues to detect operation 407 described below. When at detect operation 404, if the data examined has been written to a modular part, the routine 400 continues from detect operation 404 to detect operation 407. At detect operation 407 a determination is made as to whether all the data has been examined. If all the data has been examined, the routine 400 returns control to other operations at return operation 412. When there is still more data to examine, the routine 400 continues from detect operation 407 to operation 410 where the spreadsheet application 10 points to other data. The routine 400 then returns to operation 402 described above. Based on the foregoing, it should be appreciated that the various embodiments of the invention include file formats, methods and computer program products for representing workbooks in a modular content framework. 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. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS8055995 *Mar 10, 2006Nov 8, 2011Orangescape Technologies LimitedSystem and method of defining a hierarchical datamodel and related computation and instruction rules using spreadsheet like user interfaceUS8365066 *Feb 9, 2010Jan 29, 2013Konica Minolta Laboratory U.S.A., Inc.Systems and methods for processing markup language specified spreadsheet stylesUS8429118Oct 23, 2009Apr 23, 2013Microsoft CorporationEmbedding and retrieving data in an application file formatUS8589783Feb 9, 2010Nov 19, 2013Konica Minolta Laboratory U.S.A., Inc.Systems and methods for processing color information in spreadsheetsWO2009043025A2 *Sep 29, 2008Apr 2, 2009Microsoft CorpSpreadsheet workbook part libraries* Cited by examinerClassifications U.S. Classification1/1, 715/234, 715/215, 715/235, 707/999.1International ClassificationG06F7/00, G06F17/24Cooperative ClassificationG06F17/246, G06F17/2247European ClassificationG06F17/24S, G06F17/22MLegal EventsDateCodeEventDescriptionMar 18, 2013FPAYFee paymentYear of fee payment: 4Feb 15, 2011CCCertificate of correctionFeb 28, 2005ASAssignmentOwner name: MICROSOFT CORPORATION, WASHINGTONFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ROTHSCHILLER, CHAD B.;WU, SU-PIAO B.;REEL/FRAME:015803/0980;SIGNING DATES FROM 20041210 TO 20041216RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google