The Application Design Guidelines presented here are the required and best practices for building an effective application with the Windows Live™ Messenger Library.
Contact
A person for whom the user has subscribed to presence updates.
Display Name
A name that a user presents to his or her contacts.
Pending Contact
A person who has subscribed to the user and is not on the user’s contact list.
Personal Message
An expressive message that a user presents to his or her contacts.
Presence
The collection of data exposed by a user to his or her contacts. Presence is comprised of status, display name, personal message, and other content.
Status
The basic presence state indicating a user's availability. Potential values include:
Sign-in Control
The visual element rendered within the application that enables the user to sign in to the Windows Live Messenger Library.
User
The person signing in to the Messenger Service via Windows Live Messenger Library.
The following key words are to be interpreted as described in RFC 2119: Must, Must Not, Required, Shall, Shall Not, Should, Should Not, Recommended, May, and Optional.
The following sections outline required and recommended guidelines for all Messenger Library applications.