This patent application is assigned to
The following quote was obtained by the news editors from the background information supplied by the inventors: "Content management systems can host content such as digital documents (hereinafter documents). Examples of such documents include word processing documents, spreadsheets, slide presentations, digital notebooks, etc. Content management systems have one or more features that interact with content in the documents. For example, content management systems may provide browser-based document editing applications, search indexing, versioning, property promotion/demotion, workflow involving the documents, document permissions and sharing, etc.
"Users have been able to embed files into some documents that are managed by the content management systems. Users have also been able to insert file links into managed documents, and such links could point to other files that are hosted on the content management system."
In addition to the background information obtained for this patent application, VerticalNews journalists also obtained the inventors' summary information for this patent application: "Embedding a file in a document hosted by a content management system can make the embedded file opaque to the hosting content management system. This can prevent the content management system from interacting directly with the embedded file to provide features specifically for that file. Also, inserting a link into a document and separately uploading the linked file to the content management system can break a containment relationship between the two files. As just one example, if someone copies the document that includes the link, the linked file may not be automatically copied with the linking document.
"The tools and techniques discussed herein relate to imitation of file embedding in a document, which may be done without actually embedding the file in the document. Such tools and techniques can allow a file to appear as if it has been embedded in a container document, imitating an embedded relationship between the file and the container document (i.e., imitating one or more behaviors of embedded files). However, the container document and the file can be stored and maintained separately, which can allow a content management system to interact with the contained file to provide one or more features for that file.
"In one embodiment, the tools and techniques can include a client document manager maintaining a container document. The container document can include a file node indicating a file and pointing to a location for the file that is separate from the container document on a remote server (though the pointing may be to a location on the remote server and to another location or via another location, such as to a location in a local cache). User input requesting an update to be performed on the file node can be received. The user input can be directed at the container document. An embedded relationship between the file and the container document can be imitated. The imitation can include responding to the user input by performing the update on the file node, and by requesting that the server perform an update on the file that reflects the update performed on the file node.
"In another embodiment of the tools and techniques, a content management system can maintain a container document on a server. The container document can include a file node indicating a file and pointing to a location for the file that is separate from the container document on the server. A request for an update to be performed on the file node can be received from a remote client. The request can be directed at the container document. In response to the request, the update can be performed on the file node. Additionally, a corresponding update can be performed on the file. The corresponding update can reflect the update performed on the file node.
"This Summary is provided to introduce a selection of concepts in a simplified form. The concepts 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 to limit the scope of the claimed subject matter. Similarly, the invention is not limited to implementations that address the particular techniques, tools, environments, disadvantages, or advantages discussed in the Background, the Detailed Description, or the attached drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
"FIG. 1 is a block diagram of a suitable computing environment in which one or more of the described embodiments may be implemented.
"FIG. 2 is a schematic diagram of a client-server system in conjunction with which one or more of the described embodiments may be implemented.
"FIG. 3 is a flowchart of a technique for imitation of file embedding in a document.
"FIG. 4 is a flowchart of another technique for imitation of file embedding in a document.
"FIG. 5 is a flowchart of yet another technique for imitation of file embedding in a document."
URL and more information on this patent application, see: Tse, David; Holley, Brian; Srinivasan, Varun; Granor, Nathaniel; Kern, Jonathan F.; Andeen,
Keywords for this news article include:
Our reports deliver fact-based news of research and discoveries from around the world. Copyright 2014, NewsRx LLC
Most Popular Stories
- Obama, Ukraine Discuss Russian Incursion in Crimea
- Chinese May Have Spotted Malaysia Airlines Debris
- Social Media Causee Sleep Deprivation in Students
- First-time Jobless Claims Drop Unexpectedly
- Banks Buying Little From Minority Firms: Study
- General Electric Plans IPO of Credit Card Unit
- SXSW Crash Kills 2, Injures 23
- U.S. Business Inventories Up, Retail Sales Down
- 'Candy Crush' Maker Files IPO
- First-time U.S. Jobless Claims Hit 3-month Low