This is non-essential in that we can use GeoShape --address-- PostalAddress -- postalCode-- xyz.
But that is needlessly heavy, so let's pick out the most useful piece of PostalAddress for this purpose, postalCode. This fits well with the approach implemented in #808 which allows these to have a simple textual 'address' too.
The text was updated successfully, but these errors were encountered:
You're right. It would make more sense with a Country.
The most obvious options seem to be:
use address with a value of PostalAddress which has an addressCountry ...
allow addressCountry to apply to these types directly
In passing I note that Country says "You can also provide the two-letter ISO 3166-1 alpha-2 country code." but doesn't say which property of a Country would carry such a code (e.g. alternateName? should we add something?) [edit: rather - we don't say how the property would use the codes. We ALSO don't say how these codes would show up via the Country type, see #815).
Just as suggestion, some time ago I came across with a ISO standard for Addresses via UPU ( Universal Postal Union - upu.net ) .
The direction they go is ZIP CODE-COUNTRY, Thus maybe a format like Country ISO_3166-2 - Zip Code would satisfy ( ex. US-90210 would suffice ).