Definition Type: ComplexType
Name: MLSAreaType
Namespace: http://rets.org/xsd/RETSCommons/2007-08
Containing Schema: RETSCommons.xsd
Abstract
Documentation:
A Marketing area descriptor for a listing, consisting of optional major, secondary and minor names. These names may be area (region/zone), a county, neighborhood, city, or combination of geographic areas which may have no legal standing but defines a small region in terms well-known by users of the information. The schema does not enforce data-mapping order but common usage is that data fields are mapped in order of major, secondary and minor. Systems that do not capture information for any of these elements should suppress the field to element mapping using the order described above. For example, if a system only has a single piece of data for marketing area, they should map this to the major area. If a system has two pieces of information, the mapping should be to the major and secondary area. In both examples, no data is mapped to the minor area and it would not be expressed in the response document.
Collapse XSD Schema Diagram:
Drilldown into MinorArea in schema retscommons_xsd Drilldown into SecondaryArea in schema retscommons_xsd Drilldown into MajorArea in schema retscommons_xsdXSD Diagram of MLSAreaType in schema retscommons_xsd (Real Estate Transaction Standard (RETS))
Collapse XSD Schema Code:
<xs:complexType name="MLSAreaType">
    <xs:annotation>
        <xs:documentation>
				A Marketing area descriptor for a listing, consisting
				of optional major, secondary and minor names.
				These names may be area (region/zone), a county,
				neighborhood, city, or combination of geographic
				areas which may have no legal standing but
				defines a small region in terms well-known
				by users of the information.
				
				The schema does not enforce data-mapping order
				but common usage is that data fields are mapped
				in order of major, secondary and minor. Systems
				that do not capture information for any of these
				elements should suppress the field to element
				mapping using the order described above. For
				example, if a system only has a single piece of
				data for marketing area, they should map this to
				the major area. If a system has two pieces of
				information, the mapping should be to the major
				and secondary area. In both examples, no data
				is mapped to the minor area and it would not
				be expressed in the response document.
			</xs:documentation>
    </xs:annotation>
    <xs:sequence>
        <xs:element name="MajorArea" type="commons:SecureString" minOccurs="0" maxOccurs="1">
            <xs:annotation>
                <xs:documentation>
						The major marketing area name, as defined by
						the MLS or other non-governmental organization
					</xs:documentation>
                <xs:appinfo>
                    <retsid>100385</retsid>
                    <example>Harbor Hill</example>
                </xs:appinfo>
            </xs:annotation>
        </xs:element>
        <xs:element name="SecondaryArea" type="commons:SecureString" minOccurs="0" maxOccurs="1">
            <xs:annotation>
                <xs:documentation>
						The secondary marketing area name, as defined
						by the MLS or other non-governmental
						organization.
					</xs:documentation>
                <xs:appinfo>
                    <retsid>100386</retsid>
                    <example>Hilltop</example>
                </xs:appinfo>
            </xs:annotation>
        </xs:element>
        <xs:element name="MinorArea" type="commons:SecureString" minOccurs="0" maxOccurs="1">
            <xs:annotation>
                <xs:documentation>
						A tertiary marketing area name, as
						defined by the MLS or other non-governmental
						organization.
					</xs:documentation>
                <xs:appinfo>
                    <retsid>100387</retsid>
                    <example>Old Crossroads</example>
                </xs:appinfo>
            </xs:annotation>
        </xs:element>
    </xs:sequence>
</xs:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
MajorArea commons:MajorArea 0 1
SecondaryArea commons:SecondaryArea 0 1
MinorArea commons:MinorArea 0 1
Collapse Derivation Tree:
Collapse References:
idxex:MarketingArea, list:MLSArea