# Patent

## Title
Exposing embedded data in a computer-generated document

## Abstract

A mechanism is provided for embedding an object in a receiving or client document such that a client application may operate on the embedded object to include interrogation and modification of data contained in the embedded object. When a given document object is embedded into a receiving document, data representing the embedded object is saved to a data stream storage for the receiving document. When the embedded object in the receiving document is subsequently requested in response to an operation executed on the embedded object, the receiving application obtains the data representation of the embedded object from the data stream storage. Once the receiving application obtains the data representation of the embedded object, the receiving application may perform operations on the embedded object by accessing the embedded object via its data representation.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
This patent application claims priority to U.S. Patent Application Ser. No. 60/687,461 filed Jun. 3, 2005, entitled “Embedded Document Modeling,” and this patent application is a continuation-in-part of U.S. patent application Ser. No. 11/019,095 filed Dec. 21, 2004, entitled “Method and System for Exposing Nested Data in a Computer-Generated Document in a Transparent Manner,” the disclosures of which are expressly incorporated herein by reference.


BACKGROUND
With the advent of the computer age, computer and software users have grown accustomed to user-friendly software applications that help then write, calculate, organize, prepare presentations, send and receive electronic mail, make music, and the like. For example, modern electronic word processing applications allow users to prepare a variety of useful documents. Modern spreadsheet applications allow users to enter, manipulate, and organize data. Modern electronic slide presentation applications allow users to create a variety of slide presentations containing text, pictures, data or other useful objects.
Often documents, spreadsheets, presentations, and the like, generated by such applications are embedded with document objects from other documents generated by other applications. For example, a user may desire to embed a chart object from a spreadsheet application document into a memorandum document generated by a word processing application. Or, a user may desire to embed a word processing document object into a slide presentation document. While such embedded objects may be displayed in the receiving document, operating on embedded objects via the receiving document application is very limited. For example, a user may be able to move an embedded object in the receiving document using the functionality of the receiving document application, but the user may not interrogate or modify the data contained in the embedded object. For example, if a user desires to modify data contained in a chart object that has been embedded in a word processing document, the user may be required to go back to the providing application document (e.g., spreadsheet application document) to make modifications to the data contained in the embedded chart object, followed by a replacement or update of the embedded chart object in the receiving document.
It is with respect to these and other considerations that the present invention has been made.
SUMMARY
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Embodiments of the invention solve the above and other problems by providing a mechanism for embedding an object from a providing or server document into a receiving or client document such that a client application with which the receiving document is provided may operate on the embedded object to include interrogation and modification of data contained in the embedded object. According to embodiments, when a given document object is embedded into a receiving document, data representing the embedded object, for example, an Extensible Markup Language (XML) representation of the embedded object, is saved to a data stream storage for the receiving document. A schema associated with the data representation may also be saved to the data stream storage. When the data representation of the embedded object is saved, a program identification (progID) and class identification (classID) for the providing application and for the embedded object are maintained in the registry of the operating system that enables operation of the receiving application.
When the embedded object in the receiving document is subsequently requested in response to an operation executed on the embedded object (for example, an attempted modification of data in the embedded object), the receiving application obtains the data representation of the embedded object from the data stream storage based on the progID and classID for the embedded object. Once the receiving application obtains the data representation of the embedded object along with any associated schema, the receiving application may perform operations on the embedded object by accessing the embedded object via the data representation of the embedded object.
These and other features and advantages, which characterize the present invention, will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention as claimed.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram showing the architecture of a personal computer that provides an illustrative operating environment for embodiments of the present invention.
FIG. 2 is a simplified block diagram illustrating interaction between a client application and a server application for obtaining formatting and other information about an embedded object embedded into a client application document from a server application document.
FIG. 3 is a flow diagram of an exposing of nested data associated with an embedded object embedded into a client application document from a server application document according to embodiments of the present invention.
FIG. 4 is a simplified block diagram illustrating interaction between a client application and a server application for obtaining data representing an embedded object to allow operation on the embedded object by the client application.
FIG. 5 is a flow diagram illustrating an exposing of data representing an embedded object to a client application for allowing the client application to operate on the embedded object.



