Search

RETS Change Proposal 38: Transmission of Field Security Information
Author: Bruce Toback
Organization: OPT, Inc.
Telephone: (800)858-4507
Address: 11801 N. Tatum Blvd. Ste. 142, Phoenix AZ 85028
Email: btoback@optc.com
Status: Proposal
Date: 08/01/2003
Proposal Version: 1.0
1. Synopsis
New table-level metadata fields are added in order to communicate public visibility requirements to replicating servers.
2. Rationale
RETS is currently being used to replicate data, and it is expected that this use will expand in the future. Currently, there is no way for a server using RETS to retrieve data from another server to know what level of protection to apply to various data fields. A mechanism to supply this information is necessary in order to help avoid accidental exposure of sensitive information on public web sites or to public search services.
3. Proposal
3.1. Specification Changes

Extend the METADATA-TABLE structure to include one additional field, defined as follows:

NameValuesMeaning
ProtectionPublicNo special protection is required; the field may be displayed in public settings and freely transmitted downstream.
MLSThe field should not be displayed or transmitted without a valid agent login.
PrivateThe field should not be displayed or transmitted at all; it is intended for use only by system internal processes.

A "valid agent login" means that the system receiving and retransmitting and/or displaying the data has satisfied itself that the viewer has agreed to abide by the rules of the MLS or operating association.

End-user client software is not required to process this field in any way. However, such software MAY use the field in assisting users with construction of reports that may be displayed to the public.

4. Development Impact
Minimal; the field is optional and advisory for purposes of standards compliance.
5. Compatibility
No compatibility issues are expected.
6. Proof/Need of Concept Examples
None.