![]() | |
#11
| |||
| |||
|
|
In article <87k4prnq1c.fsf (AT) benfinney (DOT) id.au>, bignose+hates- spam (AT) benfinney (DOT) id.au says... Jasen Betts <jasen (AT) xnet (DOT) co.nz> writes: On 2010-06-22, Ben Finney <bignose+hates-spam (AT) benfinney (DOT) id.au> wrote: A better example is street addresses (though, of course, there are some locations that make this not as simple as it might first appear). Country, state or province, postal code, city or town, street, property number, unit number, addressee's full name. That's much less ambiguous and more reliably queried and re-composed. Not really. There are national variations in addressing too, Yes, and if you read my message again you'll see that I allowed that. I maintain that, compared to people's names, addresses are much less ambiguous in their components and much more easily re-composed from components by simple mechanical process, and thus a better candidate for functional decomposition. I disagree. Basically every culture has "surname" and "given" personal name components (or in some cases, just a single name). It's just the order that they are written (or spoken) will vary. |
|
Addresses have a much wider range from what I've seen. |
#12
| |||
| |||
|
|
Normalization and this breaking down of fields into component parts (I hadn't heard the term "functional decomposition" before) aren't the same thing, though they are related. WRT the street address thing, I personally think breaking down the street address into multiple pieces is a mistake, but the city, state and postal code should be their own fields. |
#13
| |||
| |||
|
|
On Tue, 22 Jun 2010 14:49:48 -0400, David Kerber dkerber (AT) WarrenRogersAssociates (DOT) invalid> wrote: Normalization and this breaking down of fields into component parts (I hadn't heard the term "functional decomposition" before) aren't the same thing, though they are related. WRT the street address thing, I personally think breaking down the street address into multiple pieces is a mistake, but the city, state and postal code should be their own fields. For Canadian Postal Codes, the position on the street part of the address -- Does it have a name? -- does matter. Different values can have different Postal Codes. |
#14
| |||
| |||
|
|
On Tue, 22 Jun 2010, Gene Wirchenko wrote: On Tue, 22 Jun 2010 14:49:48 -0400, David Kerber dkerber (AT) WarrenRogersAssociates (DOT) invalid> wrote: Normalization and this breaking down of fields into component parts (I hadn't heard the term "functional decomposition" before) aren't the same thing, though they are related. WRT the street address thing, I personally think breaking down the street address into multiple pieces is a mistake, but the city, state and postal code should be their own fields. For Canadian Postal Codes, the position on the street part of the address -- Does it have a name? -- does matter. Different values can have different Postal Codes. Same in the UK. For example at the far ends of the rather long but entirely continuous Holloway Road: 91 Holloway Road is N7 8LT (and is a nice Georgian restaurant) 746 Holloway Road is N19 3JF (and is a very good bakery) |
#15
| |||
| |||
|
|
91 Holloway Road is N7 8LT (and is a nice Georgian restaurant) 746 Holloway Road is N19 3JF (and is a very good bakery) codes (which is what we call our postal codes). In the US, the 5-digit zip code tells you what post office handles the mail, and the last 4 (optional) digits narrow it down to a range of a block or a few blocks. |
#16
| |||
| |||
|
|
On Tue, 22 Jun 2010, Gene Wirchenko wrote: On Tue, 22 Jun 2010 14:49:48 -0400, David Kerber dkerber (AT) WarrenRogersAssociates (DOT) invalid> wrote: Normalization and this breaking down of fields into component parts (I hadn't heard the term "functional decomposition" before) aren't the same thing, though they are related. WRT the street address thing, I personally think breaking down the street address into multiple pieces is a mistake, but the city, state and postal code should be their own fields. For Canadian Postal Codes, the position on the street part of the address -- Does it have a name? -- does matter. Different values can have different Postal Codes. Same in the UK. For example at the far ends of the rather long but entirely continuous Holloway Road: 91 Holloway Road is N7 8LT (and is a nice Georgian restaurant) 746 Holloway Road is N19 3JF (and is a very good bakery) But i don't see why that means breaking down the address as David suggests is a problem. There is redundancy, because the postcode implies the street name even if not vice versa, and so this data wouldn't be normalised, but it would be decomposed. |
#17
| |||
| |||
|
|
If you are trying to look up Postal Codes, it is easier to have the address parsed. |
![]() |
| Thread Tools | |
| Display Modes | |
| |