DETAILED DESCRIPTION
As briefly described above, embodiments of the present invention are directed to exposing data representing an embedded document object to allow a receiving or client application to operate on the embedded object. 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 sense 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 refer to like elements through the several figures, aspects of the present invention and an exemplary operating environment will be described. FIG. 1 and the following discussion are intended to provide a brief, general description of a suitable computing environment in which the invention may be implemented. While the invention will be described in the general context of program modules that execute in conjunction with an application program that runs 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 program modules.
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 FIG. 1, an illustrative architecture for a personal computer 2 for practicing the various embodiments of the invention will be described. The computer architecture shown in FIG. 1 illustrates a conventional personal computer, including a central processing unit 4 (“CPU”), a system memory 6, including a random access memory 8 (“RAM”) and a read-only memory (“ROM”) 10, and a system bus 12 that couples the memory to the CPU 4. 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 10. The personal computer 2 further includes a mass storage device 14 for storing an operating system 16, application programs, such as the application program 205, and data.
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 % operating systems 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 205 for providing a variety of functionalities to a user. For instance, the application program 205 may comprise many types of programs such as a word processing application, a spreadsheet application, a desktop publishing application, and the like. According to an embodiment of the present invention, the application program 205 comprises a multiple functionality software application suite for providing functionality from a number of different software applications. Some of the individual program modules that may comprise the multiple functionality application suite 205 include a word processing application 125, a slide presentation application 135, a spreadsheet application 140 and a database application 145. An example of such a multiple functionality application suite 205 is OFFICETM manufactured by Microsoft Corporation. Other software applications illustrated in FIG. 1 include an electronic mail application 130.
FIG. 2 is a simplified block diagram illustrating interaction between a client application (client) and a server application (server) for obtaining formatting and other information about an object embedded into a client application document from a server application document. Referring to FIG. 2, a client application document 215 representing a top-level container receives an embedded object 230 from a server application document representing an inner container. The embedding object 225 represents text, data, pictures, images, charts, and the like that is copied to or moved to the client application document 215, or that is pointed to by the client application document 215.
The client application 205 is representative of a software application being utilized for generating or editing the client application document. The server application 210 is representative of a software application being used for generating or editing the server application document. The client application 205 and the server application 210 may represent multi-application suites containing multiple software applications, for example, word processing applications, spreadsheet applications, slide presentation applications, database applications, and the like. In addition, as should be understood, the client application 205 and the server application 210 may be two of such multiple applications belonging to a single application suite. On the other hand, the client application 205 and the server application 210 may be separate applications operated by different users or entities in a distributed computing network where the client application 205 is enabled to communicate with the server application as described herein.
As illustrated in FIG. 2, an embedding object 225 is embedded into a client application document 215 in order to insert the data, coding or other information associated with the embedding object 225 into the client application document 215 as an embedded object 230. For example, the client application 205 may be a word processing application with which a client application document 215, for example, a memorandum, is being generated or edited. In order to provide a chart of data, for example, salary information for all sales employees of a given organization, the author/editor of the client application document 215 may desire to embed a chart object 225 from a server application document 220, for example, a spreadsheet document, generated or edited by a server application 210, for example, a spreadsheet application. As briefly described above, a problem with prior methods and systems for embedding objects into a client application document results from an inability of the client application 205 responsible for generating and/or editing the client application document 215 to understand or read formatting information, properties, methods, mechanisms, and the like associated with the embedded object imparted to the embedded object by the server application 210 responsible for generating and/or editing the embedded object.
For example, the following is a simplified Extensible Markup Language (XML) representation of a sample word processing document having an embedded slide presentation application object in the sample word processing document. As should be understood by those skilled in the art, the example XML representations illustrated and described below are simplified, are for purposes of example only, and are not limiting in any way of the application or operation of embodiments of the present invention described herein. Referring to the example XML representation below, the information contained in the following representation after the XML markup “<w:binData w:name=“oledata.mso”> and before the XML markup </w:binData> is representative of the slide presentation object embedded into the sample word processing document. As can be seen, the information associated with the embedded object may be very difficult to understand, if at all, by the client application generating or editing the associated client application document, for example, the word processing document.












