| RETS Change Proposal 57: Standard Names Metadata |
| Author: Sergio Del Rio |
| Organization: Templates 4 Business, Inc. |
| Telephone: (604)529-1544 |
| Address: |
| Email: sergio.del.rio@t4bi.com |
| Status: Proposal |
| Date: 03/02/2004 |
| Proposal Version: 1.8 |
| 1. Synopsis |
| This change request will allow servers to provide Metadata for Standard Names in addition to System Names. |
| 2. Rationale |
| The Data Dictionary Working Group is making good progress on defining the full set of Standard Names that RETS should support. In this process, we felt that it would be very beneficial if clients were given the ability to get metadata for the set of Standard Names that a server supports.
This would allow clients to be more flexible in the way that they handle formulating queries and in how they present data to the end users. |
| 3. Proposal |
| This proposal affects GetMetadata Transaction as follows.
3.1 Additional Optional Request Argument (Section 12.3)
StandardNames
Metadata may be output for either standard name or system names. If the client chooses to use standard names, it MUST indicate this using StandardNames argument.
StandardNames ::= 0 | 1
If this entry is set to (“0”) or is not present, the field names and other information returned by the Metadata request are for the SystemNames. If this entry is set to (“1”), then the field names and other information returned by the Metadata request are for the StandardNames. |
| 4. Development Impact |
| Development impact depends on each current RETS client and server implementations, but should not have any impact on future RETS client and server implementations. Each existing RETS server and client, prior to passing of this proposal, have the option to change accordingly to be RETS compliant. Future RETS server and client implementation after approval of RETS 1.8 MUST follow RETS 1.8 standard. |
| 5. Compatibility |
| Servers that do not have metadata for standard names remain compatible to the existing RETS 1.7 specification and can continue to function and be considered RETS 1.8 compatible. It is not mandatory for a server to send back any metadata for Standard Names. If a server does not provide this information, a response code of 20509 MUST be returned in response to a request for it. |
| 6. Proof/Need of Concept Examples |
| None. |