Abstract: Client and server based copies of a file are maintained in synchronicity as changes are made to the file. Data is compared to a previous version known to both the client and server and a highly compressed representation of the differences between the two is generated. These differences, or “diffs”, are then transmitted, and may use extensions to the HTTP (HyperText Transport Protocol) protocol.

Abstract: A method is disclosed for a recipient to receive rights management (RM) protected content. The protected content is encrypted and decryptable according to a content key (KD), where (KD) is found in a corresponding license. In the method, the protected content is received while connectively coupled to a network through which the protected content may be obtained, and it is recognized that the received protected content is in fact protected content. In response to receiving the protected content and recognizing same, the license for the protected content is obtained from an RM server while still connectively coupled to the network and in an automatic manner. Thus, the license is available to the recipient even when such recipient is not connectively coupled to the RM server by way of the network at a later time. In one particular embodiment of the present invention, the protected content is received within an email.

Abstract: A method is employed to propagate rights management (RM) protection to an email and to an attachment thereof comprising an RM-protectable document. The email with the RM-protectable attachment is authored, and a content key (KD) and a bind ID are generated. RM protection is first applied to the RM-protectable attachment of the email based on the generated (KD) and the generated bind ID, and the RM-protected attachment is attached to the email. RM protection is then applied to the email with the attached RM-protected attachment based on the generated (KD) and the generated bind ID. The RM-protected email and the RM-protected attachment thereof thus share the generated (KD) and the generated bind ID such that a license obtained for the RM-protected email and having therein the generated bind ID and the generated (KD) can be applied to render the RM-protected email and also the RM-protected attachment thereof.

Abstract: A method is disclosed for rendering content encrypted according to a cryptographic key, where the content has corresponding rights data including a decryption key (KD) for decrypting the encrypted content, and where (KD) in the rights data is encrypted according to a public key of a rights management (RM) server (PU-RM) to result in (PU-RM(KD)). The RM server normally delivers (KD) within a license, but upon being decommissioned can no longer issue such license. In the method, a notification is received that the RM server has been decommissioned, and thereafter an attempt is made to render a piece of content. Such content is determined to be protected to the decommissioned RM server, and a request is sent to the decommissioned RM server for the content key (KD) for the content rather than any license. Thereafter (KD) is received from the decommissioned RM server.

Abstract: A rights-managed email is provided for sending protected content from a sender to a recipient, whereby the recipient can render the protected content with a corresponding license if the recipient satisfies terms set forth in the license. In the email, a main information portion has a message that the email is rights management protected, and an attachment portion has the protected content. The recipient if enabled can render the protected content in the attachment portion. If not enabled, the recipient can only review the main information portion having the message. The enabled recipient recognizes that the email has the protected content in the attachment portion thereof, discounts the main information portion of the email, and examines the attachment portion of the email and proceeds based thereon to render the protected content in the attachment portion.

Abstract: A document store delivers a document requested therefrom from a folder having rights information associated therewith. In response to a request for a copy of the document, rights data for the copy of the document is defined based on the rights information of the folder, and the copy of the document and the defined rights data thereof are published to result in a package with the rights data and the copy of the document encrypted according to a content key (KD) to result in (KD(copy)). The formed package is then delivered to the requester. The rights data can be discovered upon the requester attempting to render the package and such discovery triggers a request for a corresponding license based on such rights data. The license includes (KD) therein in a form available to the requester to decrypt (KD(copy)) if the requester satisfies the rights data.

Abstract: A rights-managed document has protected content from an author thereof, whereby a recipient of the document can render the protected content with a corresponding license if the recipient satisfies terms set forth in the license. In the document, a storage portion has a message that the document is rights management protected, and a custom data portion has a section including the protected content. The recipient if enabled can render the protected content in the custom data portion and if not enabled can only review the storage portion having the message. An enabled recipient handles the received rights-managed document by recognizing that the document has the protected content in the custom data portion thereof, and discounting the storage portion of the document. Thus, the recipient examines the custom data portion of the document and proceeds based thereon to render the protected content in the custom data portion.

Abstract: Content is encrypted according to a content key (CK) to result in (CK(content)) and the content key (CK) is protected according to a public key for a license server (PU-RM). Rights data is retrieved from a rights template to be associated with the content, and rules for modifying the retrieved rights data are also retrieved from the retrieved rights template. The retrieved rights data from the rights template is modified according to the rules, and the rights data and the protected content key (CK)) are submitted as a rights label to the license server for signing thereby. The license server thus validates the rights label and, if valid, creates a digital signature based on a private key (PR-RM) corresponding to (PU-RM) and based at least in part on the rights data to result in a signed rights label (SRL), and returns the SRL.

Abstract: A server is implemented with a modified file open action, which, when a user performs the modified open, initially opens a file without locking the file. When a user indicates (either explicitly or implicitly) that the user is attempting to or intending to open the file, the file can then be locked for editing. In this way, the default action when a user requests a file is to open the file without denying other users access to the file. Then, when the user indicates that editing should occur, the lock for the file is obtained.

Abstract: Depth-related requests without root-level information or actions according to standard request-response protocols such as HTTP are disclosed. For example, in one embodiment, a method specifies a request, such as a PROPFIND command, for application against a collection, such as a hierarchy of folders. Within a DEPTH header of the request, the method includes a NOROOT token to indicate that root-level information of the collection is unwanted. The request is then output, according to a predetermined transport protocol such as HTTP. In one embodiment, the outputting of the command is also according to a predetermined markup language, such as XML.