<?xml version=“1.0” encoding=“UTF-8” standalone=“yes”?>


<?mso-application progid=“Word.Document”?>


<w:wordDocument


xmlns:w=http://schemas.microsoft.com/office/word/2003/wordml>


<w:docOleData>


 <w:binData w:name=“oledata.mso”>


  0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/C


QAGAAAAAAAAAAAAAAABAAAAAQAAAAAAAAAAEAAAAgA


AAAEAAAD+////AAAAAAAAAAD///////////////////////////////////////////////


//////////////////////////////////////////////////////////////////////////


//////////////////////////////////////////////////////////////////////////


/////////////////


/DEANQAzADEANAAxADUAOQA0AAAAAAAAAAAAAAAAAAAA


AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABgAAg


H///////////////8AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA


AAAAAAAAAAAAAAAAAAAAWgoAAAAAAAAAAAAAAAAA


AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA


AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAP


///////////////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA


AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA


AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA


AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA/


///////////////AAAAAAAAAAAAAAAAAAAAAAAAA


  o9RcjOS6a7TCVdc9sz2e+UeMivhf3rqQ16rKUv5C1/GrIg50C2abL


ymb5dtQ0193p4PwRNzkJ+3vazrk5e5zmsU24+e1V75Pznd8785xzBOQ


BLAJUIHYhKSfq0nDgmiGYAM4ELgVnARcDFwHuACmA2YAFzg


LnAe4F5wPuAS4BLgfnAZcD7gQXAQmARsBi4HKgErgA+AF


QBHwQ+BFwJfBhYAlwFXA1cA3wE+Cjx2kZ0LVADLAU+


BtQCdcB1wDLg48By4Hpl+w2obwRWAJ8E6oEg8CnVf64WxKLu


HxEf6U1zzhxEqmiw3pgqY3/k3OcxXxFujscSsVDSCsY67HgwFo4


mrYZIuMUWIbSiIRi3E3Y02ZQMx6IiinJ0iwXd4iV0/Koff3FcDQ


wRk2dfTpgcbxy7a/rvPbbB5Pg+bhj018qG1qaOqHVzOBJ


pisei7KUGaqUm6sBctehmCiNzRfAcx7yNnqX005ixXk0f9Z5zx


NBXd73+Vn1r4Pv3+mnBpQ8/w/H+b5LzkftvIbkHawQ


497aRnLObSM7b3STn5g/UN4Mk1/AjJOcxJ+


 </w:binData>


</w:docOleData>


<w:p>


 <w:r>


  <w:t>


  This is some text


  </w:t>


 </w:r>


</w:p>









