RCP 88 - Revised StandardNames document

ATTACHEMENT: RETS_Standard_Names_Worksheet_r3.6.xls

	Name	Size	Creator (Last Modifier)	Creation Date	Last Mod Date	Comment
	RETS Standard Names Worksheet r3.6.xls	380 kB	Paul Stusiak	Feb 04, 2010	Feb 04, 2010		View

Synopsis

The StandardNames document has been revised to reflect current usage and restructured to provide additional representations to simplify use.

Rationale

The existing StandardNames document has not met the needs of the community. The implementation and use of the fields has been hampered by the organization of the data dictionary. The people responsible for creating the mapping between local names and the StandardNames have found it challenging to associate the local name with the StandardName. The people using the StandardNames have found it challenging because the names may not have been expressed in the system during the implementation phase or may have a name that does not match that of local use.

Proposal

The Data and Schema Workgroup undertook to work with operators to identify important fields, describe meanings for those fields and present those fields in a form more like that of a listing input form.

From this work, a new list of (Resource=Property) StandardName fields has been created that better matches the information and naming styles of RETS and the participants.

As well, some changes to the well-known Class names of Table 11-10, StandardName. The summary changes are: add RentLease, Mobile and Farm as well-known names for property classes.

Additional fields have been added where necessary.

Unused fields have been removed.

These fields have been assigned semantic meaning, where possible, and provided with some organization to make data points more obvious to both the implementation and use communities.

The proposal is to adopt a new list of StandardNames, replacing the existing standard names document. The list of StandardNames is provided in the document StandardNames-2010-04, attached to this change proposal.

Please also see the change proposal "RCP 89, Resource=StandardName" for a proposed solution to the problem of StandardNames version.

Impact

In systems that have implemented the new StandardNames list, existing applications that depend on the old StandardNames list may not behave as expected.

Compatibility

This is intended to be for all servers. A backward compatibility issue exists since there is no way to tell what the version of standard names is provided in previous editions.