Page Comparison

...

A2.1
This part might be interesting.
Please tread read this entire page to get a sense of what we need to do.
In particluarparticular, please look at example 3 as well as 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.

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 make change 3 things on an address

• retire
• status (provisional, offical...)
• location
  You may not change anything else.
  Once the APNs are set, you cannot change them.
  If you need to change the associated APNs, you do a retire/replace.

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

...

A5
I will add the native primary key to the messages.

Q6

A6

...

A simple example to get us started.
This example is DBI does not track addresses with no ownership but MAD does.
For example, an apartment build with 10 aprtments will have 10 MAD addresses but only 1 DBI address.
HOw will we handle this?

A6
The publisher will send only addresses that have APNs.

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:

...

    insert
    update
    retire

I think this addresses Q1question 1 above.

The "base" tag domain is:

...

    <address>
        <number>14</number>
        <street>MAPLE ST</street>
        <unit>
            <base>true</base>
            <number><<number>100</number>
            ...
            <apns>
                <apn>1234001</apn>
            </apns>
            <action>insert</action>
        </unit>
        <unit>
            <base>false</base>
            <number>a</number>
            ...
            <apns></apns>
            <action>insert</action>
        </unit>
        <unit>
            <base>false</base>
            <number>b</number>
            ...
            <apns></apns>
            <action>insert</action>
        </unit>
    </address>

...

What I think we want an instead of the example 2 (apt building) is something like this:

message 1

<xml>
    <address_change>
        <key>12873</key>
        <action>insert</action>
        <address>
            <number>14</number>
            <street>MAPLE ST</street>
            <unit_number>a<number>100</unit_number>
            ...<apn>1234001</apn>
            <apn>1234001</apn>
        </address>
    </address_change>

message 2

    <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.

</xml>

Example 4

Anchor
example4 example4

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

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

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.

message 1

<xml>
    <address_change>
        <address_change><key>12873</key>
        <action>insert</action>
        <address>
            <number>2655</number>
            <street>HYDE ST</street>
            <unit_number>1</unit_number>
            <disposition>provisional</disposition>
            <create_tms>2010-07-02 14:11:22.843000</create_tms>
            <retire_tms>None</retire_tms>
            <apn>0026T065A</apn>
        </address>
    </address_change>
</xml>

message 2

<xml>
    <address_change>
        <key>12873</key>
        <action>insert</action>
        <address>
            <number>2655</number>
            <street>HYDE ST</street>
            <unit_number>1</unit_number>
            <disposition>provisional</disposition>
            <create_tms>2010-07-02 14:11:22.843000</create_tms>
            <retire_tms>None</retire_tms>
            <apn>0026T066A</apn>
        </address>
    </address_change>
</xml>

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 tenants in common example, where each unit has a single owner, and there
is a "common area" owned by the owners association.

message 1 (base unit or common area, APN is assigned)

<xml>
    <address_change>
        <key>12873</key>
        <action>insert</action>
        <address>
            <number>100</number>
            <street>MAIN ST</street>
            <unit_number></unit_number>
            <disposition>provisional</disposition>
            <create_tms>2010-07-02 14:11:22.843000</create_tms>
            <retire_tms>None</retire_tms>
            <apn>12340001<<apn>1234001</apn>
        </address>
    </address_change>
</xml>

message 2 (condo unit)

<xml>
    <address_change>
        <key>12873</key>
        <action>insert</action>
        <address>
            <number>100</number>
            <street>MAIN ST</street>
            <unit_number>1</unit_number>
            <disposition>provisional</disposition>
            <create_tms>2010-07-02 14:11:22.843000</create_tms>
            <retire_tms>None</retire_tms>
            <apn>1234002</apn>
        </address>
    </address_change>
</xml>

message 3 (condo unit)

<xml>
    <address_change>
        <key>12873</key>
        <action>insert</action>
        <address>
            <number>100</number>
            <street>MAIN ST</street>
            <unit_number>2</unit_number>
            <disposition>provisional</disposition>
            <create_tms>2010-07-02 14:11:22.843000</create_tms>
            <retire_tms>None</retire_tms>
            <apn>1234003</apn>
        </address>
    </address_change>
<xml>

========================= original email ================================

...