According to embodiments of the present invention, when an embedded object is requested by a client application document 215 for embedding in the client application document as an embedded object 230, the client application 205 queries the server application 210 responsible for generating and/or editing a server application document from which the embedded object 230 is being requested for formatting information, properties, methods, mechanisms, and/or the like associated with the requested object. The client application 205 requests from the server application 210 information about the requested object to allow the client application 205 to understand the formatting, coding and other properties associated with the requested object and to enable the client application 205 to operate on the requested object according to the properties imparted to the embedded object by the server application so that the embedded object coding, formatting and properties become transparent and available to the client application.
As described above, the client application requests information about the requested object to enable the client application to better utilize the requested object. According to prior and well-known OLE object embedding principles, an embedded object may include various information that may be available to the client application 205. For example, metafile information may be passed to the client application that is an image that the server application returns from the serving application. But, because the client application does not understand the embedded object's file format, according to prior methods, it is up to the server application to give the client application an image to use to display the object. For instance, if a spreadsheet object is embedded in a word processing document, the view that is displayed of that spreadsheet object in the word processing document is an image of the spreadsheet object. The image is updated whenever the embedded object is activated, and usually this happens when a user double clicks on the embedded object. Other information may include a classID that identifies the server application that should be called to render the embedded object. That is, the classID maps to the server application. Additional information may include information regarding actual persistence of the file. According to one embodiment this information is in the form of an IStorage format. For example, a spreadsheet object within a word processing document is stored similarly as it is stored when it is saved by the spreadsheet application (server).
The metafile information is stored as a separate image that any client application can access as needed. For example, when the image is saved, rather than write the information out as a simple binary data file, the registry is surveyed to determine if the application that matches the classID for the requested object has indicated a content type for the object. According to embodiments, the content type identifies the object. For example, for an image object of a server document, the content type associated with the object may be “JPEG” or “GIF.” If the server application has identified a content type for the object, then a determination is made as to what file extension is associated with the identified content type. If a content type and a file extension are determined, then the client application may call out the content type and apply the correct extension to the file (object). The client application may then take the requested object from the server application document and treat the requested object as a native object of the client application because the client application understands the content type and file extension. In addition, the registry may be surveyed to determine if the persistence format for the file (requested object) is an IStorage format. Some file formats like the well-known “.doc” format are in IStorage format. According to embodiments of the present invention, the object data stream may be “wrapped” in an IStorage format so that it can also be acted on by the client application as described herein.
According to an embodiment, objects may be embedded in embedded objects. For example, a chart object embedded into a word processing document may, in turn, include a slide presentation object from a slide presentation application embedded into the chart object. Accordingly, the slide presentation object would be embedded in the chart object, which may then be embedded in the client application document 215 as the embedded object 230. According to embodiments of the present invention, the server application 210 would request and receive formatting information, properties, methods and mechanisms associated with the slide presentation object embedded into the chart object, and ultimately, the client application 205, for example, a word processing application, would receive formatting information, properties, methods and mechanisms associated with the embedded object from both the example spreadsheet application and the example slide presentation application associated with the slide presentation application object embedded into the chart object.
The following is a simplified XML representation illustrating the nesting of one container (document or object) into another container (document or object). For the following example, consider a first object includes a parts list and consider that an embedded object includes parts identification information.















<container>



 <partslist>



  <part id=”1”/>



  <container>



   <partslist>



    <part id=1’”>



    <part id=”2”/>



   </partslist>



  </container>



  <part id=”n”/>



 </partslist>



</container>










According to a particular example implementation types could be assigned to “parts” and the <part id=“#”/> syntax could be replaced with <part id=“#” type=“item”/> and the nested <container> could be replaced with <part id=“#” type=“container”/>. In addition, an inheritance model with the nested containers may be created. For example, metadata may be associated with a container (document or object) that describes whether or not code might be found within the embedded document's or object's parts. As shown below, this metadata association may be made by using an attribute on the <container> element.















<container containscode=”false”>



 <partslist>



  <part id=”1”/>



  ...



  <part id=”n”/>



 </partslist>



</container>










By creating a hierarchy between nested objects, many problems associated with nested objects described above may be addressed. For example, given the example above, if an embedding is added to the container that contains code (e.g., potential virus), without a hierarchical relationship between the embedded object and the receiving document or object a representation like the following representation may result.















<container containscode=”false”>



 <partslist>



  <part id=”1”/>



  <container containscode=”true”>



   <partslist>



    <part id=1’”/>



    <part id=”2”/>



   </partslist>



  </container>



  <part id=”n”/>



 </partslist>



</container>










On the other hand, with a relationship between the embedded object and the containing document or object (container), an improved representation such as the following may be generated.















<container containscode=”true”>



 <partslist>



  <part id=”1”/>



  <container containscode=”true”>



   <partslist>



    <part id=1’”/>



    <part id=”2”/>



   </partslist>



  </container>



  <part id=”n”/>



 </partslist>



</container>










