Home
Documents
Resources
Compliance
Meetings
Mailing Lists
Workgroups
Compliance
Data Dictionary
Marketing
Media
Metadata
Transport
Update
Comments
Links
Outstanding Change Proposals
| Number | Name | Submitted | Status | Reference |
| 057 | Standard Names Metadata | 3/2/04 | Open | |
| 053 | Enhancements to Upload Transaction | 11/21/03 | Open | |
| 050 | Simplify GetMetadata | 11/21/03 | Withdrawn by Author | 12/3/03 |
| 049 | Remove Multipart from GetObject | 11/21/03 | Postponed | December 2003 meeting notes. |
| 048 | Compact Format Simplification | 11/19/03 | Deferred | December 2003 meeting notes. |
| 040 | Object Upload | 9/29/03 | Deferred | December 2003 meeting notes. |
| 039 | GetObject Changes | 8/7/03 | Discussed | August 2003 meeting notes. |
| 038 | Transmission of Field Security Information | 8/1/03 | Withdrawn | August 2003 meeting notes. |
| 037 | Update Transaction Validation | 7/24/03 | Discussed | August 2003 meeting notes. |
| 030 | Hotsheet | 1/20/03 | Open | April 2003 meeting notes. February 2003 meeting notes. |
| 029 | Distributed Database Enhancements | 2/13/03 | Open | February 2003 meeting notes. |
| 001 | Transmitting Structure Information | 12/25/01 | Resubmitted by the author | June 2002 meeting notes. |
Informal comments on the standards should be sent to the rets-dev mailing list. To subscribe to this list, see the lists page; you must be subscribed in order to post to the list. Working group members routinely monitor the list traffic and should be able to respond to questions or comments within a day or so.
Formal change proposals for RETS should be sent to [email protected]. To be considered for publication, the comment must contain the following information:
Your name
The name of your organization
A mailing address
Optionally, a telephone number and email address
A description of the proposed change, including the section of the document to be changed, and any new proposed wording. If the proposal is for changes to the DTD, the precise meaning of any new elements should be specified.
An estimate of the complexity of implementing the proposed change.
An estimate of the effect of the change on interoperability with implementations that have not yet incorporated the proposed change.
An email template to assist in preparing formal comments will be available on this page in the near future. There will also be a special form for registration of new well-known resource names, as described in the standard.
Once a proposal has met the requirements for publication, it will be available for public comment through this page. In addition, a digest of formal change proposals available for review is sent periodically to the rets-announce mailing list