Microsoft Technology Licensing, LLC

Microsoft Corporation

Hai Liu

Hani Saliba

Noah Benjamin Edelstein

Anne M Archambault

Marcin Sawicki

Ethan Joseph Bernstein

Ruth Kikin-Gil

Lauren Nicole Antonoff

Steven James Rayson

John Griffin

Cedric Patrick Dussud

Andrew Quinn

Dustin G Friesenhahn

Noah Edelstein

Jason Matthew Cahill

Christopher Hugh Pratley

Brett David Brewer

Jason F Morrill

Steven Wayne Ickman

William L Portnoy

Darren Alexander Apfel

David Benjamin Lee

Lars Hasso Liden

Brandon V Taylor

Christopher James Antos

Andrew Grey Carlson

Andrew Sean Watson

Adrian Fanaru

Shahin Shayandeh

Sarah Faulkner

Katrika Marie Morris

Jennifer P Michelstein

Mingquan Xue

Nathaniel George Freier

Jonathan Fred Kern

Steven Richard Hollasch

Sean Lamont Grant Livingston

Raj B Merchant

David M Buchthal

Timothy Paul McConnell

Steve Rayson

Chad Garrett Waldman

Mitika Gupta

Robert G Lefferts

Janice Von Itter

Nelle Steele

Luis Angel Mex

Ethan D Gur-esh

Ruihua Song

Wei-Ying Ma

Ji-Rong Wen

Architecture that provides enhanced tag telemetry in a microblogging communications infrastructure. The architecture provides efficient discovery and tracking of topics that are of interest to a specific user by enabling users to follow (track) hash tags (#tag) and to receive and view all messages tagged with the hash tag appear in the user's personal feed. Each hash tag has a persisted tag page that aggregates all the associated activity, and includes a list that includes, but is not limited to, the tag followers, the most frequent user (uses the tag the most often in a specific time frame), a description, related tags, for example. The user can receive all the updates in the user's personal feed, and see an aggregation of all the messages and conversations associated with the tag in single place. The user can also mute the tag to prevent the receiving of tag information.

Hash tag management in a microblogging infrastructure

Methods, computer systems, and computer-storage media are provided for connecting devices. Shared spaces may be created among one or more users and/or devices. Based on various factors including locations, histories among users, time of day, etc., spaces may be created among users such that content may be shared within the shared space. The spaces may be created using multiple technologies such that one user may connect to the space via a first identifier format while a second user may connect to the space via a second identifier format. Once created, content may be shared with one or more users of the space. Depending on privacy and/or security settings of the space, any user may invite other users to join the space. The content may be available to any participant once the space has terminated.

Creating connections and shared spaces

Server-based collaboration is initiated by an email. When the user creates the email message with attachments, a collaboration website is provisioned. The collaboration website allows collaborations on the attached documents by the recipients of the message. The ease of collaboration with email and the advantages of the collaboration server are thus both available to the user.

Method to initiate server based collaboration on e-mail attachments

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.

Method to delay locking of server files on edit

Method to initiate server based collaboration on E-mail attachments

Concepts and technologies are described herein for creating variations when transforming data into consumable content. In accordance with the concepts and technologies disclosed herein, a computing device can execute a transformation engine for transforming data into the consumable content. The computing device can be configured to analyze the data to identify relationships among data elements or other portions of the data, and to identify any possible approaches to transforming the data ('worlds') based upon the relationships and the data. The worlds can be ranked and selected based upon rank. The computing device can obtain rules associated with the selected and apply the rules to the data to generate the output. In some embodiments, the computing device can be configured to obtain and apply feedback regarding the world selection.

Creating variations when transforming data into consumable content

Architecture that facilitates the discovery of interesting and relevant content by a user in a serendipitous way on a microblogging site. For example, relevant content can be defined as connected to the user, the user's work, and user interests, while interesting content can be defined as content that does not directly affect the user, yet the user chooses to obtain (e.g., for viewing, interacting, etc.). The content can be presented as a tile cluster, where each tile is a specific content type (e.g., image, link, post, user recommendations, tags, etc.). Additionally, the content can be obtained and presented relative to a specific temporal setting such as the latest content. The different content types are visually distinguished such that one type of content looks and behaves differently from another content type. The user can also drill into content details from the top content.

Aggregated view of content with presentation according to content type

Architecture that enables separation of a user interface (UI) upgrade from the content and application logic upgrade. Administrators can upgrade to take advantage of new infrastructure features, and independently schedule the UI upgrade, for example, to accommodate customization work or to ensure user training. Furthermore, administrators can now allow users to choose when to switch to the new UI. More specifically, the architecture facilitates the separation of a UI upgrade from content and application logic upgrade, the ability to control the UI upgrade at multiple levels of precision, the ability for application logic and UI components to change behaviors based on the UI version of the context, and the ability to 'preview' the updated UI before permanently switching to it. Additionally, UI components can be filtered to only appear in the appropriate UI version, and the site's UI version can be compared to versions that a component is compatible with.

Upgrade management of application components

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.

Optimizing file replication using binary comparisons

A server file replication technique is implemented with three local copies of a replicated file. First, a shadow file is a copy of the last known good version of the file on the server. Second, a local copy is the user's working copy. Whatever changes the user has made to the file are stored in the local copy. Third, a rollback file is a copy made of the local copy if the local copy changes (for example, when conflicts are resolved or the server version is copied to the local copy.) Different states exist, based on whether these copies contain differences from each other and from the server version, and based on the user's use of the document. These states guide what is done to maintain the local copies and whether conflict resolution is required.

Method for managing multiple file states for replicated files

A system and method is provided to automatically associate type-specific information with a document of a prescribed type. The type information includes instance-specific type information that can be instantiated to each document of the prescribed type. The type information also includes generic type information that is automatically applied to all documents of the prescribed type. Such generic type information includes policies that govern, for example, the life span of the documents or who can access the documents. Instance-specific type information can be demoted to and promoted from a document of the prescribed type. Generic type information can only be demoted to a document of the prescribed type. Type information may be demoted into a document only when the document is requested.

Method for automatically associating data with a document based on a prescribed type of the document

Growing community of inventors

Sammamish, WA, United States of America

Hai Liu