As described herein, when an embedding object 225 is requested from a server application document 220 for embedding in a client application document 215 as an embedded object 230, a formats query 240 is passed from the client application 205 to the server application 210 for information about file formats associated with the requested object. As described herein, the term “file formats” is meant to include format types, for example, Hypertext Markup Language (HTML), rich text formatting (RTF), XML, and the like, formatting properties, and methods and/or mechanisms (coding) utilized by the server application for generating or editing the requested object.
According to one embodiment of the present invention, the client application 205 passes an application program interface (API) call to the server application 210 for the requested information. According to this embodiment, the client application 205 may pass a first API call for obtaining all file formats available from the server application that may have been used by the server application on or in association with the requested object. The first API call may be in the form of “EnumerateFileFormats( )” for obtaining a listing of all file formats available from the server application 210 that may be utilized by the server application for formatting or applying properties to the requested object. If the server application is of a different type as the client application (e.g., spreadsheet application versus word processing application), the client application may need a list of all available file formats for operating the embedded object according to the file formats native to the object as received from the server application document.
Alternatively, a second API call may be passed to the server application to obtain only the file format information associated with the requested object. For example the second API call may be in the form of “GetFileData(fileformat)” and may be passed from the client application 205 to the server application 210 for obtaining particular format information applied to the particular requested object. Once the client application 205 obtains a listing of available file formats and/or particular file formats applied to the requested object, the client application 205 may utilize the requested object in the client application document 215 in a transparent manner as the client application 205 would utilize or operate on other data or information contained in the client application document 215.
According to alternative embodiments, the formats query 240 between the client application 205 and the server application 210 may take the form of a web service 250, illustrated in FIG. 2, for obtaining file format information from the server application 210. As should be understood, the server application 210 may be located separately from the client application 205 over a distributed computing network such as the Internet 245. According to this embodiment of the present invention, a web service 250 may be utilized for receiving queries from client applications 205 and for obtaining requested file format information from server applications 210. According to a web service application 250, the client application 205 does not have to generate API calls or other requests according to the known language or protocols of the server applications 210. That is, the web service 250 may operate as an interface or layer between the requesting client application 205 for receiving requested information from server applications associated with requested server application documents and requested embedding objects 225.
According to another embodiment, a file format manifest may be generated by the server application 210 for enumerating file formats available from the server application or that are associated with particular objects from server application documents. According to this embodiment, when an embedding object 225 is requested from a server application document 220 for embedding into a client application document 215, the formats query 240 from the client application 205 to the server application 210 requests the file format manifest 260 from the server application 210 associated with the server application document and the embedding object 225. Once the client application 205 receives the file format manifest 260, the client application 205 may parse the file format manifest 260 to obtain file format information associated with the server application 210 or to obtain particular file format information associated with the requested embedding object 225.
Having described embodiments of the present invention with respect to FIGS. 1 and 2 above, FIG. 3 is a flow diagram illustrating steps performed by a method and system of the present invention for exposing nested data associated with an embedded object embedded into a client application document from a server application document. The routine 300 begins at start block 305 and proceeds to block 310 where a request is received at the client application 205 for an embedded object in the client application document 215. For example, the request may be in the form of a copying of a chart object from a spreadsheet document 220 containing employee salary information into a memorandum document 215 being generated with a word processing client application 205.
At operation 315, in response to the request for the embedded object 230 into the client application document 215, the client application 205 sends a formats query 240 to the server application 210 for a listing of application file formats available from the server application 210, for example, a spreadsheet application. As described above, the formats query 240 may be in the form of an API call to the server application 210, or the formats query 240 may be a call to a web service 250, or the formats query 240 may be a request for a file format manifest 260 for review by the client application 205. At operation 320, the client application 205 queries the server application 210 for particular file formats information associated with the requested object 225. As should be understood, the query from the client application to the server application for both a listing of available file formats and for particular file formats associated with the requested object may be in the form of a single formats query 240.
At operation 325, the requested file formats information is received by the client application 205, and at operation 330, the client application 205 receives and embeds the requested object 225 into the client application document 215 as the embedded object 230. At operation 345, the client application 205 utilizes the received file format information for processing and for rendering transparent the embedded object 230. For example, if the embedded object 230 is a chart object from a spreadsheet application document containing a summary of employee salary information, because the client application 205 has access to file format information associated with the embedded object, all other information associated with the embedded object becomes transparent to the client application 205. For example, if the embedded object also includes detailed employee information associated with the summary salary information, the client application 205 may access the detailed employee information and may process or otherwise operate on the detailed information associated with the embedded object because the client application 205 has access to file formats, methods, mechanisms or other properties applied to or associated with all data contained or associated with the embedded object as received from the server application document 220 and as imparted to the embedded object by the server application 210. The method ends at operation 395.
As described above with reference to FIGS. 1-3, a mechanism is provided for exposing formatting data for an embedded object to allow a receiving or client application to display an embedded object so that the embedded object does not become an opaque region in the client application document outside the functional reach or understanding of the client application. According to additional embodiments of the invention, a mechanism is provided for exposing data representing an embedded object to a receiving or client application to allow the receiving or client application to operate on the embedded object to allow for interrogation and modification of data contained in the embedded object by the receiving or client application.
As illustrated in FIG. 4, according to embodiments, when an embedding object 225 is embedded from a providing or server application document 220 into a receiving or client application document 215 as an embedded object 230, data representing the embedded object 230 is stored to a data stream storage 410 for the client application document. According to an embodiment, the data stream storage 410 for the client application document is in the format of an IStorage stream for the receiving document. For example, if the receiving or client application document is a word processing document, a data stream containing all data for the receiving document including user data, formatting data, file format data, or any other data required for representation of the receiving document and required by the client application 205 for operating the receiving document are stored to the data stream storage 410. When an object is embedded from a server or providing document, for example, a spreadsheet document, data representing the embedded object is inserted into the data stream for the receiving or client document 215. When data representing the embedded object is stored to the data stream for the client document, an identification of data representing the embedded object is also stored. According to an embodiment, a program identification (progID) and a class identification (classID) for the embedded object and for the providing or server application 210 associated with the embedded object are maintained in the registry of the operating system 16 that enables operation of the client application 205.
According to embodiments, data representing the embedded object may be stored to the data stream 410 according to different formats. For example, a first data representation of the embedded object may be stored to the data stream according to an Extensible Markup Language (XML) format, described below, and a first program ID and a first class ID may be stored to the registry for the XML format. Other data representations for the embedded object may be stored to the data stream 410 according to alternate formats, for example, binary format, and the alternate formats may be registered with the operating system registry according to alternate program IDs and class IDs. Thus, a requesting client application may request data representing the embedded object from the data stream 410 according to a desired data format (e.g., XML, binary, other).
As described above, according to one embodiment, data representing the embedded object is stored to the data stream 410 as an Extensible Markup Language (XML) data representation. In addition, an XML schema associated with the XML data representation of the embedded object may be stored with the XML representation. As should be appreciated by those skilled in the art, the XML schema associated with the XML representation of the embedded object may provide grammatical and syntax rules associated with the XML markup utilized for representing the embedded object. Thus, a receiving or client application 205 may utilize the XML representation of the embedded object in accordance with the associated XML schema file or data. That is, according to embodiments, as long as the receiving or client application 205 may consume the XML representation of the embedded object according to the associated XML schema, the client application 205 may utilize the embedded object via the native functionality of the client application 205 to include interrogation (search and find) and modification of data contained in the embedded object.
For example, if a given embedded object includes a chart object containing data from a spreadsheet document that has been embedded in a word processing document, then a receiving word processing application may utilize data contained in the embedded chart object based on the XML representation of the data contained in the chart object. For example, if a particular cell of data contained in the chart object has been marked up with XML data that has been defined by an associated XML schema, then the receiving or client application 205 may search, find, and modify the data contained in the example cell in the spreadsheet chart using the native functionality of the client word processing application because the word processing application may locate and operate on the data based on its location and definition in the embedded object according to the XML representation of the data.
Having described embodiments of the present invention with respect to FIG. 4 above, FIG. 5 is a flow diagram illustrating an exposing of data representing an embedded object to a client application for allowing the client application to operate on the embedded object. The method 500 begins at start operation 505 and proceeds to operation 510 where an object is embedded into a client document. For purposes of example, consider that a chart containing one or more rows and columns of data is embedded from a spreadsheet document 220 into a word processing document 215.
At operation 515, data contained in the embedded object is saved to the data stream storage 410 for the receiving client document 215. At operation 520, the embedded object is saved as an XML representation, along with any associated or required XML schema for the XML representation of the embedded object. At operation 525, a program ID and a class ID for the XML representation of the embedded object are stored in the registry of the operating system 16 that enables operation of the receiving client application 205. As described above, data representing the embedded object may be stored to the data stream storage 410 for the client document 215 according to other formats, for example, a binary format. If multiple formats of the embedded object data are stored to the data stream storage 410, then unique program IDs and class IDs for the different formats are registered with the operating system registry.
At operation 530, a request is received at the client application 205 for the embedded object. As should be understood, a request received for the embedded object may be in the form of any attempted operation on the embedded object (including operation on data contained in the embedded object). For example, a request for the embedded object may be in the form of a search for particular data contained in the embedded object. For another example, a request for the embedded object may be in the form of an attempt to move the embedded object in the client document 215. For another example, a request for the embedded object may be in the form of an attempt to modify (insert, delete, copy, move, paste, and the like) data contained in the embedded object.
At operation 535, in response to the request for the embedded object, the client application 205 parses the data stream storage 410 for the data representation of the embedded object based on the program ID and class ID registered in the operating system registry for the XML representation of the requested embedded object. As should be appreciated if the client document 215 is in XML format, then the program ID and class ID used to locate the data representation will be the IDs associated with the XML formatted data representation. If the client document 215 is formatted according to another format, for example, binary format, then an alternate format data representation of the embedded object may be requested. Next, the client application 215 retrieves the XML representation of the embedded object along with any associated XML schema from the data stream storage for the client document 215. According to embodiments, the XML based representation of the embedded object is retrieved by the client application.
At operation 540, the client application 205 processes the request for the embedded object in the client document 215 based on the retrieved XML representation of the embedded object. For example, if the requested operation includes searching and finding a particular data item in the embedded object, then the client application 205 will utilize its native search and find functionality to find the desired data in the embedded object based on the XML markup applied to the desired data in accordance with any XML schema associated with the embedded object. For example, if the desired data is represented by an XML markup tag <datacell2>, then the client application 205 may parse the XML representation of the embedded object to locate the data represented by this particular markup in order to process the requested search and find operation. The routine ends at end operation 590.
As described herein, exposing data representing an embedded document object is provided to allow a receiving or client application to operate on the embedded object. 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.

