Thoughts?
I'd agree with that. Very common attributes for something like an
ecommerce site.
http://axschema.org/contact/postalAddress/shipping | ShippingAddress | |
http://axschema.org/contact/postalAddressAdditional/shipping | Shipping Address 2 | |
http://axschema.org/contact/city/shipping | Shipping City | |
http://axschema.org/contact/state/shipping | Shipping State/Province | |
http://axschema.org/contact/country/shipping | Shipping Country | |
http://axschema.org/contact/postalCode/shipping | Shipping Postal code |
http://axschema.org/contact/postalAddress/billing | Billing Address | |
http://axschema.org/contact/postalAddressAdditional/billing | Billing Address 2 | |
http://axschema.org/contact/city/billing | Billing City | |
http://axschema.org/contact/state/billing | Billing State/Province | |
http://axschema.org/contact/country/billing | Billing Country | |
http://axschema.org/contact/postalCode/billing | Billing Postal code |
Yes I agree and your proposal looks sound, apart from the fact with UK
addresses, we could really do with 3 top address lines!
EG:
Address1
Address2
Address3
City
State/Province/County
Country
Postal code
For example my old parents address used to be:
House name
1, Street name
Village
City (actually nearest town)
UK
Post code
And for the UK, this lengthy address is not uncommon, so please could
you propose this for me?
Cheers Mark
Date: Tue, 20 Nov 2007 09:49:52 -0700
From: sapp...@gmail.com
To: axsc...@googlegroups.com
Subject: Re: Intent to define - New Addresses
CC: m1...@hotmail.com
Appending home, home2, and home3 would make those different groups of
values but still for the same base "postalAddress" attribute.
What we might want to do is append to "postalAddress" more like this:
http://axschema.org/contact/postalAddress/street1/home
http://axschema.org/contact/postalAddress/street2/home
Which would more easily extend to the conventional street1, 2, 3 as
well as break down into finer-grained parts like direction, street
type, etc.
So, "postalAddressAdditional" would become "postalAddress/street2"
I think by doing that it would become more like "namePerson" in that
you could simply request "/contact/postalAddress" and get the entire
thing. (Whereas now you have to ask for 2 separate attributes).
The "postalAddress" and "namePerson" URI's have always bugged me a
bit but I'd never really considered changing them before for the sake
of compatibility.
I agree, it does feel backwards, I felt the same way when I first saw
it, but I know there is an explanation for the trailing "home",
"work", etc item...
The idea was that you can request a "street1" item from a user
without caring whether it is their home, work, etc. address. And
potentially the user can decide which address they would like to give
you. Moving up the parts of the URI gives you progressively more
generic values.