Abstract: Various arrangements for maintaining a listing of candidate resources for a resource request are presented. A resource request may be received. A plurality of resource records may be searched using a first set of search criteria to identify a subset of resource records from the plurality of resource records. Each record of the plurality of resource records may indicate qualifications of a corresponding resource. Each record of the plurality of resource records may also correspond to a person. A selection of candidate resource records may be received from the subset of resource records. A listing of candidate resources that indicates each candidate resource selected by the user may be presented to the user. The listing of candidate resources that indicate each candidate resource selected by the user may be linked to the resource request, such that the listing of candidate resources is presented when the resource request is accessed.

Abstract: A personal messaging application programming interface can be utilized by a developer in order to add groupware functionality to an application. The interface can include various schemas and providers that allow the schemas to connect to a collaboration server which provides the groupware functionality. The schemas can further include item and container classes and can extend other schemas so as to provide functionality that is more specific to the collaboration server. The items and containers can represent various entities on the collaboration server. The providers can use stubs in order to create connections to the collaboration server and can implement the schema hierarchy so as to map the functionality defined by the schema into various core calls on the collaboration server.

Abstract: A personal messaging application programming interface can be utilized by a developer in order to add groupware functionality to an application. The interface can include various schemas and providers that allow the schemas to connect to a collaboration server which provides the groupware functionality. The schemas can further include item and container classes and can extend other schemas so as to provide functionality that is more specific to the collaboration server. The items and containers can represent various entities on the collaboration server. The providers can use stubs in order to create connections to the collaboration server and can implement the schema hierarchy so as to map the functionality defined by the schema into various core calls on the collaboration server.