## Claims

1. A computer readable storage medium containing computer executable instructions which when executed by a computer perform a method for exposing data of an embedded object to a receiving software application, comprising:
sending, from the receiving software application, a formats query for a file format manifest comprising information about file formats associated with a requested embedded object, the file formats comprising at least one of formatting properties, methods, and coding utilized by a providing software application for editing the requested embedded object;
parsing the file format manifest to obtain the information about the file formats;
storing a data representation of the embedded object, wherein the object is embedded in a receiving document in a data stream representing the receiving document according to a data format, wherein the object is embedded in the receiving document from a providing document, wherein when the object is embedded from the providing document, the data representation of the object is inserted into the data stream by the providing software application associated with the embedded object for receipt by the receiving software application, wherein the data stream comprises user data, formatting data, file format data, and other data for representing the receiving document and for operating the receiving document containing the embedded object, by the receiving software application, wherein storing the data representation of the object includes storing a markup language representation of the object in the data stream representing the receiving document;
receiving a program ID and a class ID, associated with the data format, to identify the data representation of the embedded object, wherein the program ID and the class ID are associated with the providing software application;
receiving a request for an operation on the object at the receiving software application;
in response to receiving the request for an operation on the object at the receiving software application, parsing the data stream for the data representation of the object; and
at the receiving software application, utilizing the data representation of the object for processing the operation on the object via a native functionality of the receiving software application, wherein the object comprises a file format utilized by the providing software application for generating a first document type which is different than a file format utilized by the receiving software application for generating a second document type.

