Microsoft Technology Licensing, LLC

Michael Justin Flasko

Pablo Castro

Jason Duane Clark

Lance Olson

Michael Pizzo

Siddharth Jayadevan

Andrew Conrad

Alex James

Amir Netz

Giovanni Moises Della-Libera

Kevin Grealish

David John Nettleton

Andrew James Peacock

Mark Wade Heninger

Christina Storm

Chiu Ying Cheung

Cheryl Couris

Sonia P Carlson

Paula M Bach

Pratik Patel

Subramanian Muralidhar

Alexander Douglas James

Colin Joseph Meek

Marcelo Lopez Ruiz

Simon Cavanagh

Mark Ashton

Job execution can be scheduled and monitored. Execution of a job results in generation of one or more data slices, which can be consumed as input by one or more related jobs. Data slices can be presented in an interactive view. Selection of a data slice in the view can trigger automatic identification of related data slices based on dependencies between data slices. Each data slice can also include and be presented with a status indicating the availability of corresponding data, such as pending, ready, or failed. Furthermore, selection of a data slice that failed to generate successfully can trigger identification of related data slices that failed or are predicted to fail to generate successfully.

Job scheduling and monitoring in a distributed computing environment

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

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

A view of data transformation jobs can be presented by way of a user interface. Related jobs can subsequently be identified automatically after a job is selected based on data dependencies between jobs. Execution status can also be determined and presented such that successful and failed execution of jobs, for example, can be differentiated. Furthermore, selection of a job run that failed to execute successfully can trigger identification of related jobs runs that failed or are predicted to fail to execute successfully.

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

Duvall, WA, United States of America

Michael Justin Flasko