Kim S Cameron

6944626, Sep 13, 2005

Nov 26, 2001

09/995415

Kim Cameron - Bellevue WA, US
Stewart P. MacLeod - Woodinville WA, US
George G. Robertson - Seattle WA, US
James H. Booth - Issaquah WA, US
Luc Clement - Sammamish WA, US

Microsoft Corp. - Redmond WA

G06F017/00

707103R, 707100, 707102

The described arrangements and procedures provide for interfacing (e. g. , managing, presenting, etc. ) with complex and often elastic inter-object relationships between objects in a data polyarchy. Specifically, a schema is dynamically generated by a server to represent multiple hierarchies of inter-object relationships between objects in a data polyarchy. The schema indicates or lists each attribute or element of interest in the data polyarchy. The schema further indicates any of one or more dimensions of inter-object relationships within which objects that comprise at least a subset of the listed the elements of interest participate. Thus, the schema indicates how to interface with the data polyarchy, which represents multiple hierarchies of inter-object relationships based on the values of attributes of the represented objects.

6952704, Oct 4, 2005

Nov 26, 2001

09/995001

Stewart P. MacLeod - Woodinville WA, US
James H. Booth - Issaquah WA, US
Kim Cameron - Bellevue WA, US
Jonathan A. Fischer - Carnation WA, US
Max L. Benson - Redmond WA, US
Felix Wong - Bellevue WA, US
Robert Dan Thompson IV - Fort Worth TX, US
Hilal Al-Hilali - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F017/30

707103R, 707103 Y, 707103, 707103 Z, 7071041

The described arrangements and procedures provide a directory schema with object classes that have flexible attributes. This means that attributes can be extended independent of modifications to the directory schema. Specifically, an object instance of a content class described in the directory schema is instantiated. The content class includes a flexible attribute having a data type. A property is assigned to the attribute. The property is any combination of an operational and data providing property. The property is independent of the attribute's data type. Thus, without modifying the directory schema, multiple instances of the same object class can have attributes that provide completely different data types and completely different data operations.

6957230, Oct 18, 2005

Nov 26, 2001

09/995414

Kim Cameron - Bellevue WA, US
George G. Robertson - Seattle WA, US
Mark R. Brown - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F017/30

707103R, 707101, 707102

The described arrangements and procedures dynamically generate a data polyarchy from information received from a data store (e. g. , a directory or database). The data polyarchy represents multiple hierarchies of inter-object relationships based on values of attributes of the objects. These multiple hierarchies are generated and represented in a manner that is independent of object naming and predetermined hierarchical data structures.

7051043, May 23, 2006

Oct 18, 2004

10/967742

Kim Cameron - Bellevue WA, US
Stewart P. MacLeod - Woodinville WA, US
George G. Robertson - Seattle WA, US
James H. Booth - Issaquah WA, US
Luc Clement - Sammamish WA, US

Microsoft Corporation - Redmond WA

G06F 17/30

707103R, 707100

Systems and methods for dynamically generating a schema representing multiple hierarchies of inter-object relationships are described. In one aspect, a polyarchical query language data structure includes first, second, and third data fields. The first data field is used to specify a particular schema for presenting or managing a plurality of objects in a data polyarchy based on values of attributes in the objects. The second data field is to indicate an attribute of interest. The third data field indicates how one or more objects that include the attribute of interest are to be presented or managed with respect to one or more participating dimensions of inter-object relationships based on the schema.

7181472, Feb 20, 2007

Oct 23, 2003

10/693175

Kim Cameron - Bellevue WA, US
Don Hacherl - North Bend WA, US

Microsoft Corporation - Redmond WA

G06F 17/30

707201, 707 10, 707200, 709231

An identity system and method that stores identity information related to different principals and stores the identities on different or disparate systems such that the different systems can use the identities. A synchronization process synchronizes identity information and rules based on identity information between a primary computer system and a disparate secondary computer system. Accordingly, the secondary computer system has a representative database of identity information following receipt of the converted information, wherein the representative database is representative of a primary database of identity information stored on the primary computer system. In order to synchronize a conversion may take place. The conversion process may be performed by a dedicated process designed for the secondary system. Alternatively, the conversion is performed by a generalized process using mapping tables designed to convert identity information into multiple different formats.

7200608, Apr 3, 2007

Oct 23, 2003

10/693097

Matthew Rimer - Redmond WA, US
Andy Harjanto - Sammamish WA, US
Kim Cameron - Bellevue WA, US
Don Hacherl - North Bend WA, US
Murli Satagopan - Sammamish WA, US
Nitin Karmarkar - Bellevue WA, US

Microsoft Corporation - Redmond WA

G06F 17/00
G06F 15/173

707102, 707101, 707103 R, 7071041, 709224

In the present invention, data relating to principals known to a computer system is centrally stored and objects having a standardized principal application programming interface (API) for finding, managing and accessing that data is provided to applications in lieu of having the applications independently store the principal data. The present invention eliminates the need for each application to create duplicate principal data. It also ensures that principal data are consistent throughout the applications on the computer system. In addition, the present invention allows any application with objects having the principal API to manage and change the principal data making such principal data easy to update. The principal API includes methods to find principals based on an identity reference to a principal or an identity claim that uniquely identifies the principal on computer system.

7231400, Jun 12, 2007

May 13, 2004

10/846368

Kim Cameron - Bellevue WA, US
George G. Robertson - Seattle WA, US
Mark R. Brown - Seattle WA, US

Microsoft Corporation - Redmond WA

G06F 7/00
G06F 17/00

707103Z, 707103 R

Systems and methods are presented to dynamically generate multiple hierarchies of inter-object relationships based on object attribute values. In one aspect, a data structure includes a first virtual object data field to represent a first object of multiple objects in a data store. A second virtual object data field represents a second object of the multiple objects. Attributes of the first object intersect with attributes of the second object to form multiple hierarchies of inter-object relationships.

7240073, Jul 3, 2007

May 8, 2003

10/435708

Max L. Benson - Redmond WA, US
Michael Jerger - Redmond WA, US
Edward H. Wayt - Seattle WA, US
Kenneth Mark - Kirkland WA, US
Kim Cameron - Bellevue WA, US
Matthias Leibmann - Woodinville WA, US
Jing Wu - Sammamish WA, US

Microsoft Corporation - Redmond WA

G06F 7/00
G06F 17/00

707103R, 707101, 707102

Subject matter includes exemplary flexible rules for defining an information management process, for example a process that manages information being transferred between databases or with respect to an exemplary metadirectory. The flexible rules have inherent logic to define part of an information management action or a database structure and perform a call out for custom logic. The custom logic performs or defines another part of the information management action or database structure. Besides the exemplary flexible rules, the subject matter describes exemplary identity information management processes, engines, and related methods.