About: Object Linking and Embedding is a research topic. Over the lifetime, 411 publications have been published within this topic receiving 9225 citations. The topic is also known as: OLE.
TL;DR: In this article, the signator of an electronic document can be verified by embedding a security object, for example, supported by an object linking and embedding (OLE) capability, in the electronic document at a location selected by the signators.
Abstract: The integrity or the signator of an electronic document can be verified by embedding a security object, for example, supported by an object linking and embedding (OLE) capability, in the electronic document at a location selected by the signator. The embedded security object includes security information and an identifier for invoking the processing of the security information. The security information may include a document digest that characterizes the electronic document at the time the security object was embedded, a signature digest that identifies the signator and that characterizes the instance of the embedded security object, and the signator's electronic chop, which may be the signator's digitized signature or other graphic image. In addition, the security information can be encrypted using either private key encryption or public key encryption. When the electronic document is later displayed, the identifier invokes processing that decrypts the security information and calculates the document digest based on the current state of the electronic document. The signator of the electronic document can be verified based upon the result of the decryption. The integrity of the electronic document can be verified if the decrypted document digest matches the calculated document digest. If the signator and the document integrity are confirmed, the electronic chop is displayed in the document. If, however, the signator or document integrity are not verified, the electronic chop is not displayed. In addition, a warning message may be displayed if verification fails.
TL;DR: A system for inserting new objects into existing photographs by querying a vast image-based object library, pre-computed using a publicly available Internet object database, to shield the user from all of the arduous tasks typically involved in image compositing.
Abstract: We present a system for inserting new objects into existing photographs by querying a vast image-based object library, pre-computed using a publicly available Internet object database. The central goal is to shield the user from all of the arduous tasks typically involved in image compositing. The user is only asked to do two simple things: 1) pick a 3D location in the scene to place a new object; 2) select an object to insert using a hierarchical menu. We pose the problem of object insertion as a data-driven, 3D-based, context-sensitive object retrieval task. Instead of trying to manipulate the object to change its orientation, color distribution, etc. to fit the new image, we simply retrieve an object of a specified class that has all the required properties (camera pose, lighting, resolution, etc) from our large object library. We present new automatic algorithms for improving object segmentation and blending, estimating true 3D object size and orientation, and estimating scene lighting conditions. We also present an intuitive user interface that makes object insertion fast and simple even for the artistically challenged.
TL;DR: In this article, a new object for pasting data within a clipboard to a desktop for an object management facility is created, and an icon is displayed on the desktop for the new object.
Abstract: In response to a user pasting data within a clipboard to a desktop for an object management facility, a new object for the data is created. The data is placed within the new object, and an icon is displayed on the desktop for the new object. When the data is text, the new object is created to be of a type which contains text. When the data is bitmapped, the new object is created to be of a type which contains bitmaps. The data is placed in the clipboard, for example, in response to a Cut command or in response to a Copy command from an application process originally processing the data. The data can reformatted, for example, before exporting the data from the application process, before importing the data to the new object or after importing the data to the new object. Also, in response to a user selecting a first object and issuing a conversion command, classes of objects into which the first object may be converted are displayed to the user. Upon the user selecting a class of objects into which the first object is to be converting, the first object is converted into a new object of the selected class of objects. The new object is created, data from the first object is extracted and sent to the new object. The data may be converted to a format usable by the first object, by the new object or by the object management facility.
TL;DR: In this article, a data synchronization protocol is developed that is capable of adapting to different types of object stores and the characteristics of network connection media to optimize data synchronization, which is based on both the object store based system and the object version management mechanism.
Abstract: Object stores are used as building blocks to construct a system with variable complexity on a network. Typically, an object store comprises information (e.g., data) stored in object format, or objects. The objects and object stores are managed by an object version management mechanism that adapts to different object store types and optimizes resource consumption by each object store. Various data fields are used to indicate an object's version within an object store. Version information is used to compare the states among matching object replicas in matching object stores. Utilizing both the object store based system and the object version management mechanism, a data synchronization protocol is developed. The data synchronization protocol is capable of adapting to different types of object stores and the characteristics of network connection media to optimize data synchronization.
TL;DR: In this article, a method of classifying a computer object as malware includes receiving at a base computer data about a computer objects from each of plural remote computers on which the object or similar objects are stored.
Abstract: In one aspect, a method of classifying a computer object as malware includes receiving at a base computer data about a computer object from each of plural remote computers on which the object or similar objects are stored. The data about the computer object received from the plural computers is compared in the base computer. The computer object is classified as malware on the basis of said comparison. In one embodiment, the data about the computer object includes one or more of : executable instructions contained within or constituted by the object; the size of the object; the name of the object; the logical storage location or path of the object on the respective remote computers; the vendor of the object; the software product and version associated with the object; and, events initiated by or involving the object when the object is created, configured or runs on the respective remote computers.