RCP 92 - RESO Payload Transport-Level Metadata Support

Synopsis

Add to Section 7.6 an example response body for Payload=<RESO schema name> and modify the rets-xml-search-response-1_8_0.xsd to provide responses for each of the adopted RESO schemas.

Rationale

RCP 76 added a GetPayloadList Transaction to the standard that permits the use of RESO schema as a response format on a Search Transaction.

RCP 76 is silent on the response body format that using this argument will produce. This change proposal resolves that question.

Proposal

Correct the structure of Section 7.6 Search Response Body Format to place the elements with the appropriate format type and place the common elements at the bottom of the section.

Modify Section 7.6 to add an example of the response body when the Payload=<RESO Schema Name> is used on a SearchTransaction.

<new text>

The body of the search response has the following format when replying to a payload request for a RESO schema:
<?xml version="1.0" ?>
[ doctype ]
<RETS 1*SP ReplyCode= quoted-reply-code 1*SP ReplyText= quoted-string *SP >
[ count-tag ]
*({{ RESO-data-record )}}
[ max-row-tag ]
[<RETS-STATUS [rcpdropbox:1*SP ReplyCode= quoted-end-reply-code 1*SP
ReplyText= quoted-string *SP]/>]
</RETS> CRLF

RESO-data-record ::= <A record structure as defined in the rets-xml-search-response-1_8_0.xsd document>

</new text>

Update the rets-xml-search-response-1_8_0.xsd to provide for the response of each of the root RESO Schema: Listings, Media, Members, Offices, Properties, PublicRecords, Syndication, Teams.

Impact

None.

Compatibility

Compatible with 1.8