All Schema files in the OpenTravel Alliance specification are made available according to the terms defined by the OpenTravel License Agreement at http://www.opentravel.org/Specifications/Default.aspx. This message is used to request a business rate for a specific account for one or many locations. Used to identify the sender of the request. If the sender is an intermediary, this may additionally be used to identify the company on whose behalf the information is being requested. A collection of TransientRFP_RequestSegment. This allows for the RFP to be sent to multiple properties. A collection of RequestedInfo elements. Used to specify what information should be returned in the response. A collection of specific information being requested. Used to request specific information within the response. When true, indicates the data requested by the Name attribute or Text element is mandatory. Used to identify information to be included in the response. Refer to OpenTravel Code List Requested Info Code Category (RQC) code list. When true, all response data should be sent in a single file and when false, the response for each RequestedInfoCode should be in a separate file. Typically used when the response is requested in electronic format. Provides the details of the data being requested. A collection of ContactInfo elements. This may be used for who this is from as well as who this is going to. May be used in conjuction with the HotelName attribute found in TransientRFP_RequestSegment to specify a particular hotel, or simply to pass hotel address information. Used to specify information that is specific to the requesting account. This is the potential number of room nights that the requestor believes they will produce for the single specified hotel. This is the potential number of room nights that the requestor believes they will produce for the specified city. When true, this means hotels that weren't in the original request can offer their own negotiated rate for this specific account. Used to specify from who the requestor would like an RFP. This may be a specific property, all the properties for a specific brand and chain in a specific city or other combinations of data. This is an intermediary specific code used to identify a specific hotel (i.e., RFPExpress uses a proprietary code that could be passed here). A collection of Comment elements. May be used to send textual information regarding the request such as questions, legal text, special requests, etc. This is used to identify the format in which the response should return the specific requested data. This defines how the detailed response to the RFP should be communicated (e.g., http, e-mail, telephone). Refer to OpenTravel Code List Distribution Type (DTB). This defines the format in which the response to the RFP should be communicated (e.g., XML, Excel, hardcopy). Refer to OpenTravel Code List Format Type (FMT). The date the requestor requires a response. The date the requestor intends to make a decision. This specifies the intended length of time to which this request applies. The intended originating contract year or year and month The ID is used to identify the request.