Long Form XML - Multiple Dwellings

Multiple Dwellings

The Long Form template is required to accommodate multiple dwellings in the one report. To accommodate this requirement, two approaches have been taken to map related entities to a dwelling.

Repeated Nodes

In a similar fashion that is currently implemented for Short Forms, where a specific field is required to be supplied for each dwelling a parent element of the field can be repeated.

  • Where a repeated element is used, the first instance the element should contain all of the fields that are not applicable to multiple dwellings. ValEx will ignore fields that are not applicable to multiple dwellings in the repeated nodes.
  •  Where the element may not be applicable to a specific dwelling (e.g Lease) an empty element can be provided.

The following Elements may be repeated for the purpose of capturing dwelling specific details:

  • RealEstate
  • SiteDetailedResponse
  • ValueComponent
  • SalesMarket
  • BuildingModification
  • CarAccomodation
  • UnitDetails
  • AncillaryFeature
  • Lease
  • Development
<SiteDetailResponse TitleSearched="Yes" TitleSighted="Yes">
    <SiteDimensions Depth="" Frontage="" IrregularShape="No" UnitOfMeasurement="LinearMetres"/>         
    <SiteDimensions Depth="" Frontage="" IrregularShape="No" UnitOfMeasurement="LinearMetres"/>
    <SiteArea Size="100" UnitOfMeasurement="SquareMeters"/>
    <SiteArea Size="120" UnitOfMeasurement="SquareMeters"/>
    <Locality>
        <Amenity>
            <Identifier UniqueID=""/>
            <Description>The suburb of .... </Description>
        </Amenity>
    </Locality>
    <Neighbourhood>Comment...</Neighbourhood>
    <SiteDescription CurrentUse="Residential" ElevationPerStreetLevel="Above">Comment...</SiteDescription>
    <PropertyCharacteristics
        ActualWeeklyRental=""
        ArchitecturalStyle="Modern"
        Attachment="Attached"
        CurrentUse="Residential"
        EssentialRepairs=""
        FixturesAndFittings="Carpet, floor tiles."
        FloorConstructionMaterial="Concrete"
        RoofConstructionMaterial="Unsighted assumed to be metal decking"
        MainWallType="Rendered masonry, stone and aluminium cladding"
        WindowFrames="Aluminium"
        MainInteriorLinings="Plasterboard"
        ExternalCondition="Good"
        InternalCondition="Good"
        InternalLayout="Good" MainBuilding="Yes"
        MainBuildingComment="2 bedrooms, 2 bathrooms, Entry."
        MineSubsidence="No"
        NumberOfBathrooms="1"
        NumberOfBedrooms="2"
        PCItems="Double bowl sink."
        OtherServicesDescription="Electricity, town water"
        SiteArea="0"
        SiteAreaUnits="SquareMeters"
        StreetAppeal="Good"
        StyleDescription="Modern Attached Single Storey"
        YearBuilt="2012"
        YearBuiltIndicator="Circa" YearModified=""/>
    <PropertyCharacteristics
        ActualWeeklyRental=""
        ArchitecturalStyle="Modern"
        Attachment="Attached"
        CurrentUse="Residential"
        EssentialRepairs=""
        FixturesAndFittings="Carpet, floor tiles."
        FloorConstructionMaterial="Concrete"
        RoofConstructionMaterial="Unsighted assumed to be metal decking"
        MainWallType="Rendered masonry, stone and aluminium cladding"
        WindowFrames="Aluminium"
        MainInteriorLinings="Plasterboard"
        ExternalCondition="Good"
        InternalCondition="Good"
        InternalLayout="Good" MainBuilding="Yes"
        MainBuildingComment="2 bedrooms, 2 bathrooms, Entry."
        MineSubsidence="No"
        NumberOfBathrooms="1"
        NumberOfBedrooms="2"
        PCItems="Double bowl sink."
        OtherServicesDescription="Electricity, town water"
        SiteArea="0"
        SiteAreaUnits="SquareMeters"
        StreetAppeal="Good"
        StyleDescription="Modern Attached Single Storey"
        YearBuilt="2012"
        YearBuiltIndicator="Circa" YearModified=""/>
</SiteDetailResponse>

Improvement Areas

When providing Living Area, Outdoor Area and Other Area sizes, each living area type is required to be provided in dwelling order.

<ImprovementAreas AreaType="Living">
    <Identifier UniqueID="Dummy_Value"/>
    <SiteArea Size="85" UnitOfMeasurement="SquareMeters"/>
    <Description/>
</ImprovementAreas>
<ImprovementAreas AreaType="Living">
    <Identifier UniqueID="Dummy_Value"/>
    <SiteArea Size="100" UnitOfMeasurement="SquareMeters"/>
    <Description/>
</ImprovementAreas>
<ImprovementAreas AreaType="Outdoor">
    <Identifier UniqueID="Dummy_Value"/>
    <SiteArea Size="250" UnitOfMeasurement="SquareMeters"/>
    <Description/>
</ImprovementAreas>
<ImprovementAreas AreaType="Outdoor">
    <Identifier UniqueID="Dummy_Value"/>
    <SiteArea Size="300" UnitOfMeasurement="SquareMeters"/>
    <Description/>
</ImprovementAreas>

Recommended Documents to Sight

A recommended document to sight can be matched to a dwelling by setting the //ResponseSupportingDoc/Identifier/UniqueID to the dwelling identifier. Where a single document may apply to multiple dwellings, the identifier field can be repeated.

<ResponseSupportingDoc DocAttached="Yes" RequestorToSight="Yes" DocType="Image">
    <Identifier UniqueID="DW1"/>
    <Identifier UniqueID="DW2"/>
    <Description>Excavations Photo</Description>
</ResponseSupportingDoc>

Related Party References

So that a Dwelling can be referenced, for Long Forms an Identifier must be provided under the RealEstate node so related party elements can reference a specific dwelling. The dwelling identifier must have a description of “DwellingID”.

<FullRegistered ValSubType="Standard" PrimaryValuationMethod="DirectComparison" SecondaryValuationMethod="Summation">
    <SubTypeNote></SubTypeNote>
    <RealEstate Construction="No" Transaction="Purchasing">
        <Identifier UniqueID="DW1" Type="VPMAssigned" Description="DwellingID"/>
        <Residential/>
        <EstimatedValue EstimateBasis="CustomerEstimate">660000</EstimatedValue>

Lessor, Lessee, TitleLessee and Architect related parties can be associated to a dwelling buy adding a related entity reference to the applicable dwelling identifier. ValEx will only parse the Firstname and Surname details for these related party types. 

<RelatedParty RelPartyType="Architect" RelPartyDescription="Applicant">
    <Identifier UniqueID="7" Type="BrokerAssigned"/>
    <PersonName>
        <FirstName>Joe</FirstName>
        <Surname>Bloggs</Surname>
    </PersonName>
    <RelatedEntityRef RelatedID="DW1"/>
</RelatedParty>

Dwelling Names

Under every RealEstate node for each dwelling a Residential node must exist containing text up to 20 characters, this is a unique name for the dwelling used on the report:

/ValuationTransaction/Message/ValuationType/FullRegistered/RealEstate/Residential 

<RealEstate>
   <Residential>Dwelling 1</Residential>
   ...
</RealEstate>