2. The computer readable storage medium of claim 1, prior to storing the data representation of the object in the data stream representing the receiving document, receiving a request for embedding the object from a providing document into the receiving document.

3. The computer readable storage medium of claim 1, further comprising storing a markup language schema associated with the markup language representation of the object in the data stream representing the receiving document.

4. The computer readable storage medium of claim 3, wherein utilizing the data representing the object for processing the operation on the embedded object includes parsing the markup language representation of the object for exposing the object to one or more functionalities of the receiving software application.

5. The computer readable storage medium of claim 1, further comprising storing the program ID and the class ID for the data representation in the data stream representing the receiving document.

6. The computer readable storage medium of claim 5, further comprising maintaining the program ID and the class ID in an operating system registry.

7. The computer readable storage medium of claim 5, wherein parsing the data stream for the data representation of the object includes locating the data representation of the object based on the program ID and the class ID.

8. A computer readable storage medium containing computer executable instructions which when executed by a computer perform a method for exposing data of an embedded object to a receiving software application, comprising:
sending, from the receiving software application, a formats query for a file format manifest comprising information about file formats associated with a requested embedded object, the file formats comprising at least one of formatting properties, methods, and coding utilized by a providing software application for editing the requested embedded object;
parsing the file format manifest to obtain the information about the file formats;
storing an Extensible Markup Language (XML) representation of the object in a data stream representing the receiving document, wherein the object is embedded in the receiving document from the providing document, wherein when the object is embedded from the providing document, the XML representation of the object is inserted into the data stream by a providing software application associated with the embedded object for receipt by the receiving software application, wherein the data stream comprises user data, formatting data, file format data, and other data for representing the receiving document and for operating the receiving document containing the embedded object, by the elk & receiving software application;
receiving a program ID and a class ID to identify the XML representation of the embedded object, wherein the program ID and the class ID are associated with the providing software application;
receiving a request for an operation on the object at the receiving software application;
in response to receiving the request for an operation on the object at the receiving software application, parsing the data stream for the Extensible Markup Language (XML) representation of the object in the data stream representing the receiving document; and
at the receiving software application, utilizing the Extensible Markup Language (XML) representation of the object for processing the operation on the object via a native functionality of the receiving software application, wherein the object comprises a file format utilized by the providing software application for generating a first document type which is different than a file format utilized by the receiving software application for generating a second document type.

