Page Comparison

...

Q1
From DBI's perspective, we are either going to be inserting addresses or updating addresses with your data. (Addresses are never deleted but retired on our end and yours I believe). How will we tell the difference if it is an address update or a brand new address? via an XML tag?

A1
Agreed.
Jump ahead to example 3 to see a proposed solution.
We will publish every insert and update.
A retire is a special kind of update.
While addresses can be retired, they cannot be deleted.

Q2
The first example you give below does not have an APN (what DBI refers to as block/lot). DBI cannot make use of any address without an APN (block/lot). These should be excluded until they are complete.

A2.1
This part might be interesting.
Please tread this entire page to get a sense of what we need to do.
In particluar, please look at this question example 3 as well as this question example 5 along with the questions posed at the end of the example.
MAD addresses can be associated with APNs or not.
By and large I think they are, but read more below.

A2.2
A MAD address is mostly immutable (if that make sense).
You can retire it, and change it's status, and change it's location.
But you cannot change anything else.
Once the APNs are set, you cannot change them.
If you need to change the asscoated associated APNs, you do a retire/replace.

A2.3
We can use APN or BlkLot for this XML - your choice - most municipalities use APN.

Q3
2655 HYDE ST below has a bunch of APN's associated with it. For convenience, we would like each APN sent to us as a separate complete <address> .

A3
No problem.
See corrected examples below Take a look at example 3 which is fairly close to what I think we want.

Q4
Also, the 2655 Hyde is broken up into units(<number>) (318), but there doesn't seem to be a connection between the unit(<number>) and the APN in the data below, but perhaps I am misreading it.

A4
My apologies, I had it wrong.
See corrected examples below.

We will publish every insert and update.
A retire is a special kind of update.
While addresses can be retired, they cannot be deleted.

First we discuss the XML message layoutmisreading it.

A4
My apologies, I had it wrong.
Please take a look at example 5.

Example 1

Anchor
example1 example1

A simple example to get us started.
This example is MAD centric.
I suspect that we'll end up with something a alot different at the end of this discussion.
Here is a single family dwelling with one owner:

...

This is a MAD artifact - DBI probably won't want it.
But let me explain the purpose.
A MAD "address" is represented using the concept of a base address and a unit address.
A base address always has one corresponding unit address.
There may be additional unit addresses or not.
If the base tag is marked true, then this unit information is directly associated with the base address.
If the base tag is marked false, then this unit information is not directly associated with the base address.

Example 2

Anchor
example2 example2

Now in the case of an apartment bldg, say
14 MAPLE ST,
apartments a & b
MAD represents the world this way:

...

    <address_change>
        <action>insert</action>
        <address>
            <number>14</number>
            <street>MAPLE ST</street>
            <unit_number>b</unit_number>
            ...
            <apn>1234001</apn>
        </address>
    </address_change>

...

Here, we assume that if a unit does not have an APN, we shall use the APN or APNs assigned at the base level.
Val - Please confirm that this is correct.

Example 4

Anchor
example4 example4

And reworking example 1 (single family) to fit the model shown in example 3, we have this:

    <address_change>
        <action>insert</action>
        <address>
            <number>14</number>
            <street>MAPLE ST</street>
            <unit_number></unit_number>
            ...
            <apn>1234001</apn>
        </address>
    </address_change>

Example 5

Anchor
example5 example5

Let's move on to a time share, which can be seen at 2655 Hyde St.
In a time share we have a single unit with multiple owners.

...

The only difference here is that the APN is different in message 2.
This much is straight forward.
If a unit address changes, and there are APNs assigned to the unit,
we have one address change message for each of these APNs.
But at 2655 Hyde, there are lots of APNs assigned to the base address.

Example 6

Anchor
example6 example6

Here is a condo or tennants in common example, where each unit has a single owner, and there
is a "common area" owned by the owners association.

...