Address Change Publisher

Here we discuss how we will go about publishing changes to addresses.

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.
See corrected examples below.

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.
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 APNs, you do a retire/replace.

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.

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

Example 1

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:

    <address>
        <number>14</number>
        <street>MAPLE ST</street>
        <unit>
            <base>true</base>
            <number></number>
            <disposition>official</disposition>
            <create_tms>2010-07-02 08:18:50.937000</create_tms>
            <retire_tms>None</retire_tms>
            <apns>
                <apn>1234001</apn>
            </apns>
            <action>insert</action>
        </unit>
    </address>

The "action" tag domain is

    insert
    update
    retire

I think this addresses Q1.

The "base" tag domain is:

    true
    false

This is a MAD artifact - DBI probably won'lt 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

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

    <address>
        <number>14</number>
        <street>MAPLE ST</street>
        <unit>
            <base>true</base>
            <number></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>

There is no ownwership at the unit level.
The owner is specified at the base address level.

Example 3

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

message 1

    <address_change>
        <action>insert</action>
        <address>
            <number>14</number>
            <street>MAPLE ST</street>
            <unit_number>a</unit_number>
            ...
            <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.

Example 4

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

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

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

message 2

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

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.
Val, please take a look at this address and tell me if you think we need to
do anything special here.
http://174.37.80.164/

Example 6

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.

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

    <address_change>
        <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>
        </address>
    </address_change>

message 2 (condo unit)

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

message 3 (condo unit)

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

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

MAD - address publishing

Val,
Hema,

I think I have a good start on the address publisher.
I am producing the xml you see below.
Of course I will have to work on the format of the xml to fit your requirements.

So from you, I will need the following:
1) a complete example of the xml you would like to receive
2) target web server details: host, port, user, password, path

Regards,
Paul

<unit>
<number>400</number>
<disposition>provisional</disposition>
<create_tms>2010-07-02 08:18:50.937000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>FL3</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>1500</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>48</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>1550</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>308</number>
<disposition>provisional</disposition>
<create_tms>2010-07-02 14:11:22.843000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>
<apn>0026028</apn>

</apns>
</address>

sleeping for 5 seconds
---- 2010-07-02 14:50:21.921000 ----
<address>

<number>1</number>
<street>S VAN NESS AVE</street>
<unit>
<number>400</number>
<disposition>provisional</disposition>
<create_tms>2010-07-02 08:18:50.937000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>FL3</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>1500</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>48</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>1550</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>308</number>
<disposition>provisional</disposition>
<create_tms>2010-07-02 14:11:22.843000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>
<apn>0026028</apn>

</apns>
</address>

sleeping for 5 seconds
---- 2010-07-02 14:50:27.656000 ----
<address>

<number>1</number>
<street>S VAN NESS AVE</street>
<unit>
<number>400</number>
<disposition>provisional</disposition>
<create_tms>2010-07-02 08:18:50.937000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>FL3</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>1500</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>48</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>1550</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>308</number>
<disposition>provisional</disposition>
<create_tms>2010-07-02 14:11:22.843000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>
<apn>0026028</apn>

</apns>
</address>

sleeping for 5 seconds
---- 2010-07-02 14:50:33.406000 ----
<address>

<number>1</number>
<street>S VAN NESS AVE</street>
<unit>
<number>400</number>
<disposition>provisional</disposition>
<create_tms>2010-07-02 08:18:50.937000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>FL3</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>1500</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>48</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>1550</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>308</number>
<disposition>provisional</disposition>
<create_tms>2010-07-02 14:11:22.843000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>
<apn>0026028</apn>

</apns>
</address>

sleeping for 5 seconds
---- 2010-07-02 14:50:39.125000 ----
<address>

<number>1</number>
<street>S VAN NESS AVE</street>
<unit>
<number>400</number>
<disposition>provisional</disposition>
<create_tms>2010-07-02 08:18:50.937000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>FL3</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>

<unit>
<number>1500</number>
<disposition>official</disposition>
<create_tms>2009-09-01 16:59:51.607000</create_tms>
<retire_tms>None</retire_tms>
</unit>
<apns>

</apns>
</address>