Removed ProcInst. Removed ProcessSynchronous, will be passed in by TransportHandler. Moved ProcessAsGroup down to JobPositionPostings element. Removed DeliveryReceiptRequest. Note: Do not use attributeFormDefault="qualified" due to bugs in XML Spy. Attributes turned on individually. The From element identifies the entity that produced the message. An optional credential can be supplied when password schemes are employed. The To element identifies the intended target of the message. PartyId provides the Id of a to or from party. Types include "duns", which is a standard organizational identifier or "organization" which is a locally (Monster) meaningful name of a partner. uri is the default. Credentials is an item used to establish the identity of the From party. The most common type is expected to be password. The MessageData element contains items relevant to processing the message. The MessageId element uniquely identifies the message. It is recommended that this identifier by globally unique. The From party should utilize some scheme combining a unique identifier for them as an entity and the message. Alternatively, a Microsoft-esque GUID generator could be employed. MessageId is not a domain specific unique identifier (like a resume id) but instead is used to correlate request and response and to ensure that the same message isn't processed multiple times. The RefToMessageId element contains the MessageId of a previous message. This field is provides the means to correlate a DeliveryReceipt or a ProcessingReceipt with the original Message. The Timestamp element is the time at which the message element was created, formatted as an XML Schema timeInstant. The TimeToLive element is the time by which the message must be processed, formatted as an XML Schema timeInstant. uniquely identifies the message. It is recommended that this identifier is globally unique. MessageId is not a domain-specific unique identifier but instead is used to correlate request and response and to ensure that the same message isn't processed multiple times. the time at which the message header was created, formatted as an XML schema dateTime. contains the MessageId of a previous message. This field provides the means to correlate a DeliveryReceipt or a ProcessingReceipt with the original Message. A ReceiptRequestType element is used by the From party to request a Receipt. Address is used by the From party to define where a receipt should be sent. The value of the element can be empty, in that case it directs the system the respond to the pre-defined address for that protocol type. Additionally, the value may be ignored in favor of the value defined in the profile. If file is specified, the value of the address should be left empty and will be ignored. file means to place the receipt in the local file system at the location defined in the partners profile. This is most often used to accomodate customers who FTP content to us and then utilize FTP to poll a local directory for status.