Specification - RETS
Specification - RETS
Specification - RETS
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
S ECTION<br />
CHAPTER 0INTRODUCTION<br />
1.1 Purpose<br />
1.2 Scope<br />
1.3 Requirements<br />
1.3.1 Required Features<br />
The Real Estate Transaction Standard (<strong>RETS</strong>) is a specification for a standard<br />
communication method between computer systems exchanging real estate information. It<br />
defines a standard interface for use by applications such as agent desktop software, IDX<br />
(Internet Data Exchange) systems, data aggregation systems, and many other systems that<br />
store, display or operate on real estate listing, sales and other data.<br />
This specification describes the Real Estate Transaction Standard communication<br />
protocol. Together with the companion XML DTDs (Document Type Definitions) listed<br />
in Appendix A, it constitutes the specification for the standard.<br />
This specification is intended to define only the minimum a product or service must do in<br />
order to be considered “compliant”. This specification is extensible and nothing in the<br />
specification precludes a vendor from adding data or functionality over and above that<br />
detailed here. However, when a function is provided or a data element is stored by a<br />
compliant system, it must offer access to the function or mechanism in a way that<br />
complies with the specification in order to be considered compliant.<br />
This specification uses the same words as RFC 1123 [1] for defining the significance of<br />
each particular requirement. These words are:<br />
MUST<br />
This word or the adjective "required" means that the item is an<br />
absolute requirement of the specification. A feature that the<br />
specification states MUST be implemented is required in an<br />
implementation in order to be considered compliant.<br />
Version 1.7.2 1-1