This resource supports translations.

	Field name	Description
#	DisplayName
#	EntityEventSequence
#	LegacyODataValue	The name of the resource the field belongs to. This will be a RESO Standard Name, such as “Property”, but may also be a non-standard local resource name.
#	LookupKey	The key used to uniquely identify the lookup entry.
#	LookupName	The name of the enumeration. This is the LookupField in the adopted Data Dictionary spreadsheet. It is called a “LookupName” in this proposal because more than one field can have a given lookup, so it refers to the name of the lookup rather than a given field. For example, Listing with CountyOrParish and Office with OfficeCountyOrParish having the same CountyOrParish LookupName. This MUST match the Data Dictionary definition for in cases where the lookup is defined. Vendors MAY add their own enumerations otherwise. The LookupName a given field uses is required to be annotated at the field level in the OData XML Metadata, as outlined later in this proposal.
#	LookupValue	The human-friendly display name the data consumer receives in the payload and uses in queries. This may be a local name or synonym for a given RESO Data Dictionary lookup item.
#	ModificationTimestamp	The timestamp for when the enumeration value was last modified. This is used to help rebuild caches when metadata items change so consumers don’t have to re-pull and reprocess the entire set of metadata when only a small number of changes have been made.
#	StandardLookupValue	The Data Dictionary LookupDisplayName of the enumerated value. This field is required when the LookupValue for a given item corresponds to a RESO standard value, meaning a standard lookup display name, known synonym, local name or translation of that value. Local lookups may omit this value if they don’t correspond to an existing RESO standard lookup value.
#	Translations	This is a navigation field.