Microsoft Technology Licensing, LLC

Andrew G Bybee

Christopher Andrew Evans

Pritvinath Obla

Chad C Neff

Leslie S Yeh

Balan Sethu Raman

Timothy P McKee

Gregory Darrell Fee

Tony Edward Schreiner

Anil Kumar Nori

Walter R Smith

Jingyang Xu

John M Hawkins

Aaron Ross Goldfeder

Derik Bjorn Stenerson

Shashi Ranjan

Viresh Ramdatmisier

Jeremiah S Epling

Joseph T Farro

Jamie Lee Cool

Sergey A Khorun

Denis Seniuc

Kalmadi Santhosh Rao

Users are enabled to quickly and easily associate records representing entities such as themselves, other users, contacts, accounts, teams/groups, and similar ones employing a record of the association and assign each entity a role or other attributes as a part of this association. Relationship records and attributes preserving entity association information allow teamwork, communication, and collaboration for effective management of business processes. The records and attributes also enable visualization and facilitate deeper understanding of the relationships between people, data, and business processes.

Creating ad hoc relationships between entities

Described is a mechanism for collectively evaluating security risks associated with loading an application. A hosting environment associated with loading the application invokes a trust manager to evaluate the security risks. The trust manager invokes a plurality of trust evaluators, where each trust evaluator is responsible for analyzing and assessing a different security risk. Upon completion of each security risk evaluation, results of those individual security risk evaluations are returned to the trust manager. The trust manager aggregates the variety of security risk evaluation results and makes a security determination based on the aggregated evaluation results. That determination may be to move forward with loading the application, to block the load of the application, or perhaps to prompt the user for a decision about whether to move forward with the load.

Mechanism for evaluating security risks

A file system that does not conflate item lifetime with the item's inclusion in an organizational structure of the file system is described herein. In addition, the file system's organizational structure is not limited to directory trees, but instead may use any directed acyclic graph (DAG). Items, once stored into the file system, may be maintained until affirmatively deleted by a client of the file system, regardless of whether the item is part of a DAG or not. Items may be placed in file regions, which are conceptual workspaces for a client to control item lifetime and to organize items into any DAG structure of the user's choosing. Items may be concurrently stored in multiple DAGs, and each file region may have one or more independent DAGs. An item's placement in a DAG may also be used to govern file properties such as namespace, security, privacy, and read/write attributes.

Computer file system

The present invention relates to a system and method for providing dynamic wizard interfaces to end users. In one embodiment, a client device retrieves a container encapsulating a number of packages utilizing a self-describing data format from a remote server. A wizard engine on the client device interprets the container and packages to produce a wizard interface. Preferably, the present invention utilizes a compatible data structure for receiving, saving, and transmitting captured information regarding the wizard interface.

Dynamic wizard interface system and method

XGL and dynamic accessibility system and method

XGL and multi-platform user interface engine

Growing community of inventors

Redmond, WA, United States of America

Andrew G Bybee