RETS Change Proposal 19: Metadata-Table ShortName
|
| Author: Brita Brodin |
| Organization: WyldFyre Technologies |
| Telephone: (408)369-8900 |
| Address: |
| Email: brita@wyldfyre.com |
| Status: Proposal |
| Date: 12/09/2002 |
| Proposal Version: 1.0 |
| 1. Synopsis |
| The Metadata-Table ShortName field currently is described as “An abbreviated field name that is also localizable and human-readable. Use of this field is implementation-defined”. The first sentence should be modified to read “An abbreviated field name that is also localizable, human-readable, and user-friendly”. |
| 2. Rationale |
| Certain RETS vendor(s) currently provide values such as “AX0001” as the ShortName for a field such as List Price. The vendor’s argument is that the ShortName provided is “human-readable”. Thus, it is requested that the description be further enhanced to indicate that the value provided should be user-friendly as well. |
| 3. Proposal |
| In Table 11-4 the first sentence in the Description column for the ShortName field should read:
“An abbreviated field name that is also localizable, human-readable, and user-friendly. This is the value that may be used to define column headings”. |
| 4. Development Impact |
| RETS Metadata generation methodologies may need to be altered. |
| 5. Compatibility |
| RETS 1.5 Servers would be required to adhere to the uniqueness rule to be compatible. |
| 6. Proof/Need of Concept Examples |
| None. |