Microsoft Technology Licensing, LLC

Pablo Castro

Michael Pizzo

Jason Duane Clark

Lance Olson

Alex James

Michael Justin Flasko

Sid Jayadevan

Mike Flasko

Siddharth Jayadevan

Andrew Conrad

Subramanian Muralidhar

Blaine J Dockter

Pratik Patel

Alexander Douglas James

Nikhil Kothari

Brian J Deen

Ramachandran Venkatesh

Alazel Acheson

Michael Ray Clark

Jose A Blakeley

Chris A Suver

Colin Joseph Meek

Adam Wade Smith

Robert Michael Howard

Dax H Hawkins

Christian Kleinerman

Kawarjit Bedi

Stephen Frederick Starck

Lale R Divringi

Marcelo Lopez Ruiz

Benjamin Albahari

Simon Cavanagh

Sharad Sundaresan

Eugene Shvets

Alyssa Heather Henry

Gary Liam Cavanagh

Mark Ashton

Konstantin Isakov

The subject disclosure relates to techniques for performing an operation on a resource, based on a state of the resource, by invoking a hypertext transfer protocol (HTTP) request on a universal resource locator (URL) indicating the operation. An interface component can receive a request including an HTTP method and a URL including a first portion indicating a resource and a second portion indicating an operation. Further, an invocation component, in response to the operation being associated with the resource, can invoke the operation on the resource utilizing the HTTP method based on a state of the resource. Other embodiments relate to conditionally returning the operation within a return payload, for example, alone or within a feed, based on an applicability of the operation according to a state of an associated resource.

Representation/invocation of actions/functions in a hypermedia-driven environment

The subject disclosure relates to techniques for referencing a change in data utilizing a network resource locator. An interface component can receive one or more requests that are associated with a data set from a client, and send, based on the one or more requests, a network resource locator and at least one portion of the data set to the client. Further, a data service component can compute a parameter that is associated with a change of the data set, and include the parameter in the network resource locator. In other embodiments, the data service component can receive a request utilizing the network resource locator, determine the change of the data set based on the parameter, and send the change of the data set to the client.

Referencing change(s) in data utilizing a network resource locator

The subject disclosure relates to techniques for providing data experience(s) via disparate semantic annotations based on a respective user scenario. Semantic information for respective data types of data set(s) may be received. The data types may be annotated based on the semantic information to obtain respective data annotations. In response to receipt of a search query from a client, a search result that includes at least a portion of one or more data annotations is generated to be sent to the client. The search query may request performance of a search against the semantic information to obtain first semantic information associated with first data type(s) of the data types. The portion of the one or more data annotations may include the first semantic information. The first semantic information may describe operation(s) to be performed on data of at least one of the first data type(s).

Providing data experience(s) via disparate semantic annotations based on a respective user scenario

Embodiments are directed to dynamically tuning search result rankings to control how the search results are presented in a user interface and to dynamically updating search result rankings based on tuning inputs. In one scenario, a computer system receives search results with associated search result attributes. The search results are displayed within a user interface according to each search result's determined ranking. The computer system then receives a tuning input at the user interface. The tuning input indicates that a search result ranking model is to be adjusted for various specified search result attributes. Moreover, the search result ranking model determines how each search result is ranked. The computer system then dynamically updates the displayed search results as the search result ranking model is tuned for the specified search result attributes. The dynamic updating includes repositioning, adding and removing search results according to the determined ranking for each search result.

Real-time search tuning

The subject disclosure relates to annotating data based on gestures. Gestures include user interaction with a client device or client software. Gestures are tracked and associated with data. In an aspect, client context associated with a gesture is also tracked. The gestures are then employed to determine a global term to associate with the data. In an aspect, a look-up table comprising a pre-defined relationship between gestures and a global term can be employed. In another aspect, an inference component employ context information in conjunction with the tracked gestures to determine a global term to assign to data. After a global term is determined for data based on a gesture, an annotation file for the data can be created associating the data with the global term.

Gesture inferred vocabulary bindings

The subject disclosure relates to techniques for providing data experience(s) via disparate semantic annotations based on a respective user scenario. An annotation component can synthesize semantic information for respective data types of data set(s), associate the semantic information with the respective data types to obtain respective data annotations, and in response to receiving a query from a client, send at least a portion of the respective data annotations to the client. Further, a data aggregation component can aggregate the respective data annotations and at least a portion of the data set(s). Other embodiments relate to performing, via an application, operations utilizing a data type based on respective semantic annotations associated with the data type. Yet other embodiments relate to receiving external data annotation(s) and associating the external data annotation(s) with portion(s) of the respective data types to derive portion(s) of the respective semantic annotations.

The subject disclosure relates to one or more computer-implemented processes for collecting, analyzing, and employing annotations of data sources. In particular, an annotation component is configured to receive annotations of data for a data source, wherein the respective annotations comprise different associations of a global terms with the data of the data source, a data store configured to store the annotations, and an interface component configured to render the data based on the annotations in response to a request for the data. In an aspect, storing information, the data also stores descriptions of the data sources and definitions of the global terms, and the interface component determines a subset of the information in the data store based on the annotations. A method is further provided comprising receiving a global term and determining data sources that have the global term associated with the data thereof based on the information in the data store.

Data discovery and description service

Data communications are enabled to be performed between first and second computer systems without having to match data types at the first and second computer systems. A first data type is associated with a request for a resource. The request for the resource is transmitted from a first agent at the first computer system to a second agent at the second computer system. The resource is instantiated at the second computer system according to a second data type that is different from the first data type. The resource is received by the first agent from the second agent. The received resource is materialized into an instance of the first data type using the first agent.

Soft type binding for distributed systems

Techniques for exchanging data are provided herein. An 'open' data type is established on a computer system to define the structure of data. The open data type includes one or more predefined properties, and enables one or more extension properties to be optionally included. Data that is defined according to the open data type includes data values for the predefined properties, and may optionally include data values for extension properties. A second computer system may consider the extension properties to be extension properties or predefined properties of a data type known at the second computer system. In this manner, the type system that is used to exchange data between nodes need not necessarily be commonly known among the nodes, and/or may be dynamically modified, even for a particular data instance. Furthermore, queries may be performed against the data that query against the predefined properties and/or extension properties.

Open types for distributed systems

Query expressions, such as LINQ (language integrated queries) queries, are enabled to be translated to URIs (uniform resource indicators) that may be used to query data sources at REST (representational state transfer) interfaces. A compiler is configured to convert a query into an expression tree. An expression tree normalizer is configured to normalize the expression tree into a normalized expression tree. A resource bound expression tree generator is configured to transform the normalized expression tree into a resource bound expression tree. A URI generator is configured to translate the resource bound expression tree into a URI.

Translating queries to representational state transfer (REST)

Growing community of inventors

Redmond, WA, United States of America

Pablo Castro