9. The computer readable storage medium of claim 8, further comprising storing an XML schema associated with the XML representation of the object in the data stream representing the receiving document.

10. The computer readable storage medium of claim 8, wherein utilizing the Extensible Markup Language (XML) representation of the object for processing the operation on the object includes parsing the XML representation of the object for exposing the object to one or more functionalities of the receiving software application.

11. The computer readable storage medium of claim 8, further comprising storing the program ID and the class ID for the XML representation in the data stream representing the receiving document.

12. The computer readable storage medium of claim 11, further comprising maintaining the program ID and the class ID in an operating system registry.

13. The computer readable storage medium of claim 11, wherein parsing the data stream for the XML representation of the object includes locating the XML representation of the object based on the program ID and the class ID.

14. A method for exposing an embedded object to a receiving software application, comprising:
sending, from the receiving software application, a formats query for a file format manifest comprising information about file formats associated with a requested embedded object, the file formats comprising at least one of formatting properties, methods, and coding utilized by a providing software application for editing the requested embedded object;
parsing the file format manifest to obtain the information about the file formats;
storing, by a client computer, an Extensible Markup Language (XML) representation of an object embedded in a receiving document in a data stream representing the receiving document, wherein the object is embedded in the receiving document from a providing document, wherein when the object is embedded from the providing document, the XML representation of the object is inserted into the data stream by a providing software application associated with the embedded object for receipt by the receiving software application, wherein the data stream comprises user data, formatting data, file format data, and other data for representing the receiving document and for operating the receiving document containing the embedded object, by the receiving software application;
receiving a program ID and a class ID to identify the XML representation of the embedded object, wherein the program ID and the class ID are associated with the providing software application;
receiving, by the client computer, a request for application of a functionality of the receiving software application on the object;
in response to receiving the request for application or a functionality of the receiving software application on the object, retrieving, by the client computer, the Extensible Markup Language (XML) representation of the object;
at the receiving software application, parsing the XML representation of the object for exposing the object to the functionality of the receiving software application; and
utilizing the XML representation of the object for applying the functionality to the object via a native functionality of the receiving software application, wherein the object comprises a file format utilized by the providing software application for generating a first document type which is different than a file format utilized by the receiving software application for generating a second document type.

15. The method of claim 14, further comprising storing the program ID and the class ID the XML representation in the data stream representing the receiving document.

16. The method of claim 15, wherein parsing the XML representation of the object for exposing the object to the functionality of the receiving software application includes locating the XML representation of the object based on the program ID and the class ID.