This schema outlines the structure of a response document published by a Partner for processing by Point2. Every response document received by Point2 is checked for validity. A valid document is one that is formally valid according to this XML schema and meets the additional requirements contained in the xs:documentation. If a Partner fails to deliver a valid response document once every 72 hours Point2 will stop updating their feed. A Partner can request that their feed be updated regularily once again using the Point2 Platform web site at http://platform.point2.com/account. Point2's validation will check that a timezone is specified. Point2's validation will check that either ErrorMessage or Link is provided. Point2's validation will check that this ListingID corresponds to a listing contained in the most recent data feed. A human-readable error message. A machine-readable error code. Point2 will periodically check Links provided here to ensure they respond to an HTTP GET with a nonblank body and response code of 200. Our crawler uses the agent string "Point2 Platform PublishingReport Validator" and respects 301 and 302 redirects. Bad Request - This error occurs if the Order was incorrectly formatted, or otherwise uninterperatable. Insufficient Data - The listing data sent did not include some field that is required (zipcode, state, etc.) Internal Server Error - An unknown error occured while processing this listing. Unknown Geographic Location - The listing is listed in a location that is not known to the receiving system. No coverage for specified area - The listing is lited in a location that is not supported by the receiving system. Listing Type Not Supported - The listing type is not supported by the receiving system. Listing Status Not Supported - The listing status is not supported by the receiving system. Listing Duplicate - The listing is a duplicate of a listing already present in the receiver's system. The sender's listing data was not imported.