Search

RETS Change Proposal 30: Hotsheet
Author: Maggi Diaz
Organization: WyldFyre
Telephone: (408)369-8900
Address: 900 East Hamilton Ave., Suite 500, Campbell, CA 95008
Email: maggie@wyldfyre.com
Status: Proposal
Date: 01/20/2003
Proposal Version: 1.5
1. Synopsis
This change proposal is to (1) add Hotsheet as another Resource in the metadata structure, (2) add Hotsheet as another Search Type, and (3) add Hotsheet to the RETS DTD.
2. Rationale
RETS vendors need a standard to implement Hotsheet that is currently not in RETS
3. Proposal
3a. Include Hotsheet as another Search Type in Chapter 7, Section 7.1 Search Types, and describe as follows:

Hotsheet A Hotsheet Search is a search against a property class database/table.

3b. Include Hotsheet as another Resource in Section 11.2.2. Resource, Table 11-1 Well-Known Resource Names as follows:
Resource NamePurpose
HotsheetA resource that contains information about property listings with price and status changes from a resource property class table.

3c. Include Hotsheet in Real Estate Data (REData) Transaction DTD, Chapter 1, Section 1.4.8 Packaging Elements, as follows:

    REData
    REProperties?
    ResidentialProperty*
    CommonInterest*
    LotsAndLand*
    MultiFamily*
    TaxData*
    REOffices?
    REOffice+
    REAgents?
    REAgent+
    REOfficeRosters?
    REOfficeRoster+
    REActivities?
    Activity+
    REProspects?
    Prospect+
    REPublicRecords?
    RETax+
    REHistories?
    REPropHistory+
    REPropEntry+
    REHotsheet?
    REHotsheetRecord+

3d. Include Hotsheet in Real Estate Data (REData) Transaction DTD, Section 1.5 Comments on Field Usage, as follows:

The ListingID is the intended container for the data in the KeyField of the Hotsheet Resource as defined in the Metadata.

3e. Include Hotsheet in Real Estate Data (REData) Transaction DTD, Chapter 2 DTD, as follows:

<!-- PACKAGING ELEMENTS -->
<!ELEMENT REHotsheet (REHotsheetRecord+) >

3f. Include Hotsheet in the Real Estate Data (REData) Transaction DTD, Chapter 2 DTD, as follows:

Note1: The REHotsheetRecord utilizes the 'PropertyRecord' element defined in the 'Listing History' section. That element should be moved from the 'Listing History' section to the general 'Compound Elements' section.

Note2: The REHotsheetRecord utilizes the'ChangeType' element defined in the 'Listing History' section. That element should be modified as shown below and moved from the 'Listing History' section to the general 'Compound Elements' section.

    <!ELEMENT ChangeType (#PCDATA) >
    <!ATTLIST ChangeType (#PCDATA) >
    PriceChange (Increase | Decrease | None)
    StatusChange (Yes | No)
    System (Yes | No) "No" >

    <!-- Hotsheet Elements -->
    <!ELEMENT PreviousListPrice (#PCDATA) >
    <!ATTLIST PreviousListPrice (#PCDATA) >
    Type (INTEGER | FLOAT) "INTEGER"
    CurrencyCode CDATA "USD" >

    <!ELEMENT PreviousStatus (#PCDATA) >
    <!ATTLIST PreviousStatus (#PCDATA) >
    Status (Active | Closed | Expired | OffMarket | Pending) >

    <!-- Compound Hotsheet Elements -->
    <!ELEMENT REHotsheetRecord (ListingID, ChangeType, PreviousListPrice?,
    PreviousStatus?, PropertyRecord?, ModificationTimestamp?)>

3g. Include Hotsheet in Real Estate Data (REData) Transaction DTD, Chapter 3 Sample Data, as follows:

    3.7 Hotsheet
    <REData>
    <REHotsheet>
    <REHotsheetRecord>
    <ListingID>4839424</ListingID>
    <ChangeType PriceChange="Increase" StatusChange= "No">PriceIncrease</ChangeType>
    <PreviousListPrice>489000</PreviousListPrice>
    <PreviousStatus Status="Active">New</PreviousStatus>
    <PropertyRecord>
    <ResidentialProperty>
    <Listing>
    <StreetAddress>
    <StreetNumber>720</StreetNumber>
    <StreetDirPrefix>E</StreetDirPrefix>
    <StreetName>Vineyard</StreetName>
    <StreetSuffix>Ln</StreetSuffix>
    </StreetAddress>
    <ListingData>
    <ListPrice>479000</ListPrice>
    </ListingData>
    <SalesData>
    <ClosePrice>0</ClosePrice>
    </SalesData>
    <MLSInformation>
    <ListingStatus Status="Active">Active</ListingStatus>
    <StatusChangeDate>2003-01-31T8:00:00</StatusChangeDate>
    <ModificationTimestamp>2003-01-31T15:25:40.897</ModificationTimestamp>
    </Listing>
    </ResidentialProperty>
    </PropertyRecord>
    <ModificationTimestamp>2003-01T15:25:40.897</ModificationTimestamp>
    </REHotsheetRecord>
    </REHotsheet>
    </REData>

4. Development Impact
This proposal adds another Resource and Search Type in RETS. There should not be an impact on RETS clients and servers.

This proposal is an enhancement on the specification and should not impact current or future RETS client and server implementations.

5. Compatibility
None.
6. Proof/Need of Concept Examples
None.