...
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:
...
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:
...
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:
...
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:
| Code Block |
|---|
<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.
...
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,
Example 6
---------
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.
...
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>
...
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>
...
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>
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>
...