About Developer Notes 1
|
Author: Bruce Toback
Last modified: 5 August, 1999 |
| Introduction |
| The RETS specification is highly technical, and as a formal specification, must be written so as to specify a testable set of characteristics. While such a specification is necessary in order to insure a basic level of interoperability, it can't by itself provide a uniform user experience. Nor can it provide the kind of application-oriented information that software developers need in order to make a quick start on implementation. RETS Developer Notes supplement the formal specification with explanations, examples and application information. |
| Status of Developer Notes |
In all cases, Developer Notes are subordinate to the specifications themselves. If there appears to be a conflict between something in a Developer Note and a statement in the standard, the standard prevails. However, the RETS Working Group Editors would like to be informed if you find any such conflict.
In addition, Developer Notes are recommendations only; there are no compliance tests that check for adherence to information in Developer Notes. However, we strongly recommend that you follow the application-oriented recommendations in the notes. Doing so will improve users' experience with RETS-compliant products, since adoption of a uniform set of application behaviors in some fundamental areas (for example, interpretation of times, the subject of DN-4) means that users will have fewer chances to be surprised by the results of a search or other operation. |
| Comments |
| If you have comments on a developer note, or wish to see a new developer note on some area of the standard that you think needs further explanation, please contact the Developer Note editors at devnotes@rets-wg.org. We can't promise a response, but will do our best to incorporate your comments into future notes. |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|